[web] Added System Administrators Guide in Japanese translation for f17.
Tadashi Jokagi
elf at fedoraproject.org
Sat Mar 16 10:11:45 UTC 2013
commit 4bc5298dd72fd185746e9bf6555ce2069746ce28
Author: Tadashi Jokagi <elf at poyo.jp>
Date: Sat Mar 16 00:16:24 2013 +0900
Added System Administrators Guide in Japanese translation for f17.
fedoradocs.db | Bin 921600 -> 924672 bytes
public_html/Sitemap | 24 +
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 +-
public_html/es-ES/opds-Fedora_15.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Core.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 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fr-FR/opds.xml | 14 +-
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 +-
...edora-17-System_Administrators_Guide-ja-JP.epub | Bin 0 -> 8793468 bytes
.../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
...etwork_Configuration-NM-AppletStates_Gnome3.png | Bin 0 -> 29735 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/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 -> 53804 bytes
.../images/authconfig_advanced.png | Bin 0 -> 45924 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/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 -> 13800 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/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/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/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 |15759 ++++++++++++++++++++
.../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 | 15 +
.../appe-Consistent_Network_Device_Naming.html | 53 +
.../ch-Automating_System_Tasks.html | 146 +
.../ch-Configuring_Authentication.html | 428 +
.../ch-Configuring_the_Date_and_Time.html | 25 +
.../ch-Configuring_the_Language_and_Keyboard.html | 21 +
.../ch-DHCP_Servers.html | 15 +
.../ch-DNS_Servers.html | 39 +
.../ch-Directory_Servers.html | 499 +
.../ch-File_and_Print_Servers.html | 662 +
...ackage_Management-sec-Additional_Resources.html | 15 +
.../ch-Mail_Servers.html | 97 +
.../ch-Managing_Users_and_Groups.html | 43 +
.../ch-Manually_Upgrading_the_Kernel.html | 39 +
.../ch-NetworkManager.html | 28 +
.../ch-Network_Interfaces.html | 39 +
.../System_Administrators_Guide/ch-OProfile.html | 74 +
.../System_Administrators_Guide/ch-OpenSSH.html | 95 +
.../System_Administrators_Guide/ch-PackageKit.html | 45 +
.../html/System_Administrators_Guide/ch-RPM.html | 53 +
.../ch-Services_and_Daemons.html | 33 +
.../ch-System_Monitoring_Tools.html | 148 +
.../ch-The_X_Window_System.html | 29 +
.../ch-The_sysconfig_Directory.html | 335 +
.../ch-Viewing_and_Managing_Log_Files.html | 325 +
.../ch-Web_Servers.html | 1357 ++
.../ch-Working_with_Kernel_Modules.html | 79 +
.../html/System_Administrators_Guide/ch-kdump.html | 17 +
.../html/System_Administrators_Guide/ch-proc.html | 64 +
.../html/System_Administrators_Guide/ch-yum.html | 102 +
.../System_Administrators_Guide/ch11s02s03.html | 40 +
.../chap-SSSD_User_Guide-Configuring_Domains.html | 290 +
.../chap-SSSD_User_Guide-Configuring_Services.html | 73 +
.../chap-SSSD_User_Guide-Introduction.html | 17 +
.../chap-SSSD_User_Guide-Setting_Up_SSSD.html | 185 +
.../chap-SSSD_User_Guide-Troubleshooting.html | 121 +
.../dhcp-relay-agent.html | 17 +
.../images/Editing-VPN-connection-1.png | Bin 0 -> 40728 bytes
.../Network_Configuration-NM-All_applet_states.png | Bin 0 -> 11632 bytes
...etwork_Configuration-NM-AppletStates_Gnome3.png | Bin 0 -> 29735 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/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 -> 53804 bytes
.../images/authconfig_advanced.png | Bin 0 -> 45924 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/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 -> 13800 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/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/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/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
.../17/html/System_Administrators_Guide/index.html | 34 +
.../17/html/System_Administrators_Guide/ix01.html | 9 +
.../lease-database.html | 17 +
.../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-Networking.html | 11 +
.../part-Package_Management.html | 11 +
.../System_Administrators_Guide/part-Servers.html | 11 +
.../17/html/System_Administrators_Guide/pr01.html | 25 +
.../html/System_Administrators_Guide/pr01s03.html | 61 +
.../System_Administrators_Guide/pr01s03s02.html | 34 +
.../System_Administrators_Guide/pr01s03s03.html | 17 +
.../pref-Acknowledgments.html | 15 +
.../html/System_Administrators_Guide/s1-BIND.html | 347 +
.../html/System_Administrators_Guide/s1-FTP.html | 25 +
.../s1-autotasks-additional-resources.html | 23 +
.../s1-autotasks-at-batch.html | 41 +
.../s1-check-rpm-sig.html | 37 +
.../s1-dhcp-additional-resources.html | 23 +
.../s1-dhcp-configuring-client.html | 29 +
.../s1-dhcp-configuring-server.html | 110 +
.../s1-dhcp_for_ipv6_dhcpv6.html | 23 +
.../s1-email-additional-resources.html | 35 +
.../System_Administrators_Guide/s1-email-mda.html | 63 +
.../System_Administrators_Guide/s1-email-mta.html | 78 +
.../System_Administrators_Guide/s1-email-mua.html | 61 +
.../s1-email-types.html | 21 +
.../s1-kdump-configuration.html | 21 +
.../s1-kdump-crash.html | 64 +
.../s1-kdump-resources.html | 19 +
.../s1-kernel-boot-loader.html | 83 +
.../s1-kernel-download.html | 17 +
.../s1-kernel-modules-additional-resources.html | 29 +
.../s1-kernel-perform-upgrade.html | 17 +
.../s1-kernel-preparing.html | 51 +
.../s1-log-files-additional-resources.html | 19 +
.../s1-logfiles-adding.html | 17 +
.../s1-logfiles-examining.html | 13 +
.../s1-logfiles-locating.html | 78 +
.../s1-logfiles-viewing.html | 49 +
.../s1-networkscripts-control.html | 51 +
.../s1-networkscripts-functions.html | 15 +
.../s1-networkscripts-interfaces.html | 126 +
.../s1-networkscripts-resources.html | 15 +
.../s1-networkscripts-static-routes.html | 54 +
.../s1-openssh-additional-resources.html | 25 +
.../s1-oprofile-additional-resources.html | 15 +
.../s1-oprofile-analyzing-data.html | 58 +
.../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 | 17 +
.../s1-oprofile-saving-data.html | 15 +
.../s1-oprofile-starting.html | 25 +
.../s1-printing-additional-resources.html | 29 +
.../s1-printing-edit.html | 64 +
.../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-proc-additional-resources.html | 23 +
.../s1-proc-directories.html | 118 +
.../s1-proc-sysctl.html | 32 +
.../s1-proc-topfiles.html | 23 +
.../s1-rpm-additional-resources.html | 15 +
.../s1-rpm-impressing.html | 87 +
.../System_Administrators_Guide/s1-rpm-using.html | 31 +
.../s1-services-additional-resources.html | 11 +
.../s1-services-running.html | 64 +
.../s1-ssh-beyondshell.html | 22 +
.../s1-ssh-clients.html | 34 +
.../s1-ssh-configuration.html | 95 +
.../s1-sysconfig-additional-resources.html | 13 +
.../s1-sysconfig-etcsysconf-dir.html | 30 +
.../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-groups-additional-resources.html | 45 +
.../s1-users-tools.html | 171 +
.../s1-x-additional-resources.html | 19 +
.../System_Administrators_Guide/s1-x-clients.html | 25 +
.../System_Administrators_Guide/s1-x-fonts.html | 29 +
.../s1-x-server-configuration.html | 39 +
.../s2-autotasks-at-batch-controlling-access.html | 17 +
.../s2-autotasks-at-batch-service.html | 17 +
.../s2-autotasks-at-batch-viewing.html | 11 +
.../s2-autotasks-batch-configuring.html | 19 +
.../s2-autotasks-commandline-options.html | 27 +
.../s2-bind-additional-resources.html | 41 +
.../System_Administrators_Guide/s2-bind-dig.html | 96 +
.../s2-bind-features.html | 35 +
.../s2-bind-mistakes.html | 21 +
.../System_Administrators_Guide/s2-bind-rndc.html | 88 +
.../System_Administrators_Guide/s2-bind-zone.html | 264 +
.../s2-email-mta-fetchmail.html | 115 +
.../s2-email-mta-sendmail.html | 117 +
.../s2-email-procmail-recipes.html | 140 +
.../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 | 25 +
.../s2-ftp-resources.html | 27 +
.../s2-ftp-servers.html | 35 +
.../s2-ftp-vsftpd-conf.html | 337 +
.../s2-ftp-vsftpd-start.html | 33 +
.../s2-kdump-configuration-cli.html | 96 +
.../s2-kdump-configuration-gui.html | 95 +
.../s2-kdump-configuration-testing.html | 18 +
.../s2-kdump-crash-backtrace.html | 34 +
.../s2-kdump-crash-exit.html | 12 +
.../s2-kdump-crash-files.html | 21 +
.../s2-kdump-crash-log.html | 36 +
.../s2-kdump-crash-memory.html | 39 +
.../s2-kdump-crash-processes.html | 24 +
.../s2-kdump-resources-online.html | 15 +
.../s2-kernel-boot-loader-iseries.html | 17 +
.../s2-kernel-boot-loader-pseries.html | 26 +
...rnel-modules-additional-resources-websites.html | 11 +
.../s2-keys-checking.html | 17 +
.../s2-log-files-useful-websites.html | 13 +
.../s2-networkscripts-interfaces-alias.html | 31 +
.../s2-networkscripts-interfaces-chan.html | 40 +
.../s2-networkscripts-interfaces-other.html | 19 +
.../s2-networkscripts-interfaces-ppp0.html | 74 +
...workscripts-interfaces_802.1q-vlan-tagging.html | 31 +
...2-networkscripts-interfaces_network-bridge.html | 90 +
.../s2-openssh-useful-websites.html | 15 +
.../s2-oprofile-events.html | 225 +
.../s2-oprofile-module-output.html | 37 +
.../s2-oprofile-reading-opannotate.html | 17 +
.../s2-oprofile-reading-opreport-single.html | 71 +
.../s2-oprofile-starting-separate.html | 33 +
.../s2-oprofile-useful-websites.html | 13 +
.../s2-proc-cmdline.html | 21 +
.../s2-proc-cpuinfo.html | 47 +
.../s2-proc-crypto.html | 22 +
.../s2-proc-devices.html | 46 +
.../s2-proc-dir-bus.html | 33 +
.../s2-proc-dir-driver.html | 31 +
.../s2-proc-dir-fs.html | 11 +
.../s2-proc-dir-irq.html | 17 +
.../s2-proc-dir-net.html | 53 +
.../s2-proc-dir-scsi.html | 96 +
.../s2-proc-dir-sys.html | 332 +
.../s2-proc-dir-sysvipc.html | 11 +
.../System_Administrators_Guide/s2-proc-dma.html | 13 +
.../s2-proc-execdomains.html | 15 +
.../System_Administrators_Guide/s2-proc-fb.html | 13 +
.../s2-proc-filesystems.html | 37 +
.../s2-proc-interrupts.html | 49 +
.../System_Administrators_Guide/s2-proc-iomem.html | 29 +
.../s2-proc-ioports.html | 37 +
.../System_Administrators_Guide/s2-proc-kcore.html | 15 +
.../System_Administrators_Guide/s2-proc-kmsg.html | 11 +
.../s2-proc-loadavg.html | 17 +
.../System_Administrators_Guide/s2-proc-locks.html | 23 +
.../s2-proc-mdstat.html | 21 +
.../s2-proc-meminfo.html | 87 +
.../System_Administrators_Guide/s2-proc-misc.html | 15 +
.../s2-proc-modules.html | 40 +
.../s2-proc-mounts.html | 29 +
.../System_Administrators_Guide/s2-proc-mtrr.html | 18 +
.../s2-proc-partitions.html | 28 +
.../System_Administrators_Guide/s2-proc-pci.html | 44 +
.../System_Administrators_Guide/s2-proc-pid.html | 57 +
.../s2-proc-slabinfo.html | 66 +
.../System_Administrators_Guide/s2-proc-stat.html | 48 +
.../System_Administrators_Guide/s2-proc-swaps.html | 16 +
.../s2-proc-sysrq-trigger.html | 13 +
.../System_Administrators_Guide/s2-proc-tty.html | 29 +
.../s2-proc-uptime.html | 15 +
.../s2-proc-version.html | 15 +
.../s2-redhat-config-users-group-new.html | 15 +
.../s2-redhat-config-users-group-properties.html | 15 +
.../s2-redhat-config-users-user-new.html | 27 +
.../s2-redhat-config-users-user-properties.html | 23 +
.../s2-rpm-freshening.html | 23 +
.../s2-rpm-querying.html | 35 +
.../s2-rpm-related-books.html | 11 +
.../s2-rpm-uninstalling.html | 26 +
.../s2-rpm-useful-websites.html | 13 +
.../s2-rpm-verifying.html | 51 +
.../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 | 127 +
.../s2-ssh-configuration-requiring.html | 23 +
.../s2-ssh-configuration-sshd.html | 28 +
.../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 | 25 +
.../s2-users-tools-password-aging.html | 65 +
.../s2-users-tools-users-logout.html | 39 +
.../s2-x-clients-winmanagers.html | 23 +
.../s2-x-server-config-xorg.conf.d.html | 13 +
.../s2-x-server-config-xorg.conf.html | 242 +
.../s2-x-useful-websites.html | 17 +
.../s3-ftp-vsftpd-conf.html | 23 +
.../s3-services-running-restarting.html | 13 +
.../s3-services-running-running.html | 15 +
.../s3-services-running-stopping.html | 15 +
.../sec-Adding_Other_Printer.html | 33 +
.../sec-Additional_Resources.html | 11 +
.../sec-Configuration_File_Changes.html | 23 +
.../sec-Configuring_Connection_Settings.html | 82 +
.../sec-Configuring_IPv4_Settings.html | 39 +
.../sec-Configuring_IPv6_Settings.html | 25 +
...uring_New_and_Editing_Existing_Connections.html | 27 +
...ec-Configuring_PPP_Point-to-Point_Settings.html | 21 +
.../sec-Configuring_Wireless_Security.html | 25 +
.../sec-Configuring_Yum_and_Yum_Repositories.html | 125 +
.../sec-Connecting_to_a_Network_Automatically.html | 23 +
.../sec-Creating_a_Yum_Repository.html | 19 +
.../sec-Displaying_Information_About_a_Module.html | 71 +
.../sec-Displaying_Package_Information.html | 46 +
.../sec-Establishing_Connections.html | 57 +
.../sec-Establishing_Routes.html | 23 +
.../sec-Establishing_a_DSL_Connection.html | 20 +
...Establishing_a_Mobile_Broadband_Connection.html | 105 +
.../sec-Establishing_a_VPN_Connection.html | 87 +
.../sec-Establishing_a_Wireless_Connection.html | 98 +
.../sec-Finding_Packages_with_Filters.html | 56 +
.../sec-Installing.html | 60 +
.../sec-Installing_More_Yum_Plugins.html | 11 +
...sec-Installing_and_Removing_Package_Groups.html | 15 +
...ing_and_Removing_Packages_and_Dependencies.html | 27 +
.../sec-Installing_and_Upgrading.html | 89 +
.../sec-Interacting_with_NetworkManager.html | 32 +
.../sec-Listing_Packages.html | 110 +
.../sec-Loading_a_Module.html | 29 +
.../sec-Managing_Yum_Repositories.html | 47 +
.../sec-NetworkManager_Architecture.html | 11 +
.../sec-PackageKit_Architecture.html | 93 +
.../sec-Packages_and_Package_Groups.html | 24 +
.../sec-Persistent_Module_Loading.html | 24 +
.../sec-Plugin_Descriptions.html | 150 +
.../sec-Printer_Configuration.html | 23 +
.../System_Administrators_Guide/sec-Removing.html | 35 +
.../sec-Setting_Module_Parameters.html | 44 +
.../sec-Setting_Printer.html | 23 +
.../sec-Setting_repository_Options.html | 45 +
.../sec-Specific_Kernel_Module_Capabilities.html | 15 +
.../sec-Unloading_a_Module.html | 40 +
.../sec-User_and_System_Connections.html | 33 +
.../sec-Using_Add_Remove_Software.html | 17 +
.../sec-Using_Channel_Bonding.html | 191 +
.../sec-Using_Yum_Variables.html | 25 +
.../sec-Verifying_the_Initial_RAM_Disk_Image.html | 71 +
.../sec-Viewing_the_Current_Configuration.html | 26 +
.../sec-Viewing_the_Transaction_Log.html | 20 +
.../sec-Yum-Transaction_History.html | 221 +
.../sec-Yum_Plugins.html | 34 +
.../sec-printing-LPDLPR-printer.html | 29 +
.../sect-Configuring_a_Multihomed_DHCP_Server.html | 114 +
...ing_the_Date_and_Time-Additional_Resources.html | 17 +
...d_Line_Configuration-Network_Time_Protocol.html | 51 +
...e_and_Time-Command_Line_Configuration-Time.html | 17 +
...e_Date_and_Time-Command_Line_Configuration.html | 17 +
...figuring_the_Language_and_Keyboard-Formats.html | 19 +
...figuring_the_Language_and_Keyboard-Layouts.html | 23 +
...nfiguring_the_Language_and_Keyboard-System.html | 13 +
...twork_Device_Naming-Enabling_and_Disabling.html | 17 +
...ect-Consistent_Network_Device_Naming-Notes.html | 13 +
..._Network_Device_Naming-System_Requirements.html | 13 +
...and_Groups-User_Accounts-Adding_a_New_User.html | 27 +
...s_and_Groups-User_Accounts-Removing_a_User.html | 15 +
...ct-Managing_Users_and_Groups-User_Accounts.html | 31 +
.../sect-Preface-Book_Organization.html | 79 +
.../sect-Preface-Feedback.html | 19 +
...Domains-Setting_up_Kerberos_Authentication.html | 80 +
...uration_Options-Configuring_a_Proxy_Domain.html | 86 +
...SSSD_User_Guide-Introduction-SSSD_Features.html | 57 +
...ation_Files-SSSD_Configuration_File_Format.html | 70 +
...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 +
...Fedora-17-System_Administrators_Guide-ja-JP.pdf | Bin 0 -> 7286670 bytes
public_html/ja-JP/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ja-JP/opds-Fedora.xml | 15 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Core.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 | 14 +-
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/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 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Security_Team.xml | 2 +-
public_html/nl-NL/opds.xml | 14 +-
public_html/opds.xml | 90 +-
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 +-
1173 files changed, 41618 insertions(+), 723 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index febb9dd..f288190 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 0053e5f..4de64d3 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -9937,6 +9937,30 @@
<priority>0.8</priority>
</url>
<url>
+ <loc>http://docs.fedoraproject.org/ja-JP/Fedora/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.epub</loc>
+ <lastmod>2013-03-15</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/ja-JP/Fedora/17/html/System_Administrators_Guide/index.html</loc>
+ <lastmod>2013-03-15</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/ja-JP/Fedora/17/html-single/System_Administrators_Guide/index.html</loc>
+ <lastmod>2013-03-15</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/ja-JP/Fedora/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.pdf</loc>
+ <lastmod>2013-03-15</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
<loc>http://docs.fedoraproject.org/ja-JP/Fedora/16/epub/Accessibility_Guide/Fedora-16-Accessibility_Guide-ja-JP.epub</loc>
<lastmod>2011-12-01</lastmod>
<changefreq>monthly</changefreq>
diff --git a/public_html/as-IN/Site_Statistics.html b/public_html/as-IN/Site_Statistics.html
index 9fdb6ed..183c8cd 100644
--- a/public_html/as-IN/Site_Statistics.html
+++ b/public_html/as-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 9e74666..5f5a1d3 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:27</updated>
+ <updated>2013-03-15T15:09:59</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 3a3eb7f..7c40ded 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>2013-03-15T14:21:27</updated>
+ <updated>2013-03-15T15:10:00</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 bb8b51d..513f416 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:27</updated>
+ <updated>2013-03-15T15:10:00</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 e067d1f..6ff5578 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>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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 3da589d..3f7061a 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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 f159ad6..16866dd 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index 4736981..4b600a0 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>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:27</updated>
+ <updated>2013-03-15T15:09:59</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>2013-03-15T14:21:27</updated>
+ <updated>2013-03-15T15:10:00</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:27</updated>
+ <updated>2013-03-15T15:10:00</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.xml</id>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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 9fdb6ed..183c8cd 100644
--- a/public_html/bg-BG/Site_Statistics.html
+++ b/public_html/bg-BG/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 003b56a..466c2fe 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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 aab43d2..09595c1 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>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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 327b2d6..1fa0d14 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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 645266e..a7cb975 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>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:01</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 a1a1497..a0544b9 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:01</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 ab4a073..49c209f 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 0af8f25..25106ad 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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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.xml</id>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:01</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 9fdb6ed..183c8cd 100644
--- a/public_html/bn-IN/Site_Statistics.html
+++ b/public_html/bn-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 63b238a..9eed558 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 75cece9..b68eb53 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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 0dd49fc..2d2b62f 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 dddbe9c..1b17a2e 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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 c9922f2..91112d5 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 4156c77..51a4205 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index 56aaccd..a4f20f8 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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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.xml</id>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 9fdb6ed..183c8cd 100644
--- a/public_html/bs-BA/Site_Statistics.html
+++ b/public_html/bs-BA/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 22b5f71..e823255 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 208fb24..c3e22af 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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 255dc82..baa998c 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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 067bcf4..b7cd46f 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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:01</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 404d90a..fcf357f 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:01</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 0da54ad..5afa017 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:01</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index dc96d15..24daa45 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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:01</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:01</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.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:01</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:01</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:01</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 9fdb6ed..183c8cd 100644
--- a/public_html/ca-ES/Site_Statistics.html
+++ b/public_html/ca-ES/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 a12dd9c..48a8f70 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 ac9b0cb..979267c 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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 216ae9a..98be304 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 ec88f22..33a63ad 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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 6d5393d..3cdfc84 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 12335c2..9f046b4 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index 02bca1c..63e212e 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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 9fdb6ed..183c8cd 100644
--- a/public_html/cs-CZ/Site_Statistics.html
+++ b/public_html/cs-CZ/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 dea6175..1bfc004 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 b005464..b4450e1 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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 b652a15..5ac39f1 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 ea69c89..0033465 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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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 be30397..46c373b 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:03</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 c2178de..3eae1b0 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:03</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index df8ab3f..f3c6fe5 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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:03</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:03</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:03</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 9fdb6ed..183c8cd 100644
--- a/public_html/da-DK/Site_Statistics.html
+++ b/public_html/da-DK/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 4962de0..6e8e582 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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 d393d63..f11bf19 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>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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 612cb2d..097476e 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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 478e95a..025d019 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>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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 4a34dee..aafacaa 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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 e977a89..d4f2c38 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index 09dce8a..75516b4 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>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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.xml</id>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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 ac9ebdd..3fe1461 100644
--- a/public_html/de-DE/Site_Statistics.html
+++ b/public_html/de-DE/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Sprachen gesamt: </b>44<br />
- <b>Pakete gesamt: </b>851
+ <b>Pakete gesamt: </b>852
</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 44df687..b9e5112 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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 125c2b8..680c5d6 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>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 c7c7563..1052c80 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 0461bc9..da82360 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>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 e38008a..943ce02 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 79616bd..9e75f4e 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index 0ce9469..e76d96b 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>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 9fdb6ed..183c8cd 100644
--- a/public_html/el-GR/Site_Statistics.html
+++ b/public_html/el-GR/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 73f354f..7a0ae45 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 41400a4..445a170 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>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 c58e95e..7f78f07 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 e7f71a3..9f93cf9 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>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 a114267..8c565f4 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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 c8896e0..291e20c 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:05</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index 681b90a..df8dfc3 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>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:05</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:05</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 9fdb6ed..183c8cd 100644
--- a/public_html/en-US/Site_Statistics.html
+++ b/public_html/en-US/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 83b1720..6a40b1a 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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 eca90b3..4c681e6 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>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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 3e4e78d..94d3d3f 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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 a4846a7..ad6ddfd 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>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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 7a701b8..d6bb1ca 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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 c806b1d..dddd443 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds.xml b/public_html/en-US/opds.xml
index 075bf04..1987ba5 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>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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.xml</id>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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 762caf7..e5b4820 100644
--- a/public_html/es-ES/Site_Statistics.html
+++ b/public_html/es-ES/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Idiomas totales: </b>44<br />
- <b>Paquetes totales: </b>851
+ <b>Paquetes totales: </b>852
</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 7612b39..a519e9d 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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 47760b6..f0512db 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>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_15.xml b/public_html/es-ES/opds-Fedora_15.xml
index e90bd87..78999bd 100644
--- a/public_html/es-ES/opds-Fedora_15.xml
+++ b/public_html/es-ES/opds-Fedora_15.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_15.xml</id>
<title>Fedora 15</title>
<subtitle>Fedora 15</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 5ca8d60..378de6d 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_Documentation.xml</id>
<title>Fedora Documentación de Contribuyente</title>
<subtitle>Fedora Documentación de Contribuyente</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 4487c1b..a73785f 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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 61f9452..2a2587f 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 c2b8340..ae7d486 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds.xml b/public_html/es-ES/opds.xml
index 32e4fd2..63700c6 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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 15</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_15/opds-Fedora_15.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_15.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Documentación de Contribuyente</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 9fdb6ed..183c8cd 100644
--- a/public_html/fa-IR/Site_Statistics.html
+++ b/public_html/fa-IR/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 0c7bbd6..7b0c644 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 be385ae..31f52c9 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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 a995521..6f7f069 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_Documentation.xml</id>
<title>مستندات مشارکت کننده فدورا</title>
<subtitle>مستندات مشارکت کننده فدورا</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 1f346ad..ca350a5 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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 5a9edf9..7696b85 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 84f838c..42d25b4 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds.xml b/public_html/fa-IR/opds.xml
index 628d209..b7036b7 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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:07</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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 9fdb6ed..183c8cd 100644
--- a/public_html/fi-FI/Site_Statistics.html
+++ b/public_html/fi-FI/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 6fe0870..95399a9 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:07</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 070dc85..bcfe893 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>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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 c68b9c4..ce7c134 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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 4d0521b..cc0bf61 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>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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 d5dea76..c3a12b3 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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 3f82f80..4d7abfb 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds.xml b/public_html/fi-FI/opds.xml
index ae3fa7f..3616d71 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>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:07</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>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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.xml</id>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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 9fdb6ed..183c8cd 100644
--- a/public_html/fr-FR/Site_Statistics.html
+++ b/public_html/fr-FR/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 f631c1a..98c85c5 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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 cb13019..adac561 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>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</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 e1609e4..f5ffcba 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</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 e6c67d7..1ff13c2 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>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</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 950d3e4..2f5cf2f 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</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 c2b75e6..7224a8d 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds.xml b/public_html/fr-FR/opds.xml
index 72a1f8b..e4721dd 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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</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.xml</id>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:08</updated>
<dc:language>fr-FR</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/fr-FR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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 9fdb6ed..183c8cd 100644
--- a/public_html/gu-IN/Site_Statistics.html
+++ b/public_html/gu-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 b12a0ab..f481c98 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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 e2757f6..1500617 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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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 5203263..6309587 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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 5339310..b3f0d07 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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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 746a841..26cdc15 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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 ed59f6c..edeec1e 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds.xml b/public_html/gu-IN/opds.xml
index 3b1365d..127933b 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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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 9fdb6ed..183c8cd 100644
--- a/public_html/he-IL/Site_Statistics.html
+++ b/public_html/he-IL/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 6347944..a7202eb 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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 ad7d777..e86ec33 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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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 06a1b39..f2bd878 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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 8b52bd8..8d489f7 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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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 2ae55e8..143b0c6 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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 ac20843..a914a55 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds.xml b/public_html/he-IL/opds.xml
index c47e183..f8c17ee 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>2013-03-15T14:21:37</updated>
+ <updated>2013-03-15T15:10:10</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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 9fdb6ed..183c8cd 100644
--- a/public_html/hi-IN/Site_Statistics.html
+++ b/public_html/hi-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 b083cb0..fe6a7ae 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:37</updated>
+ <updated>2013-03-15T15:10:10</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 510e30f..0820bb7 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>2013-03-15T14:21:37</updated>
+ <updated>2013-03-15T15:10:10</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 120d4fa..8240056 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:37</updated>
+ <updated>2013-03-15T15:10:10</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 e7b839e..84f5caf 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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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 1e1a6ad..90cfe99 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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 489720d..9365ec0 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds.xml b/public_html/hi-IN/opds.xml
index 73b0fa7..3bfa618 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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:37</updated>
+ <updated>2013-03-15T15:10:10</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>2013-03-15T14:21:37</updated>
+ <updated>2013-03-15T15:10:10</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:37</updated>
+ <updated>2013-03-15T15:10:10</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.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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 9fdb6ed..183c8cd 100644
--- a/public_html/hu-HU/Site_Statistics.html
+++ b/public_html/hu-HU/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 82c8bca..e0d35bb 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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 7b1b0fb..c97b4f9 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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10: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 b058d0d..c36a792 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10: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 1ae8f66..495c4ae 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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10: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 56fba76..52e4cb2 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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 915d6b4..f2ba0b6 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds.xml b/public_html/hu-HU/opds.xml
index 80e28b1..046d57f 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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10: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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10: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.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10: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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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 9fdb6ed..183c8cd 100644
--- a/public_html/ia/Site_Statistics.html
+++ b/public_html/ia/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</div>
</body>
</html>
diff --git a/public_html/ia/opds-Community_Services_Infrastructure.xml b/public_html/ia/opds-Community_Services_Infrastructure.xml
index e8bfbbd..3328907 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora.xml b/public_html/ia/opds-Fedora.xml
index dfd1b2d..691954a 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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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 2fb8bb8..8ec97ad 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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 ba739c6..e07ef6b 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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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 3ed5fe8..2d481db 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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 682719b..99ab661 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds.xml b/public_html/ia/opds.xml
index 19cec32..26c8feb 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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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_Security_Team.xml</id>
- <updated>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:11</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 9fdb6ed..183c8cd 100644
--- a/public_html/id-ID/Site_Statistics.html
+++ b/public_html/id-ID/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 cad6bb9..7a10361 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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 2a9ff59..620e712 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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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 73e5b86..d72ab61 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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 64c8545..c9e5c9d 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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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 ea0e337..ae50bdf 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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 33ebf90..5aed5d9 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds.xml b/public_html/id-ID/opds.xml
index 4a585c9..f7bd965 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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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 9fdb6ed..183c8cd 100644
--- a/public_html/it-IT/Site_Statistics.html
+++ b/public_html/it-IT/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 146f8b0..67fbc24 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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 3341871..367f056 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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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 5010b26..5ae9842 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_Documentation.xml</id>
<title>Documentazione Collaboratori Fedora</title>
<subtitle>Documentazione Collaboratori Fedora</subtitle>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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 e56baa5..51933ae 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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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 f09d5c9..193abc1 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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 ddac892..1bd9394 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds.xml b/public_html/it-IT/opds.xml
index be1207a..b190a99 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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:12</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:12</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/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.epub b/public_html/ja-JP/Fedora/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.epub
new file mode 100644
index 0000000..d6e0972
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.epub differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/css/common.css b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/css/default.css b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/css/lang.css b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/css/overrides.css b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/css/print.css b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/1.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/1.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/10.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/10.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/10.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/11.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/11.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/11.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/12.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/12.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/12.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/13.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/13.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/13.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/14.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/14.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/14.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/15.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/15.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/15.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/16.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/16.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/16.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/17.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/17.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/17.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/18.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/18.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/18.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/19.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/19.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/19.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/2.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/2.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/2.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/20.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/20.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/20.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/21.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/21.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/21.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/22.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/22.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/22.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/23.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/23.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/23.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/24.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/24.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/24.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/25.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/25.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/25.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/26.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/26.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/26.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/27.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/27.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/27.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/28.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/28.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/28.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/29.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/29.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/29.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/3.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/30.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/30.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/30.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/31.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/31.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/31.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/32.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/32.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/32.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/33.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/33.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/33.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/34.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/34.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/34.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/35.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/35.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/35.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/36.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/36.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/36.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/37.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/37.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/37.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/38.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/38.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/38.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/39.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/39.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/39.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/4.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/4.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/4.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/40.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/40.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/40.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/5.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/5.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/5.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/6.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/6.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/6.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/7.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/7.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/7.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/8.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/8.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/8.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/9.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/9.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/9.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/documentation.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/dot.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/dot2.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/green.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/green.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/h1-bg.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/image_left.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/image_right.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/important.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/important.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/important.svg b/public_html/ja-JP/Fedora/17/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/17/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"
+ 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/17/html-single/System_Administrators_Guide/Common_Content/images/logo.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/note.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/note.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/note.svg b/public_html/ja-JP/Fedora/17/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/17/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"
+ 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/17/html-single/System_Administrators_Guide/Common_Content/images/red.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/red.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/shade.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/shine.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/stock-go-back.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/stock-go-forward.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/stock-go-up.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/stock-home.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/title_logo.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/title_logo.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/warning.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/warning.svg b/public_html/ja-JP/Fedora/17/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/17/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"
+ 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/17/html-single/System_Administrators_Guide/Common_Content/images/watermark-draft.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/Common_Content/images/yellow.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Editing-VPN-connection-1.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Editing-VPN-connection-1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-AppletStates_Gnome3.png b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-AppletStates_Gnome3.png
new file mode 100644
index 0000000..b451eb2
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-AppletStates_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-alert.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-alert.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-applet_setting.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-applet_setting.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-applet_setting2.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-applet_setting2.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-event-configuration.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-event-configuration.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_access.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_access.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_backtrace_review.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_backtrace_review.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_event_configuration.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_event_configuration.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_main_screen.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_main_screen.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_problem_description.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_problem_description.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_report_confirmation.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_report_confirmation.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_select_analyzer.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_select_analyzer.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt-gui_select_reporter.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt-gui_select_reporter.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/abrt.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/abrt.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/add-remove-software-filters-available.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/add-remove-software-filters-available.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/add-remove-software-filters-end-user.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/add-remove-software-filters-end-user.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/add-remove-software-install.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/add-remove-software-install.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/add-remove-software-log.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/add-remove-software-log.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/add-remove-software-package-group.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/add-remove-software-package-group.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/add-remove-software-remove.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/add-remove-software-remove.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/add-remove-software.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/add-remove-software.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/authconfig_LDAP_kerb.png b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/authconfig_LDAP_kerb.png
new file mode 100644
index 0000000..7268d86
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/authconfig_LDAP_kerb.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/authconfig_advanced.png b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/authconfig_advanced.png
new file mode 100644
index 0000000..53ddd7c
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/authconfig_advanced.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/date-and-time-settings.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/date-and-time-settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/devicemngr.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/devicemngr.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/gnome-print-queue.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/gnome-print-queue.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/hwbrowser.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/hwbrowser.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/oprof-start-config.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/oprof-start-config.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/oprof-start-setup.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/oprof-start-setup.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/print_conf_window.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/print_conf_window.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-add-printer.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-add-printer.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-config1.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-config1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-config2.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-config2.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-config3.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-config3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-config4.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-config4.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-config5.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-config5.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-config6.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-config6.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-ipp.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-ipp.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-jetdirect.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-jetdirect.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-lpd.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-lpd.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-main.png b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-main.png
new file mode 100644
index 0000000..dfd18c4
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-main.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-select-driver.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-select-driver.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-select-model.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-select-model.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/printconf-smb.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/printconf-smb.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/region-and-language-formats-add.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/region-and-language-formats-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/region-and-language-formats.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/region-and-language-formats.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/region-and-language-language-add.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/region-and-language-language-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/region-and-language-language.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/region-and-language-language.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/region-and-language-layouts-add.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/region-and-language-layouts-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/region-and-language-layouts-indicator.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/region-and-language-layouts-indicator.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/region-and-language-layouts.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/region-and-language-layouts.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/region-and-language-system.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/region-and-language-system.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/s-c-samba-basic.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/s-c-samba-basic.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/s-c-samba-create-share.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/s-c-samba-create-share.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/s-c-samba-security.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/s-c-samba-security.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/s-c-samba-users.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/s-c-samba-users.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/s-c-samba.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/s-c-samba.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/samba-nautilus-domain.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/samba-nautilus-domain.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/software-update-preferences.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/software-update-preferences.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/software-update-software-sources.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/software-update-software-sources.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/software-update.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/software-update.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/ssh-passphrase-prompt.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/ssh-passphrase-prompt.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/ssh-startup-applications-add.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/ssh-startup-applications-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/ssh-startup-applications-check.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/ssh-startup-applications-check.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/ssh-startup-applications.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/ssh-startup-applications.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/switchmail-gui.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/switchmail-gui.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-log-viewer-add.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-log-viewer-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-log-viewer-alerts.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-log-viewer-alerts.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-log-viewer-filters-define.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-log-viewer-filters-define.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-log-viewer-filters-enable.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-log-viewer-filters-enable.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-log-viewer-filters-manage.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-log-viewer-filters-manage.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-log-viewer.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-log-viewer.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-monitor-file-systems.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-monitor-file-systems.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-monitor-processes.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-monitor-processes.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/system-monitor-resources.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/system-monitor-resources.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-accounts-create.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-accounts-create.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-accounts-password-change.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-accounts-password-change.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-accounts-remove.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-accounts-remove.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-accounts.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-accounts.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-manager-add-group.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-manager-add-group.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-manager-add-user.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-manager-add-user.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-manager-edit-group.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-manager-edit-group.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-manager-edit-user.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-manager-edit-user.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/images/user-manager.png b/public_html/ja-JP/Fedora/17/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/17/html-single/System_Administrators_Guide/images/user-manager.png differ
diff --git a/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/index.html b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/index.html
new file mode 100644
index 0000000..c1c1b70
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html-single/System_Administrators_Guide/index.html
@@ -0,0 +1,15759 @@
+<?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-17-ja-JP-1-0" /><meta name="description" content="システム管理者ガイドは、Fedora 17 の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm111286080" 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">17</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm111286080" class="title">システム管ç†è€…ガイã
ƒ‰</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Fedora 17 ã®å°Žå…¥ã€è¨å®šãŠã‚ˆã³ç®¡ç†</h2></div><p class="edition">エディッション 1</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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:jhradilek at redhat.com">jhradilek at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:silas at redhat.com">silas at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="surname">Prpič</span> <s
pan class="firstname">Martin</span> [FAMILY Given]</h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mprpic at redhat.com">mprpic at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:swadeley at redhat.com">swadeley at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:eslobodo at redh
at.com">eslobodo at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:tcapek at redhat.com">tcapek at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:pkovar at redhat.com">pkovar at 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, Inc.</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, Inc.</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, Inc.</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, Inc.</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="idm1002
35408" class="legalnotice"><h1 class="legalnotice">法律上の通知</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2012 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://creativecommons.org/licenses/by-sa/3.0/</a>. 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">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </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 17 の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#idm81962928">序文</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="#idm131549856">3. 表記方法</a></span></dt><dd><dl><dt><span class="section"><a href="#idm118497712">3.1. 印刷における表記方法</a></span></dt><dt><span class="section"><a href="#idm131547248">3.2. 引用における表記方法</a></span></dt><dt><span class="section"><a href="#idm112170144">3.3. 注記および警告</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Preface-Feedback">4. フィードバック</a></span></dt><dt><span class="section"><a href="#pref-Acknowledgments">5. Acknowledgments</a></span></dt></dl></dd><dt><span class="part"><a href="#part-Basic_Syste
m_Configuration">I. 基本的なシステム設定</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Configuring_the_Language_and_Keyboard">1. 言語とキーボードの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Language">1.1. 言語の変更</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Formats">1.2. 日付、時刻および数字の形式の変更</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Layouts">1.3. キーボードのレイアウト変更</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-System">1.4. 現在の設定の表示</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_the_Date_and_Time">2. 日付と時刻の設定</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Date_and_Time
">2.1. 日付と時刻の設定ツールの使い方</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration">2.2. コマンドラインツールの使用</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">2.2.1. 日付の変更方法</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time">2.2.2. 時刻の変更方法</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">2.2.3. Network Time Protocol の設定</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Additional_Resources">2.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Additional_Resources-Installed_Documentation">2.3.1. イ
ンストールされているドキュメント</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Managing_Users_and_Groups">3. ユーザーとグループの管理</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-groups-introduction">3.1. ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">3.1.1. ユーザープライベートグループ</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">3.1.2. シャドウパスワード</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts">3.2. ユーザー アカウントのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.2.1. アカウントの設定</a></span></dt><dt><span class="section"><a href="#sect-Managing
_Users_and_Groups-User_Accounts-Adding_a_New_User">3.2.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.2.3. ユーザーの削除</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">3.3. ユーザー管理のツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-list">3.3.1. ユーザーとグループを閲覧する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-user-new">3.3.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-new">3.3.3. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-user-properties">3.3.4. ユーザーのプロパティを変更する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-properties">3.3.5
. グループのプロパティを変更する</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">3.4. コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-tools-users-add">3.4.1. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">3.4.2. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">3.4.3. パスワードエージングの有効化</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">3.4.4. 自動ログアウトの有効化</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">3.4.5. グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-additional-resources">3.5. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><
a href="#s2-users-groups-documentation">3.5.1. インストールされているドキュメント</a></span></dt></dl></dd></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-yum">4. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">4.1. パッケージの確認と更新</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">4.1.1. 更新の確認</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">4.1.2. パッケージの更新</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">4.1.3. 設定ファイル変更の保存</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">4.2. パッケージとパッケージ グループ</a></span></dt><dd><dl><dt><span class="section"><a hr
ef="#sec-Searching_Packages">4.2.1. パッケージの検索</a></span></dt><dt><span class="section"><a href="#sec-Listing_Packages">4.2.2. パッケージの一覧</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Package_Information">4.2.3. パッケージ情報の表示</a></span></dt><dt><span class="section"><a href="#sec-Installing">4.2.4. パッケージのインストール</a></span></dt><dt><span class="section"><a href="#sec-Removing">4.2.5. パッケージの削除</a></span></dt><dt><span class="section"><a href="#sec-Yum-Transaction_History">4.2.6. 処理とトランザクションの履歴</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">4.3. Yum と Yum リポジトリーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">4.3.1. [main] オプションの設定</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">4.3.2
. [repository] オプションの設定</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">4.3.3. Yum 変数の使い方</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Current_Configuration">4.3.4. 現在の設定の表示</a></span></dt><dt><span class="section"><a href="#sec-Managing_Yum_Repositories">4.3.5. Yum リポジトリの追加・有効化および無効化</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">4.3.6. Yum リポジトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">4.4. Yum プラグイン</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Yum プラグインの無効化、有効化、設定</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">4.4.2. 追加の Yum プラグインのインストール</a></span></dt><dt><span class="sect
ion"><a href="#sec-Plugin_Descriptions">4.4.3. プラグインの説明</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Additional_Resources">4.5. その他のリソース</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-PackageKit">5. PackageKit</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Updating_Packages_with_Software_Update">5.1. ソフトウェアの更新を用いたパッケージの更新</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_preferences_for_checking_for_updates">5.1.1. 更新の確認間隔の設定</a></span></dt><dt><span class="section"><a href="#sec-Setting_preferences_for_software_sources">5.1.2. ソフトウェアソースの設定</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_Add_Remove_Software">5.2. ソフトウェアの追加/削除の使用</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Refreshing_Software_Sources_Yum_Repositories">
5.2.1. ソフトウェアソースの更新 (Yum リポジトリー)</a></span></dt><dt><span class="section"><a href="#sec-Finding_Packages_with_Filters">5.2.2. フィルターを用いたパッケージの検索</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Packages_and_Dependencies">5.2.3. パッケージ（および依存するもの）のインストールおよび削除</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Package_Groups">5.2.4. パッケージグループのインストールおよび削除</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Transaction_Log">5.2.5. トランザクションログの表示</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-PackageKit_Architecture">5.3. PackageKit アーキテクチャー</a></span></dt><dt><span class="section"><a href="#ch-Graphical_Package_Management-sec-Additional_Resources">5.4. その他のリソース</a></span>
</dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Networking">III. ネットワーク</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-NetworkManager">6. NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-The_NetworkManager_Daemon">6.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">6.2. Interacting with NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network">6.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connections">6.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automatically">6.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="#sec-User_and_System_Connections">6.2.4. User and System Connections</a></span>
</dt></dl></dd><dt><span class="section"><a href="#sec-Establishing_Connections">6.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Wired_Ethernet_Connection">6.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Wireless_Connection">6.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">6.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">6.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">6.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_Routes">6.3.6. Establishing Routes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Connection_Sett
ings">6.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_802.1x_Security">6.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Wireless_Security">6.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_PPP_Point-to-Point_Settings">6.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv4_Settings">6.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_Settings">6.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-NetworkManager_Architecture">6.5. NetworkManager Architecture</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Network_Interfaces">7. ネットワーク・インターフェース</a></span></dt><dd><dl><dt><span class="section"><a href="#s1
-networkscripts-files">7.1. ネットワーク設定ファイル</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-interfaces">7.2. インターフェース設定ファイル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-networkscripts-interfaces-eth0">7.2.1. イーサネット インターフェース</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-chan">7.2.2. チャンネル・ボンディング・インターフェース</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces_network-bridge">7.2.3. ネットワークブリッジ</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces_802.1q-vlan-tagging">7.2.4. Setting up 802.1q VLAN tagging</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-alias">7.2.5. エイリアス ファイルとクローン ファイル</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-
interfaces-ppp0">7.2.6. ダイヤルアップ インターフェース</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-other">7.2.7. 他のインターフェース</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-networkscripts-control">7.3. インターフェース制御スクリプト</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-static-routes">7.4. スタティック ルートの設定</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-functions">7.5. ネットワーク機能ファイル</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-resources">7.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-networkscripts-docs-inst">7.6.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#part-Infrastructure_Services">IV. インフラストラクチャーサ
ービス</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Services_and_Daemons">8. サービスおよびデーモン</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-configuring">8.1. サービスの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">8.1.1. サービスの有効化</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">8.1.2. サービスの無効化</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">8.2. サービスの実行</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">8.2.1. サービスの状態の確認</a></span></dt><dt><span class="section"><a href="#s3-services-running-running">8.2.2. サービスの実行</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">8.2.3. サービスの停止</a></span></dt><dt><span class="section"><a h
ref="#s3-services-running-restarting">8.2.4. サービスの再起動</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">8.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">8.3.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">8.3.2. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_Authentication">9. 認証の設定</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">9.1. 認証の設定ツール</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">9.1.1. 識別と認証</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">9
.1.2. 高度なオプション</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">9.1.3. コマンドライン版</a></span></dt></dl></dd><dt><span class="section"><a href="#chap-SSSD_User_Guide-Introduction">9.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-What_is_SSSD">9.2.1. SSIDとは?</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">9.2.2. SSIDの特徴</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Setting_Up_SSSD">9.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Services">9.2.4. サービスの設定</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Domains">9.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="#sect-SSSD_Use
r_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">9.2.6. Setting Up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">9.2.7. Configuring a Proxy Domain</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Troubleshooting">9.2.8. トラブルシューティング</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">9.2.9. SSSD Configuration File Format</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">10. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">10.1. SSH プロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">10.1.1. なぜ SSH を使うのか？</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">10.1.2. 主な機能</a></span></dt><dt><
span class="section"><a href="#s2-ssh-versions">10.1.3. プロトコル・バージョン</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">10.1.4. SSH コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">10.2. OpenSSH の設定</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">10.2.1. 設定ファイル</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-sshd">10.2.2. OpenSSH サーバーの起動</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">10.2.3. リモート接続に対する SSH の要求</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">10.2.4. キー認証の使用</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">10.3. OpenSSH クライアント</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-
ssh">10.3.1. ssh ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">10.3.2. <code class="command">scp</code> ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">10.3.3. <code class="command">sftp</code> ユーティリティの使用方法</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">10.4. 安全なシェル以上のもの</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">10.4.1. X11 転送</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">10.4.2. ポート転送</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">10.5. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-openssh-installed-docs">10.5.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a
href="#s2-openssh-useful-websites">10.5.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#part-Servers">V. サーバー</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-DHCP_Servers">11. DHCP サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-dhcp-why">11.1. DHCP を使用する理由</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-server">11.2. DHCP サーバーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">11.2.1. 設定ファイル</a></span></dt><dt><span class="section"><a href="#lease-database">11.2.2. リースデータベース</a></span></dt><dt><span class="section"><a href="#idm122588480">11.2.3. サーバーの起動と停止</a></span></dt><dt><span class="section"><a href="#dhcp-relay-agent">11.2.4. DHCP リレーエージェント</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp-configurin
g-client">11.3. DHCP クライアントã®è¨å®š</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server">11.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-dns_Host_Configuration">11.4.1. ホストã®è¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">11.5. IPv6 å‘ã‘ DHCP (DHCPv6)</a></span></dt><dt><span class="section"><a href="#s1-dhcp-additional-resources">11.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dhcp-installed-docs">11.6.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-DNS_Servers">12. DNS サーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Introduction_to_DNS">12.1. DNS ã®æ¦‚è¦</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dns-introduction-zones">12.1.1. ãƒãƒ¼ãƒ ã
‚µãƒ¼ãƒãƒ¼ã‚¾ãƒ¼ãƒ³</a></span></dt><dt><span class="section"><a href="#s2-dns-introduction-nameservers">12.1.2. ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚¤ãƒ—</a></span></dt><dt><span class="section"><a href="#s2-dns-introduction-bind">12.1.3. ãƒãƒ¼ãƒ サーãƒãƒ¼ã¨ã—ã¦ã® BIND</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-BIND">12.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-namedconf">12.2.1. named サービスã®è¨å®š</a></span></dt><dt><span class="section"><a href="#s2-bind-zone">12.2.2. ゾーンファイルã®ç·¨é›†</a></span></dt><dt><span class="section"><a href="#s2-bind-rndc">12.2.3. rndc ユーティリティã®ä½¿ç”¨æ³•</a></span></dt><dt><span class="section"><a href="#s2-bind-dig">12.2.4. dig ユーティリティã®ä½¿ç”¨</a></span></dt><dt><span class="section"><a href="#s2-bind-features">12.2.5. BIND ã®é«˜åº¦ãªæ©Ÿèƒ½</a></span></dt><dt><span class="section"><a href="#s2-bind-mistakes">12.2.6. よãã‚ã‚‹é–“é•ã„ã
‚’é¿ã‘ã‚‹ãŸã‚ã«</a></span></dt><dt><span class="section"><a href="#s2-bind-additional-resources">12.2.7. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Web_Servers">13. ウェブ サーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-The_Apache_HTTP_Server">13.1. Apache HTTP サーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-version2-features">13.1.1. 新機能</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-changes">13.1.2. 注目ã™ã¹ã変更</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">13.1.3. è¨å®šã®æ›´æ–°</a></span></dt><dt><span class="section"><a href="#s2-apache-running">13.1.4. httpd サービスã®å®Ÿè¡Œæ–¹æ³•</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">13.1.5. è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®ç·¨é›†</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">13.1.6. Working wit
h Modules</a></span></dt><dt><span class="section"><a href="#s2-apache-virtualhosts">13.1.7. 仮想ホストのセットアップ</a></span></dt><dt><span class="section"><a href="#s2-apache-mod_ssl">13.1.8. SSL サーバーのセットアップ</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">13.1.9. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Mail_Servers">14. メールサーバー</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">14.1. 電子メールプロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protocols-send">14.1.1. メール トランスポートのプロトコル</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">14.1.2. メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">14.2. 電子メールプログラム分類</a></span></dt><dd>
<dl><dt><span class="section"><a href="#s2-email-types-mta">14.2.1. メール転送エージェント (Mail Transport Agent)</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">14.2.2. メール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">14.2.3. メール ユーザー エージェント</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mta">14.3. Mail Transport Agent</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-postfix">14.3.1. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-sendmail">14.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">14.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="#s2-email-switchmail">14.3.4. Mail Transport Agent (MTA) の設定</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mda">14.4. メール配送エージェ
ント</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">14.4.1. Procmail の設定</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">14.4.2. Procmail レシピ</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">14.5. メールユーザーエージェント</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">14.5.1. 通信のセキュリティ</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">14.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">14.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">14.6.2. 役に立つ Web サイト</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">14.6.3. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span cla
ss="chapter"><a href="#ch-Directory_Servers">15. ディレクトリー サーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-OpenLDAP">15.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">15.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">15.1.2. OpenLDAP 製å“群ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">15.1.3. OpenLDAP サーãƒãƒ¼ã®è¨å®šæ³•</a></span></dt><dt><span class="section"><a href="#s2-ldap-running">15.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">15.1.5. システム㌠OpenLDAP を使用ã—ã¦èªè¨¼ã‚’実行ã™ã‚‹ã‚ˆã†ã«è¨å®šã™ã‚‹</a></span></dt><dt><span class="section"><a href="#s2-ldap-resources">15.1.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-File_and_Print_Servers">16. ファã‚
¤ãƒ«ã‚µãƒ¼ãƒãƒ¼ãŠã‚ˆã³ãƒ—リントサーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Samba">16.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">16.1.1. Samba ã®æ¦‚è¦</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">16.1.2. Samba デーモンã¨é–¢é€£ã‚µãƒ¼ãƒ“ス</a></span></dt><dt><span class="section"><a href="#s2-samba-connect-share">16.1.3. Samba シェアã¸ã®æŽ¥ç¶š</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">16.1.4. Samba サーãƒãƒ¼ã®è¨å®š</a></span></dt><dt><span class="section"><a href="#s2-samba-startstop">16.1.5. Samba ã®é–‹å§‹ã¨åœæ¢</a></span></dt><dt><span class="section"><a href="#s2-samba-servers">16.1.6. Samba サーãƒãƒ¼å½¢å¼ã¨ <code class="filename">smb.conf</code> ファイル</a></span></dt><dt><span class="section"><a href="#s2-samba-security-modes">16.1.7. Samba ã®ã‚»ã‚ュリティモード</a></span></dt><dt><span class="sect
ion"><a href="#s2-samba-account-info-dbs">16.1.8. Samba のアカウント情報データベース</a></span></dt><dt><span class="section"><a href="#s2-samba-network-browsing">16.1.9. Samba ネットワークブラウジング</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">16.1.10. CUPS 印刷サポートを使った Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">16.1.11. Samba ディストリビューションプログラム</a></span></dt><dt><span class="section"><a href="#s2-samba-resources">16.1.12. その他のリソース</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">16.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol">16.2.1. ファイル伝送プロトコル</a></span></dt><dt><span class="section"><a href="#s2-ftp-servers">16.2.2. FTP サーバー</a></span></dt><dt><span class="section"><a href="#s3-ftp-vsftpd-conf">16.2.3. Files Installed with <code class="com
mand">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-start">16.2.4. <code class="command">vsftpd</code> の開始と停止</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">16.2.5. <code class="command">vsftpd</code> 設定オプション</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">16.2.6. その他のリソース</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration">16.3. プリンタの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">16.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="#sec-Setting_Printer">16.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="#sec-Adding_Other_Printer">16.3.3. ローカルプリンタの追加</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">16.3.4. Adding an AppSocket/HP JetDire
ct printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">16.3.5. IPP プリンタの追加</a></span></dt><dt><span class="section"><a href="#sec-printing-LPDLPR-printer">16.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">16.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">16.3.8. プリンタモデルの選択と終了</a></span></dt><dt><span class="section"><a href="#s1-printing-test-page">16.3.9. Printing a test page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">16.3.10. 既存プリンタの変更</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">16.3.11. その他のリソース</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#part-Monitoring_and_Automation">VI. 監視および自動化</a></span></dt><dd><dl><dt><span class="c
hapter"><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. 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-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-configuring-rsyslog">18.1. rsyslog の設定法</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-global-directives">18.1.1. 全体ディレクティブ</a></span></dt><dt><span class="section"><a href="#s2-modules">18.1.2. モジュール</a></span></dt><dt><span class="section"><a href="#s2-rules">18.1.3. ルール</a></span></dt><dt><span class="section"><a href="#s2-rsyslog-cmd-options">18.1.4. <span class="application"><strong>rsyslog</strong></span> コマンドライン設定</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-logfiles-locating">18.2. ログファイルを探す</a></span></dt><dd><dl><dt><span class="section"><a href="#configuring-logrotate">18.2.1. logrotate の設定法</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-logfiles-viewing">18.3. ログファイルの表示</a></span></dt><dt><span class="section"><a href="#s1-logfiles-adding">18.4. ログファイルの追加</a></span></dt><dt><span cl
ass="section"><a href="#s1-logfiles-examining">18.5. ログファイルを監視する</a></span></dt><dt><span class="section"><a href="#s1-log-files-additional-resources">18.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-log-files-installed-docs">18.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-log-files-useful-websites">18.6.2. 役に立つ Web サイト</a></span></dt></dl></dd></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="#s2-autotasks-cron-service">19.1.1. サービスの起動と停止</a></span></dt><dt><span class="section"><a href="#s2-configuring-anacron-jobs">19.1.2. Configuring Anacron Jobs</a></span></dt><dt><span class=
"section"><a href="#s2-configuring-cron-jobs">19.1.3. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">19.1.4. Cron へのアクセスの制御</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-cron-jobs">19.1.5. Black/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="#s2-autotasks-at-configuring">19.2.1. At ジョブの設定</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">19.2.2. batch ジョブの設定</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">19.2.3. 保留ジョブの表示</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">19.2.4. その他のコマンドラインオプション</a></span></dt><dt><span class="section"><a hre
f="#s2-autotasks-at-batch-controlling-access">19.2.5. at と batch へのアクセスの制御</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-service">19.2.6. サービスの起動と停止</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">19.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-installed-docs">19.3.1. インストールされているドキュメント</a></span></dt></dl></dd></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><dt><span class="section"><a href="#s1-oprofile-configuring">20.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">20.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">20.2.2.
Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">20.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">20.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">20.4. Saving Data</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">20.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">20.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">20.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">20.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">20.5.4. Using <code cla
ss="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">20.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">20.7. 使用法の例</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">20.8. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">20.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">20.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-and-systemtap">20.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">20.11. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-installed-docs">20.11.1. Installed Docs</a></span></dt><dt><span class="section"><a
href="#s2-oprofile-useful-websites">20.11.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#part-Kernel_Module_and_Driver_Configuration">VII. カーネル、モジュールおよびドライバーの設定</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Manually_Upgrading_the_Kernel">21. カーネルをアップグレードする</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-packages">21.1. カーネルパッケージの概要</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">21.2. アップグレードの準備</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">21.3. アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">21.4. アップグレードの実行</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image
">21.5. 初期RAMディスクイメージの確認</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">21.6. ブートローダの確認</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-kernel-boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-iseries">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">21.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">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section">
<a href="#sec-Loading_a_Module">22.3. モジュールの読み込み方法</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#sec-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#sec-Specific_Kernel_Module_Capabilities">22.7. Specific Kernel Module Capabilities</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Using_Multiple_Ethernet_Cards">22.7.1. 複数のイーサネットカードの使用</a></span></dt><dt><span class="section"><a href="#sec-Using_Channel_Bonding">22.7.2. Using Channel Bonding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ke
rnel-modules-additional-resources-installed">22.8.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-kernel-modules-additional-resources-websites">22.8.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-kdump">23. The kdump Crash Recovery Service</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kdump-installation">23.1. Installing the kdump Service</a></span></dt><dt><span class="section"><a href="#s1-kdump-configuration">23.2. Configuring the kdump Service</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kdump-configuration-firstboot">23.2.1. Configuring the kdump at First Boot</a></span></dt><dt><span class="section"><a href="#s2-kdump-configuration-gui">23.2.2. Using the Kernel Dump Configuration Utility</a></span></dt><dt><span class="section"><a href="#s2-kdump-configuration-cli">23.2.3. Configuring kdump on the Command Line</a></span>
</dt><dt><span class="section"><a href="#s2-kdump-configuration-testing">23.2.4. Testing the Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kdump-crash">23.3. Analyzing the Core Dump</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kdump-crash-running">23.3.1. Running the crash Utility</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-log">23.3.2. Displaying the Message Buffer</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-backtrace">23.3.3. Displaying a Backtrace</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-processes">23.3.4. Displaying a Process Status</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-memory">23.3.5. Displaying Virtual Memory Information</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-files">23.3.6. Displaying Open Files</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-exit">23.3.7. Exiting the Utility</a></
span></dt></dl></dd><dt><span class="section"><a href="#s1-kdump-resources">23.4. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kdump-resources-installed">23.4.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-kdump-resources-online">23.4.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Consistent_Network_Device_Naming">A. Consistent Network Device Naming</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Consistent_Network_Device_Naming-Affected_Systems">A.1. Affected Systems</a></span></dt><dt><span class="section"><a href="#sect-Consistent_Network_Device_Naming-System_Requirements">A.2. システム要求</a></span></dt><dt><span class="section"><a href="#sect-Consistent_Network_Device_Naming-Enabling_and_Disabling">A.3. Enabling and Disabling the Feature</a></span></dt><dt><span class="section
"><a href="#sect-Consistent_Network_Device_Naming-Notes">A.4. Notes for Administrators</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-RPM">B. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rpm-design">B.1. RPM の設計目標</a></span></dt><dt><span class="section"><a href="#s1-rpm-using">B.2. RPMの使用法</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-rpm-finding">B.2.1. RPM パッケージの検索</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Upgrading">B.2.2. インストールとアップグレード</a></span></dt><dt><span class="section"><a href="#sec-Configuration_File_Changes">B.2.3. 設定ファイルの変更</a></span></dt><dt><span class="section"><a href="#s2-rpm-uninstalling">B.2.4. アンインストール</a></span></dt><dt><span class="section"><a href="#s2-rpm-freshening">B.2.5. インストール済みのアップグレードの実行</a></span></dt><dt><span class="section">
<a href="#s2-rpm-querying">B.2.6. 問い合わせ</a></span></dt><dt><span class="section"><a href="#s2-rpm-verifying">B.2.7. 検証</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-check-rpm-sig">B.3. パッケージの署名を確認する</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-keys-importing">B.3.1. Importing Keys</a></span></dt><dt><span class="section"><a href="#s2-keys-checking">B.3.2. Verifying Signature of Packages</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-rpm-impressing">B.4. Practical and Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="#s1-rpm-additional-resources">B.5. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-rpm-installed-docs">B.5.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-rpm-useful-websites">B.5.2. 役に立つ Web サイト</a></span></dt><dt><span class="sect
ion"><a href="#s2-rpm-related-books">B.5.3. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ch-The_X_Window_System">C. X Window System</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-x-server">C.1. The X Server</a></span></dt><dt><span class="section"><a href="#s1-x-clients">C.2. デスクトップ環境とウィンドウマネージャ</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-clients-desktop">C.2.1. デスクトップ環境</a></span></dt><dt><span class="section"><a href="#s2-x-clients-winmanagers">C.2.2. ウィンドウマネージャ</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-server-configuration">C.3. X サーバー設定ファイル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-server-config-xorg.conf-struct">C.3.1. The Structure of the Configuration</a></span></dt><dt><span class="section"><a href="#s2-x-server-config-xorg.conf.d">C.3.2. The <code class="
filename">xorg.conf.d</code> Directory</a></span></dt><dt><span class="section"><a href="#s2-x-server-config-xorg.conf">C.3.3. The <code class="filename">xorg.conf</code> File</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-fonts">C.4. フォント</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-x-fonts-fontconfig-add">C.4.1. Fontconfig へのフォントの追加</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-additional-resources">C.5. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-installed-documentation">C.5.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-x-useful-websites">C.5.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ch-The_sysconfig_Directory">D. sysconfig ディレクトリー</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-sysconfig-files">D.1
. Files in the /etc/sysconfig/ Directory</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysconfig-arpwatch">D.1.1. /etc/sysconfig/arpwatch </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-authconfig">D.1.2. /etc/sysconfig/authconfig </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-autofs">D.1.3. /etc/sysconfig/autofs </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-clock">D.1.4. /etc/sysconfig/clock </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-dhcpd">D.1.5. /etc/sysconfig/dhcpd </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-firewall">D.1.6. /etc/sysconfig/firstboot </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-i18n">D.1.7. /etc/sysconfig/i18n </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-init">D.1.8. /etc/sysconfig/init </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ip6tables">D.1.9. /etc/sysconfig/ip6tables-con
fig </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-kybd">D.1.10. /etc/sysconfig/keyboard </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ldap">D.1.11. /etc/sysconfig/ldap </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-named">D.1.12. /etc/sysconfig/named </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-network">D.1.13. /etc/sysconfig/network</a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ntpd">D.1.14. /etc/sysconfig/ntpd </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-quagga">D.1.15. /etc/sysconfig/quagga </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-radvd">D.1.16. /etc/sysconfig/radvd </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-samba">D.1.17. /etc/sysconfig/samba </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-selinux">D.1.18. /etc/sysconfig/selinux </a></span></dt><dt><span class="section"><a href="#s2-syscon
fig-sendmail">D.1.19. /etc/sysconfig/sendmail </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-spamd">D.1.20. /etc/sysconfig/spamassassin </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-squid">D.1.21. /etc/sysconfig/squid </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-rcu">D.1.22. /etc/sysconfig/system-config-users </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-vncservers">D.1.23. /etc/sysconfig/vncservers </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-xinetd">D.1.24. /etc/sysconfig/xinetd </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysconfig-etcsysconf-dir">D.2. Directories in the /etc/sysconfig/ Directory</a></span></dt><dt><span class="section"><a href="#s1-sysconfig-additional-resources">D.3. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysconfig-installed-documentation">D.3.1. インストールã•ã‚Œã¦ã„るドã‚ã
ƒ¥ãƒ¡ãƒ³ãƒˆ</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ch-proc">E. The proc File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-proc-virtual">E.1. A Virtual File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-viewing">E.1.1. Viewing Virtual Files</a></span></dt><dt><span class="section"><a href="#s2-proc-change">E.1.2. Changing Virtual Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-topfiles">E.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-buddyinfo">E.2.1. /proc/buddyinfo </a></span></dt><dt><span class="section"><a href="#s2-proc-cmdline">E.2.2. /proc/cmdline </a></span></dt><dt><span class="section"><a href="#s2-proc-cpuinfo">E.2.3. /proc/cpuinfo </a></span></dt><dt><span class="section"><a href="#s2-proc-crypto">E.2.4. /proc/crypto </a></span></dt><dt><span class="sec
tion"><a href="#s2-proc-devices">E.2.5. /proc/devices </a></span></dt><dt><span class="section"><a href="#s2-proc-dma">E.2.6. /proc/dma </a></span></dt><dt><span class="section"><a href="#s2-proc-execdomains">E.2.7. /proc/execdomains </a></span></dt><dt><span class="section"><a href="#s2-proc-fb">E.2.8. /proc/fb </a></span></dt><dt><span class="section"><a href="#s2-proc-filesystems">E.2.9. /proc/filesystems </a></span></dt><dt><span class="section"><a href="#s2-proc-interrupts">E.2.10. /proc/interrupts </a></span></dt><dt><span class="section"><a href="#s2-proc-iomem">E.2.11. /proc/iomem </a></span></dt><dt><span class="section"><a href="#s2-proc-ioports">E.2.12. /proc/ioports </a></span></dt><dt><span class="section"><a href="#s2-proc-kcore">E.2.13. /proc/kcore </a></span></dt><dt><span class="section"><a href="#s2-proc-kmsg">E.2.14. /proc/kmsg </a></span></dt><dt><span class="section"><a href="#s2-proc-loadavg">E.2.15. /proc/loadavg </a></span></dt><dt><span cl
ass="section"><a href="#s2-proc-locks">E.2.16. /proc/locks </a></span></dt><dt><span class="section"><a href="#s2-proc-mdstat">E.2.17. /proc/mdstat </a></span></dt><dt><span class="section"><a href="#s2-proc-meminfo">E.2.18. /proc/meminfo </a></span></dt><dt><span class="section"><a href="#s2-proc-misc">E.2.19. /proc/misc </a></span></dt><dt><span class="section"><a href="#s2-proc-modules">E.2.20. /proc/modules </a></span></dt><dt><span class="section"><a href="#s2-proc-mounts">E.2.21. /proc/mounts </a></span></dt><dt><span class="section"><a href="#s2-proc-mtrr">E.2.22. /proc/mtrr </a></span></dt><dt><span class="section"><a href="#s2-proc-partitions">E.2.23. /proc/partitions </a></span></dt><dt><span class="section"><a href="#s2-proc-slabinfo">E.2.24. /proc/slabinfo </a></span></dt><dt><span class="section"><a href="#s2-proc-stat">E.2.25. /proc/stat </a></span></dt><dt><span class="section"><a href="#s2-proc-swaps">E.2.26. /proc/swaps </a></span></dt><dt><span c
lass="section"><a href="#s2-proc-sysrq-trigger">E.2.27. /proc/sysrq-trigger </a></span></dt><dt><span class="section"><a href="#s2-proc-uptime">E.2.28. /proc/uptime </a></span></dt><dt><span class="section"><a href="#s2-proc-version">E.2.29. /proc/version </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-directories">E.3. Directories within /proc/</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-processdirs">E.3.1. Process Directories</a></span></dt><dt><span class="section"><a href="#s2-proc-dir-bus">E.3.2. /proc/bus/ </a></span></dt><dt><span class="section"><a href="#s2-proc-pci">E.3.3. /proc/bus/pci </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-driver">E.3.4. /proc/driver/ </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-fs">E.3.5. /proc/fs </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-irq">E.3.6. /proc/irq/ </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-net"
>E.3.7. /proc/net/ </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-scsi">E.3.8. /proc/scsi/ </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-sys">E.3.9. /proc/sys/ </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-sysvipc">E.3.10. /proc/sysvipc/ </a></span></dt><dt><span class="section"><a href="#s2-proc-tty">E.3.11. /proc/tty/ </a></span></dt><dt><span class="section"><a href="#s2-proc-pid">E.3.12. /proc/<em class="replaceable"><code>PID</code></em>/ </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-sysctl">E.4. Using the sysctl Command</a></span></dt><dt><span class="section"><a href="#s1-proc-additional-resources">E.5. 参考文献</a></span></dt></dl></dd><dt><span class="appendix"><a href="#app-Revision_History">F. 改訂履歴</a></span></dt><dt><span class="index"><a href="#idm107444896">索引</a></span></dt></dl></div><div xml:lang="ja-JP" class="preface" id="idm81962928" lang="ja-JP"><div class=
"titlepage"><div><div><h1 id="idm81962928" 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 17 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">
+ パッケージのインストールや管理に使用する <span class="application"><strong>PackageKit</strong></span> やコマンドライン <span class="application"><strong>Yum</strong></span> パッケージ マネージャー
+ </div></li><li class="listitem"><div class="para">
+ Setting up a network—from establishing an Ethernet connection using <span class="application"><strong>NetworkManager</strong></span> to configuring channel bonding interfaces to increase server bandwidth
+ </div></li><li class="listitem"><div class="para">
+ Configuring <code class="systemitem">DHCP</code>, <span class="application"><strong>BIND</strong></span>, <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">
+ Gathering information about your system, including obtaining kernel-space crash data with <code class="systemitem">kdump</code>
+ </div></li><li class="listitem"><div class="para">
+ Easily 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">Deployment 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/en-US/Fedora/16/html/Installation_Guide/index.html">Fedora 17 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-Configuring_the_Language_and_Keyboard">1章<em>言語とキーボードの設定</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">2章<em>日付と時刻の設定</em></a> covers the configuration of the system date and time. Read this chapter if you need to change the date and time setup, or configure the system to synchronize the clock with a remote Network Time Protocol (NTP) server.
+ </div><div class="para">
+ <a class="xref" href="#ch-Managing_Users_and_Groups">3章<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 both <span class="application"><strong>Yum</strong></span> and the <span class="application"><strong>PackageKit</strong></span> suite of graphical package management tools.
+ </div><div class="para">
+ <a class="xref" href="#ch-yum">4章<em>Yum</em></a> describes the <span class="application"><strong>Yum</strong></span> package manager. Read this chapter for information how to search, install, update, and uninstall packages on the command line.
+ </div><div class="para">
+ <a class="xref" href="#ch-PackageKit">5章<em>PackageKit</em></a> describes the <span class="application"><strong>PackageKit</strong></span> suite of graphical package management tools. Read this chapter for information how to search, install, update, and uninstall packages using a graphical user interface.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#part-Networking">パートIII「ネットワーク」</a></span></dt><dd><div class="para">
+ このパートは Fedora のネットワーク設定の仕方について記述しています。
+ </div><div class="para">
+ <a class="xref" href="#ch-Network_Interfaces">7章<em>ネットワーク・インターフェース</em></a> explores various interface configuration files, interface control scripts, and network function files located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. Read this chapter for information how to use these files to configure network interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#part-Infrastructure_Services">パートIV「インフラストラクチャーサービス」</a></span></dt><dd><div class="para">
+ このパートはリモート ログインの有効化、認証の設定、daemon やサービスの設定方法についての情報を提供します。
+ </div><div class="para">
+ <a class="xref" href="#ch-Services_and_Daemons">8章<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-Configuring_Authentication">9章<em>認証の設定</em></a> describes how to configure user information retrieval from Lightweight Directory Access Protocol (LDAP), Network Information Service (NIS), and Winbind user account databases, and provides an introduction to the System Security Services Daemon (SSSD). Read this chapter if you need to configure authentication on your system.
+ </div><div class="para">
+ <a class="xref" href="#ch-OpenSSH">10章<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">パートV「サーバー」</a></span></dt><dd><div class="para">
+ このパートは、ウェブサーバーを導入する、またはネットワーク上にファイルとディレクトリを共有する方法のようなサーバーに関連したさまざまな話題を説明しています。
+ </div><div class="para">
+ <a class="xref" href="#ch-DHCP_Servers">11章<em>DHCP サーバー</em></a> guides you through the installation of a Dynamic Host Configuration Protocol (DHCP) server and client. Read this chapter if you need to configure DHCP on your system.
+ </div><div class="para">
+ <a class="xref" href="#ch-DNS_Servers">12章<em>DNS サーバー</em></a> introduces you to Domain Name System (DNS), explains how to install, configure, run, and administer the <span class="application"><strong>BIND</strong></span> DNS server. Read this chapter if you need to configure a DNS server on your system.
+ </div><div class="para">
+ <a class="xref" href="#ch-Web_Servers">13章<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">14章<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">15章<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">16章<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></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#part-Monitoring_and_Automation">パートVI「監視および自動化」</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 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">パートVII「カーネル、モジュールおよびドライバーの設定」</a></span></dt><dd><div class="para">
+ このパートはカーネルのカスタマイズと管理を支援するさまざまなツールをカバーします。
+ </div><div class="para">
+ <a class="xref" href="#ch-Manually_Upgrading_the_Kernel">21章<em>カーネルをアップグレードする</em></a> provides important information how to manually update a kernel package using the <code class="command">rpm</code> command instead of <code class="command">yum</code>. Read this chapter if you cannot update a kernel package with the <span class="application"><strong>Yum</strong></span> package manager.
+ </div><div class="para">
+ <a class="xref" href="#ch-Working_with_Kernel_Modules">22章<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><div class="para">
+ <a class="xref" href="#ch-kdump">23章<em>The kdump Crash Recovery Service</em></a> explains how to configure, test, and use the <code class="systemitem">kdump</code> service in Fedora, and provides a brief overview of how to analyze the resulting core dump using the <span class="application"><strong>crash</strong></span> debugging utility. Read this chapter to learn how to enable <code class="systemitem">kdump</code> on your system.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#appe-Consistent_Network_Device_Naming">付録A <em>Consistent Network Device Naming</em></a></span></dt><dd><div class="para">
+ This appendix covers consistent network device naming for network interfaces, a feature that changes the name of network interfaces on a system in order to make locating and differentiating the interfaces easier. Read this appendix to learn more about this feature and how to enable or disable it.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#ch-RPM">付録B <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">yum</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#ch-The_X_Window_System">付録C <em>X Window System</em></a></span></dt><dd><div class="para">
+ This appendix covers the configuration of the X Window System, the graphical environment used by Fedora. Read this appendix if you need to adjust the configuration of your X Window System.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#ch-The_sysconfig_Directory">付録D <em>sysconfig ディレクトリー</em></a></span></dt><dd><div class="para">
+ This appendix outlines some of the files and directories located in the <code class="filename">/etc/sysconfig/</code> directory. Read this appendix if you want to learn more about these files and directories, their function, and their contents.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#ch-proc">付録E <em>The proc File System</em></a></span></dt><dd><div class="para">
+ This appendix explains the concept of a virtual file system, and describes some of the top-level files and directories within the <code class="systemitem">proc</code> file system (that is, the <code class="filename">/proc/</code> directory). Read this appendix if you want to learn more about this file system.
+ </div></dd></dl></div></div><div xml:lang="ja-JP" class="section" id="idm131549856" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm131549856">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="idm118497712"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm118497712">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 at 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="idm131547248"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm131547248">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="idm112170144"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm112170144">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="sect-Preface-Feedback" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4. フィードバック</h2></div></div></div><a id="idm119000000" 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 <a href="http://bugzilla.redhat.com/">Bugzilla</a> against the product <span class="application"><strong>Fedora Documentation</strong></span>.
+ </div><div class="para">
+ バグリポートの送信時は、必ず以下の情報を確認してください:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Manual's identifier: <code class="literal">system-administrator's-guide</code>
+ </div></li><li class="listitem"><div class="para">
+ バージョン番号: <code class="literal">17</code>
+ </div></li></ul></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">Deployment Guide</em>, copyright © 2007 Red Hat, Inc., available at <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/index.html">http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/index.html</a>.
+ </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="idm130822176"><div></div><div class="para">
+ このパートは、キーボードの設定、日付と時刻の設定、およびユーザーとグループの管理のような基本的なシステムの管理作業を取り扱います。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="#ch-Configuring_the_Language_and_Keyboard">1. 言語ã¨ã‚ーボードã®è¨å®š</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Language">1.1. 言語ã®å¤‰æ›´</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Formats">1.2. 日付ã€æ™‚刻ãŠã‚ˆã³æ•°å—ã®å½¢å¼ã®å¤‰æ›´</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Layouts">1.3. ã‚ーボードã®ãƒ¬ã‚¤ã‚¢ã‚¦ãƒˆå¤‰æ›´</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-System">1.4. ç¾åœ¨ã®è¨å®šã®è¡¨ç¤º</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_the_Date_and_Time">2. 日付ã¨æ™‚刻ã®è¨å®š</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Date_and_Time">2.1. 日付ã
¨æ™‚刻ã®è¨å®šãƒ„ールã®ä½¿ã„æ–¹</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration">2.2. コマンドラインツールã®ä½¿ç”¨</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">2.2.1. 日付ã®å¤‰æ›´æ–¹æ³•</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time">2.2.2. 時刻ã®å¤‰æ›´æ–¹æ³•</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">2.2.3. Network Time Protocol ã®è¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Additional_Resources">2.3. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Additional_Resources-Installed_Documentation">2.3.1. インストーãƒ
«ã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Managing_Users_and_Groups">3. ユーザーã¨ã‚°ãƒ«ãƒ¼ãƒ—ã®ç®¡ç†</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-groups-introduction">3.1. ユーザーã¨ã‚°ãƒ«ãƒ¼ãƒ—ã®ã‚¤ãƒ³ãƒˆãƒãƒ€ã‚¯ã‚·ãƒ§ãƒ³</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">3.1.1. ユーザープライベートグループ</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">3.1.2. シャドウパスワード</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts">3.2. ユーザー アカウントã®ãƒ„ールを使ã†</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.2.1. アカウントã®è¨å®š</a></span></dt><dt><span class="section"><a href="#sect-Managing_Users_and_Gro
ups-User_Accounts-Adding_a_New_User">3.2.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.2.3. ユーザーの削除</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">3.3. ユーザー管理のツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-list">3.3.1. ユーザーとグループを閲覧する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-user-new">3.3.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-new">3.3.3. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-user-properties">3.3.4. ユーザーのプロパティを変更する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-properties">3.3.5. グループ
のプロパティを変更する</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">3.4. コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-tools-users-add">3.4.1. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">3.4.2. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">3.4.3. パスワードエージングの有効化</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">3.4.4. 自動ログアウトの有効化</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">3.4.5. グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-additional-resources">3.5. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-us
ers-groups-documentation">3.5.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></dd></dl></div></div><div xml:lang="ja-JP" class="chapter" id="ch-Configuring_the_Language_and_Keyboard" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第1章 言語とキーボードの設定</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Language">1.1. 言語の変更</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Formats">1.2. 日付、時刻および数字の形式の変更</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-Layouts">1.3. キーボードのレイアウト変更</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Language_and_Keyboard-System">1.4. 現在の設定の表示</a></span></dt></dl></div><div class="para">
+ Fedora 17 は<span class="application"><strong>地域と言語</strong></span>設定ツールを同梱しています。これは、キーボード配置、デスクトップ環境の言語、および他の地域の設定をできます。ツールを開始するには、<span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>システム設定</strong></span>を選択することにより<span class="application"><strong>システム設定</strong></span>ウィンドウを開き、<span class="guimenuitem"><strong>地域と言語</strong></span>をクリックします。
+ </div><div class="section" id="sect-Configuring_the_Language_and_Keyboard-Language"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. 言語の変更</h2></div></div></div><a id="idm94854304" class="indexterm"></a><a id="idm120364688" class="indexterm"></a><div class="para">
+ デスクトップの言語を設定するには、<span class="application"><strong>地域と言語</strong></span>アプリケーションの<span class="guilabel"><strong>言語</strong></span>タブを選択します。一般的な言語の簡単な一覧が表示されます。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Language"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-language.png" alt="言語の変更" /><div class="longdesc"><div class="para">
+ 言語の変更
+ </div></div></div></div><h6>図1.1 言語の変更</h6></div><br class="figure-break" /><div class="para">
+ デフォルトで、このリストはいくつかの利用可能な言語のみを含みます。他の言語を追加するには、リストの下にある <span class="guibutton"><strong>+</strong></span> (プラス記号) ボタンをクリックします。ダイアログウィンドウが表示され、希望する言語を選択できます。ダイアログウィンドウの下部にある入力フィールドを使用して、そこに言語名の最初の数文字を入力すると表示される言語を減らすことができるようになります（たとえば、スロバキア語には <span class="quote">「<span class="quote">slov</span>」</span> です）。言語を選択すると、選んだものを確認するために<span class="guibutton"><strong>選択</strong></span>ボタンをクリックします。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Language-Add"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-language-add.png" alt="他の言語の追加" /><div class="longdesc"><div class="para">
+ Adding a language
+ </div></div></div></div><h6>図1.2 他の言語の追加</h6></div><br class="figure-break" /><div class="para">
+ 一覧の中から特定の言語を選択するには、その名前をクリックします。変更は次回ログイン時に有効になります。
+ </div></div><div class="section" id="sect-Configuring_the_Language_and_Keyboard-Formats"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.2. 日付、時刻および数字の形式の変更</h2></div></div></div><a id="idm124975952" class="indexterm"></a><div class="para">
+ デフォルトの日付、時刻、および通貨のフォーマットを変更するには、<span class="application"><strong>地域と言語</strong></span>アプリケーションの<span class="guilabel"><strong>フォーマット</strong></span>タブを選択します。利用可能なフォーマットの簡単な一覧が表示されます。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Formats"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-formats.png" alt="日付、時刻および数字の形式の変更" /><div class="longdesc"><div class="para">
+ 日付、時刻および数字の形式の変更
+ </div></div></div></div><h6>図1.3 日付、時刻および数字の形式の変更</h6></div><br class="figure-break" /><div class="para">
+ デフォルトで、このリストはいくつかの利用可能なフォーマットのみを含みます。他のフォーマットを追加するには、リストの下にある <span class="guibutton"><strong>+</strong></span> (プラス記号) ボタンをクリックします。ダイアログウィンドウが表示され、地域により希望するフォーマットを選択できます。ダイアログウィンドウの下部にある入力フィールドを使用して、そこに地域名の最初の数文字を入力すると表示される言語を減らすことができるようになります（たとえば、スロバキアには <span class="quote">「<span class="quote">slov</span>」</span> です）。言語を選択すると、選んだものを確認するために<span class="guibutton"><strong>選択</strong></span>ボタンをクリックします。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Formats-Add"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-formats-add.png" alt="フォーマットの追加" /><div class="longdesc"><div class="para">
+ フォーマットの追加
+ </div></div></div></div><h6>図1.4 フォーマットの追加</h6></div><br class="figure-break" /><div class="para">
+ 一覧の中から特定のフォーマットを選択するには、その名前をクリックします。変更は次回ログイン時に有効になります。
+ </div></div><div class="section" id="sect-Configuring_the_Language_and_Keyboard-Layouts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.3. キーボードのレイアウト変更</h2></div></div></div><a id="idm128031440" class="indexterm"></a><a id="idm128029872" class="indexterm"></a><div class="para">
+ システム管理者がインストール中にインストールプログラムによりキーボード配置を設定できるにも関わらず、デフォルトの設定は現在の要望に対して常に適切ではないかもしれません。デフォルトのキーボードレイアウトを変更するには、<span class="application"><strong>地域と言語</strong></span>アプリケーションの<span class="application"><strong>レイアウト</strong></span>タブを選択します。現在有効なレイアウトの一覧が表示されます。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Layouts"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-layouts.png" alt="キーボードのレイアウトの変更" /><div class="longdesc"><div class="para">
+ キーボードのレイアウトの変更
+ </div></div></div></div><h6>図1.5 キーボードのレイアウトの変更</h6></div><br class="figure-break" /><div class="para">
+ 他のレイアウトを一覧に追加するには、リストの下にある <span class="guibutton"><strong>+</strong></span> (プラス記号) ボタンをクリックします。ダイアログウィンドウが表示され、希望するレイアウトを選択できます。ダイアログウィンドウの下部にある入力フィールドを使用して、そこにレイアウト名の最初の数文字を入力すると表示される言語を減らすことができるようになります（たとえば、スロバキアのレイアウトには <span class="quote">「<span class="quote">slov</span>」</span> です）。言語を選択すると、選んだものを確認するために<span class="guibutton"><strong>追加</strong></span>ボタンをクリックします。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Layouts-Add"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-layouts-add.png" alt="キーボードのレイアウトの追加" /><div class="longdesc"><div class="para">
+ キーボードのレイアウトの追加
+ </div></div></div></div><h6>図1.6 キーボードのレイアウトの追加</h6></div><br class="figure-break" /><div class="para">
+ 一覧の最初にあるレイアウトが常にデフォルトと考えられます。特定のレイアウトを一覧において上下させるには、それを選択して、それぞれ <span class="guibutton"><strong>∧</strong></span> (上矢印) または <span class="guibutton"><strong>∨</strong></span> (下矢印) ボタンをクリックします。レイアウトを削除するには、 <span class="guibutton"><strong>−</strong></span> (マイナス記号) ボタンをクリックします。さらに、ウィンドウの右側にあるオプションボタンを選択することにより、個々のウィンドウに対して異なるキーボード配置を使用するか、すべてのウィンドウに対して一つのレイアウトを使用するかを選択できます。
+ </div><div class="para">
+ 複数のレイアウトを有効にしているとき、レイアウトを切り替えられるよう、パネルにキーボードインジケーターが表示されます。
+ </div><div class="figure" id="fig-keyboard-layouts-indicator"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-layouts-indicator.png" alt="キーボードのレイアウトのインジケーター" /><div class="longdesc"><div class="para">
+ キーボードのレイアウトのインジケーター
+ </div></div></div></div><h6>図1.7 キーボードのレイアウトのインジケーター</h6></div><br class="figure-break" /></div><div class="section" id="sect-Configuring_the_Language_and_Keyboard-System"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.4. 現在の設定の表示</h2></div></div></div><a id="idm131381280" class="indexterm"></a><div class="para">
+ 現在の設定を表示するには、<span class="application"><strong>地域と言語</strong></span>アプリケーションの<span class="guilabel"><strong>システム</strong></span>タブを選択します。あなた自身の設定とシステム全体の設定の比較が表示されます。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-System"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-system.png" alt="現在の設定の表示" /><div class="longdesc"><div class="para">
+ 現在の設定の表示
+ </div></div></div></div><h6>図1.8 現在の設定の表示</h6></div><br class="figure-break" /></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">第2章 日付と時刻の設定</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Date_and_Time">2.1. 日付と時刻の設定ツールの使い方</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration">2.2. コマンドラインツールの使用</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">2.2.1. 日付の変更方法</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time">2.2.2. 時刻の変更方法</a></span></dt><dt><span class="section"><a href="#sect-Con
figuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">2.2.3. Network Time Protocol の設定</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Additional_Resources">2.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-Additional_Resources-Installed_Documentation">2.3.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><div class="para">
+ 本章は Fedora においてシステムの日付と時刻を設定することについて取り扱いします。手動による方法と Network Time Protocol (<abbr class="abbrev">NTP</abbr>) を用いる方法どちらもです。また、適切なタイムゾーンを設定することも取り扱います。どちらの方法も、<span class="application"><strong>日付と時刻</strong></span>の設定ツールを用いて日付と時刻を設定する方法と同じことをコマンドラインにおいて実行する方法を取り扱います。
+ </div><div class="section" id="sect-Configuring_the_Date_and_Time-Date_and_Time"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. 日付と時刻の設定ツールの使い方</h2></div></div></div><div class="para">
+ Fedora 17 ã¯<span class="application"><strong>日付ã¨æ™‚刻</strong></span>è¨å®šãƒ„ールをåŒæ¢±ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ã‚·ã‚¹ãƒ†ãƒ ã®æ—¥ä»˜ã¨æ™‚刻を変更ã™ã‚‹ã€ã‚·ã‚¹ãƒ†ãƒ ã«ã‚ˆã‚Šä½¿ç”¨ã•ã‚Œã‚‹ã‚¿ã‚¤ãƒ ゾーンをè¨å®šã™ã‚‹ã€ãŠã‚ˆã³æ™‚刻サーãƒãƒ¼ã¨ã‚·ã‚¹ãƒ†ãƒ クãƒãƒƒã‚¯ã‚’åŒæœŸã™ã‚‹ãŸã‚ã« NTP (Network Time Protocol) デーモンをセットアップã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ツールを起動ã™ã‚‹ã«ã¯ã€<span class="guimenu"><strong>アクティビティ</strong></span>メニューã‹ã‚‰<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>システムè¨å®š</strong></span>ã‚’é¸æŠžã—ã¦<span class="guimenuitem"><strong>日付ã¨æ™‚刻</strong></span>アイコンをé¸æŠžã™ã‚‹ã‹ã€ãƒ‰ãƒãƒƒãƒ—ダウンメニューã‹ã‚‰<span class="guibutton"><strong>日付ã¨æ™‚刻ã®è¨å®š</strong></span>ã‚’é
¸æŠžã—ã¾ã™ã€‚
+ </div><div class="figure" id="fig-Configuring_the_Date_and_Time-Date_and_Time"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-settings.png" alt="日付と時刻の設定ツール" /><div class="longdesc"><div class="para">
+ 日付と時刻の設定ツール
+ </div></div></div></div><h6>図2.1 日付と時刻の設定ツール</h6></div><br class="figure-break" /><div class="para">
+ デフォルトで、ツールは現在の設定を表示することのみできます。<code class="systemitem">root</code> のみがシステムの日付と時刻を設定できるからです。変更するために設定ツールをロック解除するには、ウィンドウの右上角にある<span class="guibutton"><strong>解除</strong></span>ボタンをクリックして、プロンプトが出たときに正しいパスワードを入力します。
+ </div><a id="idm120823136" class="indexterm"></a><a id="idm122173072" class="indexterm"></a><div class="para">
+ システムの現在の時刻を変更するには、<span class="guilabel"><strong>ネットワーク時刻</strong></span>スイッチをクリックすることによりネットワーク上で同期するようシステムを設定するか、または数字の上と下にある上下の矢印をクリックすることにより手動で設定します。24時間形式を有効または無効にするために、<span class="guilabel"><strong>24時間</strong></span>または <span class="guilabel"><strong>AM/PM</strong></span> を選択できます。
+ </div><a id="idm124070288" class="indexterm"></a><a id="idm124068720" class="indexterm"></a><div class="para">
+ タイムゾーンを変更するには、地図をクリックするか、<span class="guilabel"><strong>地域</strong></span>および<span class="guilabel"><strong>都市</strong></span>のドロップダウンリストから地域と都市を選択してください。
+ </div><a id="idm86704448" class="indexterm"></a><a id="idm86702848" class="indexterm"></a><div class="para">
+ システムの現在の日付を変更するには、時刻の下にあるドロップダウンリストから月を選択して、日と年を選択するために上下の矢印を使用します。
+ </div><div class="para">
+ この変更は直ちに反映されます。
+ </div></div><div class="section" id="sect-Configuring_the_Date_and_Time-Command_Line_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. コマンドラインツールの使用</h2></div></div></div><div class="para">
+ Fedora 17 は、手動または NTP プロトコルを用いて日付と時刻を設定できるコマンドラインツールを提供しています。
+ </div><div class="section" id="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.1. 日付の変更方法</h3></div></div></div><a id="idm94635552" class="indexterm"></a><a id="idm90178176" class="indexterm"></a><div class="para">
+ システムの日付を変更するには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のとおり入力します:
+ </div><pre class="screen"><code class="command">date +%D -s <em class="replaceable"><code>YYYY-MM-DD</code></em></code></pre><div class="para">
+ …ここで <em class="replaceable"><code>YYYY</code></em> は4桁の年、<em class="replaceable"><code>MM</code></em> は2桁の月、<em class="replaceable"><code>DD</code></em> は2桁の日です。たとえば、日付を2010年6月2日に変更するには、次のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">date +%D -s 2010-06-02</code></pre><div class="para">
+ 何も引数をつけずに <code class="command">date</code> を実行することにより現在の設定を確認できます。
+ </div></div><div class="section" id="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.2. 時刻の変更方法</h3></div></div></div><div class="para">
+ 現在の時刻を変更するには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="screen"><code class="command">date +%T -s <em class="replaceable"><code>HH:MM:SS</code></em></code></pre><div class="para">
+ …ここで <em class="replaceable"><code>HH</code></em> は時間を意味して、<em class="replaceable"><code>MM</code></em> は時間、<em class="replaceable"><code>SS</code></em> は秒です。システムクロックが <acronym class="acronym">UTC</acronym> (Coordinated Universal Time) を使用するよう設定されているならば、以下のオプションも追加してください:
+ </div><pre class="screen"><code class="command">date +%T -s <em class="replaceable"><code>HH:MM:SS</code></em> -u</code></pre><div class="para">
+ たとえば、システムクロックを <acronym class="acronym">UTC</acronym> を使用して 11:26 PM に設定するには、次のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">date +%T -s 23:26:00 -u</code></pre><div class="para">
+ 何も引数をつけずに <code class="command">date</code> を実行することにより現在の設定を確認できます。
+ </div></div><div class="section" id="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.3. Network Time Protocol の設定</h3></div></div></div><a id="idm101383104" class="indexterm"></a><a id="idm113416912" class="indexterm"></a><a id="idm113415952" class="indexterm"></a><a id="idm110423744" class="indexterm"></a><div class="para">
+ 上述の手動セットアップと対照的に、Network Time Protocol (<acronym class="acronym">NTP</acronym>) を通してリモートサーバーとシステムクロックを同期することもできます。一度だけの同期には、<span class="application"><strong>ntpdate</strong></span> コマンドを使用します:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ 以下の形式で <code class="command">ntpdate</code> を使用することにより、選択した NTP サーバーがアクセス可能であるかを確認します:
+ </div><pre class="screen"><code class="command">ntpdate -q <em class="replaceable"><code>server_address</code></em></code></pre><div class="para">
+ たとえば、<code class="systemitem">0.fedora.pool.ntp.org</code> に接続するには、次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">ntpdate -q 0.fedora.pool.ntp.org</code>
+server 204.15.208.61, stratum 2, offset -39.275438, delay 0.16083
+server 69.65.40.29, stratum 2, offset -39.269122, delay 0.17191
+server 148.167.132.201, stratum 2, offset -39.270239, delay 0.20482
+17 Oct 17:41:09 ntpdate[10619]: step time server 204.15.208.61 offset -39.275438 sec</pre></li><li class="step"><div class="para">
+ 良好なサーバーを検索するとき、<code class="systemitem">root</code> として、1つ以上のサーバーアドレスを引数として <span class="application"><strong>ntpdate</strong></span> コマンドを実行してください:
+ </div><pre class="screen"><code class="command">ntpdate <em class="replaceable"><code>server_address…</code></em></code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]# <code class="command">ntpdate 0.fedora.pool.ntp.org 1.fedora.pool.ntp.org</code>
+17 Oct 17:42:13 ntpdate[10669]: step time server 204.15.208.61 offset -39.275436 sec</pre><div class="para">
+ エラーメッセージが何も表示されなければ、システム時刻が設定されます。<code class="command">date</code> コマンドを引数なしで実行することにより現在の時刻を確認できます。
+ </div></li><li class="step"><div class="para">
+ 大抵の場合、これらの手順で十分です。1つ以上のサービスが常に現在の時刻を使用する必要が本当にあるならば、<code class="systemitem">root</code> として以下のコマンドを実行することにより、起動時に <span class="application"><strong>ntpdate</strong></span> を実行するようにします:
+ </div><pre class="screen"><code class="command">systemctl enable ntpdate.service</code></pre><div class="para">
+ システムサービスとそのセットアップに関する詳細は、<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ 起動時に時刻サーバーと同期を続けることに失敗するならば、関連するエラーメッセージを <code class="filename">/var/log/boot.log</code> において確認できます。以下の行を <code class="filename">/etc/sysconfig/network</code> に追加してみてください:
+ </div><pre class="screen">NETWORKWAIT=1</pre></div></div></li></ol></div><a id="idm126027200" class="indexterm"></a><a id="idm139995488" class="indexterm"></a><a id="idm139994528" class="indexterm"></a><a id="idm147931440" class="indexterm"></a><div class="para">
+ しかしながら、起動時に時刻を自動的に同期されるためのより便利な方法は <code class="systemitem">ntpd</code> デーモンを設定することです:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ <code class="systemitem">root</code> として、NTP 設定ファイル <code class="filename">/etc/ntp.conf</code> をテキストエディターで開きます。もしまだ存在しなければ、新しいものを作成します。
+ </div></li><li class="step"><div class="para">
+ 公開されている NTP サーバーの一覧を追加または編集します。Fedora 17 を使用しているならば、すでに以下の行が含まれているファイルが存在しますが、必要に応じてこれらを気軽に変更や拡張してください:
+ </div><pre class="screen">server 0.fedora.pool.ntp.org iburst
+server 1.fedora.pool.ntp.org iburst
+server 2.fedora.pool.ntp.org iburst</pre><div class="note"><div class="admonition_header"><h2>初期同期の高速化</h2></div><div class="admonition"><div class="para">
+ 初期同期を高速化するには、<code class="command">iburst</code> ディレクティブを各サーバー設定行の最後に加えることが推奨されます。
+ </div></div></div></li><li class="step"><div class="para">
+ 同じファイルにおいて、適切なパーミッションを設定して、localhost のみにアクセスを制限します:
+ </div><pre class="screen">restrict default kod nomodify notrap nopeer noquery
+restrict -6 default kod nomodify notrap nopeer noquery
+restrict 127.0.0.1
+restrict -6 ::1</pre></li><li class="step"><div class="para">
+ 変更を保存して、エディタを終了して、NTP デーモンを再起動します:
+ </div><pre class="screen"><code class="command">systemctl restart ntpd.service</code></pre></li><li class="step"><div class="para">
+ 加えて、<code class="command">ntpd</code> デーモンがブート時に起動することを確実にします:
+ </div><pre class="screen"><code class="command">systemctl enable ntpd.service</code></pre></li></ol></div></div></div><div class="section" id="sect-Configuring_the_Date_and_Time-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. その他のリソース</h2></div></div></div><div class="para">
+ 日付と時刻の設定に関する詳細は、以下のリソースを参照してください。
+ </div><div class="section" id="sect-Configuring_the_Date_and_Time-Additional_Resources-Installed_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.1. インストールされているドキュメント</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">date</code>(1) — <span class="application"><strong>date</strong></span> ユーティリティのマニュアルページです。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">ntpdate</code>(8) — <span class="application"><strong>ntpdate</strong></span> ユーティリティのマニュアルページです。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">ntpd</code>(8) — <code class="systemitem">ntpd</code> サービスのマニュアルページです。
+ </div></li></ul></div></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">第3章 ユーザーとグループの管理</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-users-groups-introduction">3.1. ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">3.1.1. ユーザープライベートグループ</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">3.1.2. シャドウパスワード</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts">3.2. ユーザー アカウントのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.2.1. アカウントの設定</a></spa
n></dt><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">3.2.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.2.3. ユーザーの削除</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">3.3. ユーザー管理のツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-list">3.3.1. ユーザーとグループを閲覧する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-user-new">3.3.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-new">3.3.3. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-user-properties">3.3.4. ユーザーのプロパティを変更する</a></span></dt><dt><span class="section">
<a href="#s2-redhat-config-users-group-properties">3.3.5. グループã®ãƒ—ãƒãƒ‘ティを変更ã™ã‚‹</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">3.4. コマンドラインã®ãƒ„ールを使ã†</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-tools-users-add">3.4.1. æ–°è¦ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’è¿½åŠ ã™ã‚‹</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">3.4.2. æ–°è¦ã‚°ãƒ«ãƒ¼ãƒ—ã‚’è¿½åŠ ã™ã‚‹</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">3.4.3. パスワードエージングã®æœ‰åŠ¹åŒ–</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">3.4.4. 自動ãƒã‚°ã‚¢ã‚¦ãƒˆã®æœ‰åŠ¹åŒ–</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">3.4.5. グループ用ディレクトリーã®ä½œæˆ</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-additional-resources">3.5. ãã®ä»–ã®ãƒªã‚½ã
ƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-documentation">3.5.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt></dl></dd></dl></div><a id="idm88225408" class="indexterm"></a><a id="idm108724576" class="indexterm"></a><a id="idm115163344" class="indexterm"></a><a id="idm96621968" class="indexterm"></a><div class="para">
+ ユーザーとグループの管理は Fedora のシステム管理の中心的な要素です。本章は、グラフィカルユーザーインターフェースとコマンドラインにおいてユーザーとグループを追加、管理および削除する方法について説明しています。また、パスワードエージングやグループディレクトリの作成などの高度な話題を取り扱います。
+ </div><div class="section" id="s1-users-groups-introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. ユーザーとグループのイントロダクション</h2></div></div></div><div class="para">
+ ユーザーが人（アカウントが物理的なユーザーにひもづいていることを意味します）または特定のアプリケーションが使用するために存在するアカウントである一方、グループは共通の目的のために一緒なユーザーとひもづく組織の論理的な表現です。
+ </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">
+ さらに Fedora は、所有者以外の特定のユーザーに対してパーミッションを設定できる<em class="firstterm">アクセス制御リスト</em> (<acronym class="acronym">ACLs</acronym>: access control lists) をファイルとディレクトリに対してサポートしています。この機能の詳細については、<a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/index.html"><em class="citetitle">Storage Administration Guide</em></a> の <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-acls.html"><em class="citetitle">Access Control Lists</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">3.1.1. ユーザープライベートグループ</h3></div></div></div><a id="idm64290464" class="indexterm"></a><a id="idm128014592" class="indexterm"></a><a id="idm128013184" class="indexterm"></a><a id="idm130657328" 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">
+ 新しく作成されたファイルやディレクトリに適用されるパーミッションを決める設定は、<em class="firstterm">umask</em> と呼ばれ、<code class="filename">/etc/bashrc</code> ファイルにおいて設定されます。UNIX システムにおいては伝統的に、ファイルやディレクトリを作成したユーザーのみが変更をできる、<code class="command">umask</code> が <code class="command">022</code> に設定されます。このスキーマの下では、 <span class="emphasis"><em>作成者のグループのメンバーを含めて</em></span>すべての他のユーザーはすべての変更が許可されません。しかしながら、UPG スキーマにおいては、すべてのユーザーが自分のプライベートグループを持つので、この<span class="quote">「<span class="quote">グループ保護</span>」</span>は必要ありません。
+ </div></div><div class="section" id="s2-users-groups-shadow-utilities"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.1.2. シャドウパスワード</h3></div></div></div><a id="idm92438688" class="indexterm"></a><a id="idm92437248" class="indexterm"></a><div class="para">
+ 複数のユーザーを持つ環境においてはとくに、システムの認証ファイルのセキュリティを向上させるために、<span class="package">shadow-utils</span> パッケージにより提供される<em class="firstterm">シャドウパスワード</em>を使用することは非常に重要です。このため、インストールプログラムはデフォルトでシャドウパスワードを有効にします。
+ </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">
+ <span class="package">shadow-utils</span> パッケージにより提供されるユーティリティの多くは、シャドウパスワードが有効かどうかによらず適切に機能します。しかしながら、パスワードエージング情報は <code class="filename">/etc/shadow</code> ファイルにだけ保存されるので、パスワードエージング情報を作成または変更するコマンドはすべて動作しません。以下は最初にシャドウパスワードを有効にしないと動作しないユーティリティとコマンドの一覧です:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">chage</code> ユーティリティ。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">gpasswd</code> ユーティリティ。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">-e</code> または <code class="option">-f</code> オプションをつけた <code class="command">usermod</code> コマンド。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">-e</code> または <code class="option">-f</code> オプションをつけた <code class="command">useradd</code> コマンド。
+ </div></li></ul></div></div></div><div class="section" id="sect-Managing_Users_and_Groups-User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. ユーザー アカウントのツールを使う</h2></div></div></div><a id="idm98385824" class="indexterm"></a><a id="idm130493712" class="indexterm"></a><a id="idm118173392" class="indexterm"></a><div class="para">
+ <span class="application"><strong>ユーザーアカウント</strong></span>設定ツールは、ローカルユーザーを表示、修正、追加、および削除をできます。ツールを実行するには、<span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>システム設定</strong></span>を選択して、<span class="guimenu"><strong>ユーザーアカウント</strong></span>アイコンをクリックします。
+ </div><div class="figure" id="fig-Managing_Users_and_Groups-User_Accounts"><div class="figure-contents"><div class="mediaobject"><img src="images/user-accounts.png" alt="ユーザー アカウントの設定ツール" /><div class="longdesc"><div class="para">
+ ユーザー アカウントの設定ツール
+ </div></div></div></div><h6>図3.1 ユーザー アカウントの設定ツール</h6></div><br class="figure-break" /><div class="para">
+ デフォルトで、ツールは自分のアカウントに関連する特定の設定のみを変更できます。このため、<code class="systemitem">root</code> ユーザーのみがユーザーとグループを設定できます。すべての種類の変更のために設定ツールをロック解除するには、ウィンドウの右上角にある<span class="guibutton"><strong>ロック解除</strong></span>ボタンをクリックして、プロンプトに正しいパスワードを入力します。
+ </div><div class="section" id="sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.1. アカウントの設定</h3></div></div></div><div class="para">
+ アカウントに関連づけられている画像を変更するには、アカウント名の次にあるアイコンをクリックして、プルダウンリストから画像を選択するか、ローカルドライブから画像を使用するために<span class="guimenuitem"><strong>他の画像も参照...</strong></span> をクリックします。
+ </div><div class="para">
+ アカウントに関連する名前を変更するには、編集するために名前の次にあるアイコンをクリックします。
+ </div><div class="para">
+ アカウントの種類を変更するには、<span class="guimenu"><strong>アカウントの種類</strong></span>ラベルの次にあるテキストをクリックします。この変更は、自分自身のアカウントを変更するときでも、設定ツールがロック解除されている必要があることに注意してください。
+ </div><div class="para">
+ アカウントのデフォルトの言語を変更するには、<span class="guilabel"><strong>言語</strong></span>ラベルの次のあるテキストをクリックして、一覧から言語を選択します。
+ </div><div class="para">
+ パスワードを変更するには、<span class="guilabel"><strong>パスワード</strong></span>ラベルの次にあるテキストをクリックします。ダイアログボックスが表示され、新しいパスワードを設定できます。変更を確認するには現在をパスワードを入力しなければいけません。これをすると、変更を保存するために<span class="guibutton"><strong>変更</strong></span>ボタンをクリックします。
+ </div><div class="figure" id="fig-Managing_Users_and_Groups-User_Accounts-Changing_Password"><div class="figure-contents"><div class="mediaobject"><img src="images/user-accounts-password-change.png" alt="パスワードの変更" /><div class="longdesc"><div class="para">
+ パスワードの変更
+ </div></div></div></div><h6>図3.2 パスワードの変更</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>パスワードのセキュリティのアドバイス</h2></div><div class="admonition"><div class="para">
+ 非常に長いパスワードを使用することをお勧めします。これにより、侵入者がパスワードを推測して、権限なくアカウントにアクセスすることを難しくなるからです。また、パスワードは辞書に載っている単語を基にしないことをお勧めします。文字、数字と特殊文字の組み合わせを使用します。
+ </div></div></div><div class="para">
+ 最後に、特定のアカウントに対して自動ログインを設定するには、<span class="guilabel"><strong>自動的にログイン</strong></span>スイッチを有効にします。変更をするには、設定ツールがロック解除されなければいけません。
+ </div></div><div class="section" id="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.2. 新規ユーザーを追加する</h3></div></div></div><a id="idm94590432" class="indexterm"></a><div class="para">
+ 新しいユーザーを追加するには、確実に設定ツールがロック解除して、アカウント一覧の下にある <span class="guibutton"><strong>+</strong></span> ボタン（つまり、プラス記号）をクリックします。ダイアログウィンドウが表示され、ユーザーの詳細を決められます。
+ </div><div class="figure" id="fig-Managing_Users_and_Groups-User_Accounts-Adding_an_Account"><div class="figure-contents"><div class="mediaobject"><img src="images/user-accounts-create.png" alt="新しいアカウントの作成" /><div class="longdesc"><div class="para">
+ 新しいアカウントの作成
+ </div></div></div></div><h6>図3.3 新しいアカウントの作成</h6></div><br class="figure-break" /><div class="para">
+ アカウントを作成するために以下の手順をとります:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ <span class="guimenu"><strong>アカウントの種類</strong></span>プルダウンリストからアカウントの種類を選択します。利用可能なアカウントの種類は<code class="option">管理者</code> と <code class="option">標準</code>（デフォルトのオプション）です。
+ </div></li><li class="step"><div class="para">
+ アカウントに関連づける名前を設定するには、<span class="guilabel"><strong>フルネーム</strong></span>入力フィールドを記入します。この名前はログインマネージャーにより使用され、パネルに表示されます。
+ </div></li><li class="step"><div class="para">
+ <span class="guilabel"><strong>ユーザー名</strong></span>プルダウンリストから推奨されたユーザー名を選択するか、対応する入力フィールドを記入します。
+ </div></li><li class="step"><div class="para">
+ 設定を確認するには、<span class="guibutton"><strong>作成</strong></span>ボタンをクリックします。
+ </div></li></ol></div><div class="para">
+ Fedora は <em class="firstterm">ユーザープライベートグループ</em> (UPG: user private group) スキーマを使用します。UPG スキーマは標準的な UNIX のグループの取り扱い方法を何も追加や変更をしません。新しい利便性を提供します。新規ユーザーを作成すると必ず、ユーザーと同じ名前を持つ一意なグループが作成されます。
+ </div><div class="para">
+ 新規アカウントが作成されたとき、デフォルトの設定ファイルが <code class="filename">/etc/skel/</code> ディレクトリから新規ホームディレクトリの中にコピーされます。
+ </div></div><div class="section" id="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.3. ユーザーの削除</h3></div></div></div><a id="idm86778528" class="indexterm"></a><div class="para">
+ ユーザーを削除するには、設定ツールを確実にロック解除して、アカウント一覧から希望するアカウントを選択して、アカウント一覧の下にある <span class="guibutton"><strong>−</strong></span> ボタン（つまり、マイナス記号）をクリックします。ダイアログが表示され、変更を確認するかキャンセルできます。
+ </div><div class="figure" id="fig-Managing_Users_and_Groups-User_Accounts-Removing_an_Account"><div class="figure-contents"><div class="mediaobject"><img src="images/user-accounts-remove.png" alt="アカウントの削除" /><div class="longdesc"><div class="para">
+ アカウントの削除
+ </div></div></div></div><h6>図3.4 アカウントの削除</h6></div><br class="figure-break" /><div class="para">
+ ユーザーに属しているファイルやディレクトリ（つまり、ホームディレクトリ、メールスプールおよび一時ファイル）を削除するには、<span class="guibutton"><strong>ファイルを削除</strong></span>ボタンをクリックします。これらのファイルをそのまま残して、ユーザーアカウントのみを削除するには、<span class="guibutton"><strong>ファイルを残す</strong></span>をクリックします。削除を中止するには、<span class="guibutton"><strong>キャンセル</strong></span>をクリックします。
+ </div></div></div><div class="section" id="s1-users-configui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.3. ユーザー管理のツールを使う</h2></div></div></div><a id="idm124564208" class="indexterm"></a><a id="idm131551360" class="indexterm"></a><a id="idm85548096" class="indexterm"></a><a id="idm85546528" class="indexterm"></a><a id="idm96254192" class="indexterm"></a><a id="idm96252784" class="indexterm"></a><div class="para">
+ <span class="application"><strong>ユーザー管理</strong></span>アプリケーションにより、グラフィカルユーザーインターフェースにおいてローカルユーザーとグループを表示、編集、追加および削除できます。アプリケーションを起動するには、<span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>その他</strong></span> → <span class="guimenuitem"><strong>ユーザーとグループ</strong></span>を選択するか、シェルプロンプトにおいて <code class="command">system-config-users</code> と入力します。スーパーユーザー権限がなければ、アプリケーションが <code class="systemitem">root</code> として認証するプロンプトを表示することに注意してください。
+ </div><div class="section" id="s2-redhat-config-users-list"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.1. ユーザーとグループを閲覧する</h3></div></div></div><a id="idm103816128" class="indexterm"></a><a id="idm103814720" class="indexterm"></a><div class="para">
+ <span class="application"><strong>ユーザー管理</strong></span>のメインウィンドウは2つのタブに分けられています: <span class="guilabel"><strong>ユーザー</strong></span>タブは、ローカルユーザーの一覧とそのユーザー ID、プライマリグループ、ホームディレクトリ、ログインシェル、およびフルネームに関する追加情報を提供します。<span class="guilabel"><strong>グループ</strong></span>タブは、ローカルグループの一覧とそのグループ ID およびグループのメンバーに関する追加情報を提供します。
+ </div><div class="figure" id="fig-Users_Groups-User_Manager"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager.png" alt="ユーザーとグループを閲覧する" /><div class="longdesc"><div class="para">
+ ユーザーとグループを閲覧する
+ </div></div></div></div><h6>図3.5 ユーザーとグループを閲覧する</h6></div><br class="figure-break" /><div class="para">
+ 特定のユーザーまたはグループを検索するには、<span class="guilabel"><strong>検索フィルター</strong></span>フィールドに最初の数文字を入力して、<span class="keycap"><strong>Enter</strong></span> を押すか、<span class="guibutton"><strong>フィルターの適用</strong></span>ボタンをクリックします。列のヘッダーをクリックすると、利用可能な列は何でも項目を並べ替えることができます。
+ </div><div class="para">
+ Fedora は、1000未満のユーザー ID とグループ ID をシステムユーザーとグループのために予約しています。デフォルトで、<span class="application"><strong>ユーザー管理</strong></span>はシステムユーザーを表示しません。すべてのユーザーとグループを表示するには、<span class="guilabel"><strong>設定</strong></span>ダイアログを開くために<span class="guimenu"><strong>編集</strong></span> → <span class="guimenuitem"><strong>設定</strong></span>を選択して、<span class="guilabel"><strong>システムユーザーとグループを非表示</strong></span>チェックボックスを外します。
+ </div></div><div class="section" id="s2-redhat-config-users-user-new"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.2. 新規ユーザーを追加する</h3></div></div></div><a id="idm120165984" class="indexterm"></a><div class="para">
+ 新しいユーザーを追加するには、<span class="guibutton"><strong>ユーザーの追加</strong></span>ボタンをクリックします。<a class="xref" href="#user-new-fig">図3.6「新しいユーザーを追加する」</a>にあるようなウィンドウが表示されます。
+ </div><div class="figure" id="user-new-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager-add-user.png" alt="新しいユーザーを追加する" /><div class="longdesc"><div class="para">
+ 新しいユーザーを追加する
+ </div></div></div></div><h6>図3.6 新しいユーザーを追加する</h6></div><br class="figure-break" /><div class="para">
+ <span class="guilabel"><strong>新規ユーザーの追加</strong></span>ダイアログボックスにより、新しく作成するユーザーに関する情報を提供できます。ユーザーを作成するために、適切なフィールドにユーザー名とフルネームを、<span class="guilabel"><strong>パスワード</strong></span>と<span class="guilabel"><strong>パスワードの確認</strong></span>フィールドにユーザーのパスワードを入力します。パスワードは少なくても6文字でなければいけません。
+ </div><div class="note"><div class="admonition_header"><h2>パスワードのセキュリティのアドバイス</h2></div><div class="admonition"><div class="para">
+ 非常に長いパスワードを使用することをお勧めします。これにより、侵入者がパスワードを推測して、権限なくアカウントにアクセスすることを難しくなるからです。また、パスワードは辞書に載っている単語を基にしないことをお勧めします。文字、数字と特殊文字の組み合わせを使用します。
+ </div></div></div><div class="para">
+ <span class="guilabel"><strong>ログインシェル</strong></span>プルダウンリストにより、ユーザーのログインシェルを選択できます。選択するシェルが確かではなければ、デフォルトの <span class="guimenuitem"><strong>/bin/bash</strong></span> を受け入れてください。
+ </div><div class="para">
+ デフォルトで、<span class="application"><strong>ユーザー管理</strong></span>アプリケーションは <code class="filename">/home/<em class="replaceable"><code>username</code></em>/</code> に新しいユーザーのためのホームディレクトリを作成します。<span class="guilabel"><strong>ホームディレクトリの作成</strong></span>チェックボックスを外してホームディレクトリを作成しないことを選択できます。または<span class="guilabel"><strong>ホームディレクトリ</strong></span>テキストボックスの内容を編集することにより、このディレクトリを変更できます。ホームディレクトリを作成するときに、デフォルトの設定ファイルが <code class="filename">/etc/skel/</code> ディレクトリの中からコピーされることに注意してください。
+ </div><div class="para">
+ Fedora はユーザープライベートグループ (UPG) スキーマを使用します。新規ユーザーを作成すると必ず、ユーザーと同じ名前を持つ一意なグループがデフォルトで作成されます。このグループを作成したくなければ、<span class="guilabel"><strong>ユーザーのプライベートグループを作成する</strong></span>チェックボックスを外します。
+ </div><div class="para">
+ ユーザーのユーザー ID を指定するには、<span class="guilabel"><strong>ユーザー ID を手動で指定する</strong></span>を選択します。このオプションが選択されなければ、1000以上で次に利用可能なユーザー ID が新規ユーザーに割り当てられます。Fedora は1000未満のユーザー ID をシステムユーザーのために予約しているので、ユーザー ID を手動で 1-999 に割り当てることはお勧めできません。
+ </div><div class="para">
+ <span class="guibutton"><strong>OK</strong></span> ボタンをクリックして新規ユーザーを作成します。パスワード有効期限のようなさらに高度なユーザーのプロパティを設定するには、ユーザーの追加後にユーザーのプロパティを修正します。
+ </div></div><div class="section" id="s2-redhat-config-users-group-new"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.3. 新規グループを追加する</h3></div></div></div><a id="idm125050768" class="indexterm"></a><div class="para">
+ 新規ユーザーグループを追加するには、ツールバーから<span class="guibutton"><strong>グループの追加</strong></span>を選択します。<a class="xref" href="#group-new-fig">図3.7「新規グループ」</a>のようなウィンドウが表示されます。新規グループの名前を入力します。<span class="guilabel"><strong>グループ ID を手動で指定</strong></span>を選択して、GID を選択します。Fedora は1000未満のグループ ID をシステムグループのために予約していることにも注意してください。
+ </div><div class="figure" id="group-new-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager-add-group.png" alt="新規グループ" /><div class="longdesc"><div class="para">
+ Creating a new group
+ </div></div></div></div><h6>図3.7 新規グループ</h6></div><br class="figure-break" /><div class="para">
+ グループを作成するには <span class="guibutton"><strong>OK</strong></span> をクリックします。新規グループがグループ一覧に表示されます。
+ </div></div><div class="section" id="s2-redhat-config-users-user-properties"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.4. ユーザーのプロパティを変更する</h3></div></div></div><a id="idm112279472" class="indexterm"></a><a id="idm113640640" class="indexterm"></a><div class="para">
+ 既存のユーザーのプロパティを表示するには、<span class="guilabel"><strong>ユーザー</strong></span>タブをクリックして、ユーザーの一覧からユーザーを選択します。そして、メニューから<span class="guimenuitem"><strong>プロパティ</strong></span>をクリックします（またはプルダウンメニューから<span class="guimenu"><strong>ファイル</strong></span> → <span class="guimenuitem"><strong>プロパティProperties</strong></span>を選びます）。<a class="xref" href="#user-properties-fig">図3.8「ユーザーのプロパティ」</a>のようなウィンドウが表示されます。
+ </div><div class="figure" id="user-properties-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager-edit-user.png" alt="ユーザーのプロパティ" /><div class="longdesc"><div class="para">
+ Modifying user properties
+ </div></div></div></div><h6>図3.8 ユーザーのプロパティ</h6></div><br class="figure-break" /><div class="para">
+ <span class="guilabel"><strong>ユーザーのプロパティ</strong></span>ウィンドウは複数のタブページに分割されています:
+ </div><a id="idm128958448" class="indexterm"></a><a id="idm128957040" class="indexterm"></a><a id="idm93418048" class="indexterm"></a><a id="idm93416640" class="indexterm"></a><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>アカウント情報</strong></span> — アカウントを特定の日付に失効されたければ、<span class="guilabel"><strong>アカウント失効を有効にする</strong></span>を選択します。ユーザーアカウントをロックして、ユーザーがシステムにログインできないようにするには、<span class="guilabel"><strong>ローカルパスワードがロックされています</strong></span>を選択します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>パスワード情報</strong></span> — ユーザーのパスワードが最後に変更された日付を表示します。特定の日数経過後にパスワードの変更を強制するには、<span class="guilabel"><strong>パスワード失効を有効にする</strong></span>を選択して、<span class="guilabel"><strong>変更が要求されるまでの日数:</strong></span>フィールドに希望する値を入力します。ユーザーのパスワードが失効するまでの日数、パスワードの変更を警告されるまでの日数、アカウントが無効になるまでの日数も変更できます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>グループ</strong></span> — ユーザーのプライマリーグループ、およびユーザーをメンバーにしたいグループを表示および設定することができます。
+ </div></li></ul></div></div><div class="section" id="s2-redhat-config-users-group-properties"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.5. グループのプロパティを変更する</h3></div></div></div><a id="idm96681072" class="indexterm"></a><div class="para">
+ 既存のグループのプロパティを表示するには、グループの一覧からグループを選択して、メニューから<span class="guimenuitem"><strong>プロパティ</strong></span>をクリックします（または、プルダウンメニューから<span class="guimenu"><strong>ファイル</strong></span> → <span class="guimenuitem"><strong>プロパティ</strong></span>を選びます）。<a class="xref" href="#group-properties-fig">図3.9「グループのプロパティ」</a>のようなウィンドウが表示されます。
+ </div><div class="figure" id="group-properties-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager-edit-group.png" alt="グループのプロパティ" /><div class="longdesc"><div class="para">
+ Modifying group properties
+ </div></div></div></div><h6>図3.9 グループのプロパティ</h6></div><br class="figure-break" /><a id="idm124535584" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>グループユーザー</strong></span>タブは、どのユーザーがグループのメンバーであるかを表示します。グループのユーザーを追加または削除するには、このタブを使用します。変更を保存するには <span class="guibutton"><strong>OK</strong></span> をクリックします。
+ </div></div></div><div class="section" id="s1-users-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.4. コマンドラインのツールを使う</h2></div></div></div><a id="idm126297936" class="indexterm"></a><a id="idm119636560" class="indexterm"></a><a id="idm119634480" class="indexterm"></a><a id="idp633168" class="indexterm"></a><div class="para">
+ Fedora においてユーザーとグループを管理する最も簡単な方法は、<a class="xref" href="#s1-users-configui">「ユーザー管理のツールを使う」</a>に説明されているように、<span class="application"><strong>ユーザー管理</strong></span>アプリケーションを使用することです。しかしながら、コマンドラインツールを好むか、X Window System をインストールしていなければ、<a class="xref" href="#table-users-tools">表3.1「ユーザーとグループの管理のためのコマンドライン」</a>に一覧化されているコマンドラインユーティリティを使用できます。
+ </div><div class="table" id="table-users-tools"><h6>表3.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">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></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">3.4.1. 新規ユーザーを追加する</h3></div></div></div><a id="idm122137216" class="indexterm"></a><a id="idm101670688" class="indexterm"></a><a id="idm101669248" class="indexterm"></a><div class="para">
+ 新規ユーザーをシステムに追加するには、シェルプロンプトにおいて <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">
+ …ここで <em class="replaceable"><code>options</code></em> は<a class="xref" href="#table-useradd-options">表3.2「useradd のコマンドライン オプション」</a>において説明されているコマンドラインオプションです。
+ </div><a id="idm118705248" 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">
+ オプションとして、パスワードエージングポリシーを設定することができます。パスワードエージングを有効にする方法は<a class="xref" href="#s2-users-tools-password-aging">「パスワードエージングの有効化」</a>を参照してください。
+ </div><div class="table" id="table-useradd-options"><h6>表3.2 useradd のコマンドライン オプション</h6><div class="table-contents"><table summary="useradd のコマンドライン オプション" 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="">
+ パスワード期限切れ後にアカウントが無効化されるまでの日数です。<code class="literal">0</code> が指定されると、アカウントはパスワード期限切れ後すぐに無効化されます。<code class="literal">-1</code> が指定されると、アカウントはパスワード期限切れ後に無効化されません。
+ </td></tr><tr><td class="">
+ <code class="option">-g</code> <em class="replaceable"><code>group_name</code></em>
+ </td><td class="">
+ ユーザーのデフォルトグループのグループ名とグループ番号です。グループはここに指定される以前から存在していなければなりません。
+ </td></tr><tr><td class="">
+ <code class="option">-G</code> <em class="replaceable"><code>group_list</code></em>
+ </td><td class="">
+ ユーザーがメンバーとなる追加グループ (デフォルト以外) のグループ名とグループ番号をコンマで区切って入れます。グループはここに指定される以前から存在していなければなりません。
+ </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" /><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:501:501::/home/juan:/bin/bash</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">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">
+ オプションの <em class="firstterm">GECOS</em> 情報は空白のままです。
+ </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:501:</pre><div class="para">
+ ユーザーと同じ名前を持つグループは<em class="firstterm">ユーザープライベートグループ</em>と呼ばれます。ユーザープライベートグループの詳細は<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">
+ GID は <code class="filename">/etc/passwd</code> においてユーザー <code class="systemitem">juan</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 -l /home</code>
+total 4
+drwx------. 4 juan juan 4096 Mar 3 18:23 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">
+ <code class="filename">/etc/skel/</code> ディレクトリ（デフォルトのユーザー設定を含みます）の中にあるファイルが新規 <code class="filename">/home/juan/</code> ディレクトリの中にコピーされます:
+ </div><pre class="screen">~]# <code class="command">ls -la /home/juan</code>
+total 28
+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 Jun 22 2010 .bash_logout
+-rw-r--r--. 1 juan juan 176 Jun 22 2010 .bash_profile
+-rw-r--r--. 1 juan juan 124 Jun 22 2010 .bashrc
+drwxr-xr-x. 2 juan juan 4096 Jul 14 2010 .gnome2
+drwxr-xr-x. 4 juan juan 4096 Nov 23 15:09 .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">3.4.2. 新規グループを追加する</h3></div></div></div><a id="idm102441600" class="indexterm"></a><a id="idm102440000" 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">
+ …ここで <em class="replaceable"><code>options</code></em> は<a class="xref" href="#table-groupadd-options">表3.3「groupadd のコマンドライン オプション」</a>に説明されているコマンドラインオプションです。
+ </div><div class="table" id="table-groupadd-options"><h6>表3.3 groupadd のコマンドライン オプション</h6><div class="table-contents"><table summary="groupadd のコマンドライン オプション" 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="">
+ 重複したグループの作成を許可します。
+ </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">3.4.3. パスワードエージングの有効化</h3></div></div></div><a id="idm77793664" class="indexterm"></a><a id="idm60669696" class="indexterm"></a><a id="idm99874352" class="indexterm"></a><a id="idm99873424" class="indexterm"></a><a id="idm109034032" class="indexterm"></a><div class="para">
+ セキュリティの理由から、ユーザーがパスワードを定期的に変更するよう要求することをお勧めします。<span class="application"><strong>ユーザーの管理</strong></span>アプリケーションの<span class="guilabel"><strong>パスワード情報</strong></span>タブにおいてユーザーを追加または編集するときに、または <code class="command">chage</code> コマンドを使用することにより、これを実行できます。
+ </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="idm120103040" 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">表3.4「chhage のコマンドライン オプション」</a>において説明されているコマンドラインオプションです。<code class="command">chage</code> コマンドが直接ユーザー名を引数としているとき (つまり、コマンドラインオプションを何も指定していないとき)、現在のパスワードエージング値が表示され、対話的に変更することができます。
+ </div><div class="table" id="table-chage-options"><h6>表3.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">3.4.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">yum</code> <code class="option">install</code> <code class="option">screen</code></pre><div class="para">
+ Fedora にパッケージをインストールする方法の詳細は、<a class="xref" href="#sec-Installing">「パッケージのインストール」</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">3.4.5. グループ用ディレクトリーの作成</h3></div></div></div><a id="idm121513792" class="indexterm"></a><a id="idm86000768" class="indexterm"></a><div class="para">
+ システム管ç†è€…ã¯é€šå¸¸ã€ä¸»è¦ãªå„プãƒã‚¸ã‚§ã‚¯ãƒˆã«å¯¾ã™ã‚‹ã‚°ãƒ«ãƒ¼ãƒ—を作æˆã—ã¦ã€ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚¢ã‚¯ã‚»ã‚¹ãŒå¿…è¦ãªã¨ãã«ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’グループã«å‰²ã‚Šå½“ã¦ãŸã„ã¨è€ƒãˆã¾ã™ã€‚ã“ã®ä¼çµ±çš„ãªã‚¹ã‚ーマを用ã„ã‚‹ã¨ã€ãƒ•ã‚¡ã‚¤ãƒ«ç®¡ç†ã¯é›£ã—ã„ã§ã™ã€‚誰ã‹ãŒãƒ•ã‚¡ã‚¤ãƒ«ã‚’作æˆã™ã‚‹ã¨ãã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒå±žã—ã¦ã„るプライマリグループã¨é–¢é€£ã¥ã‘られã¾ã™ã€‚一人ãŒè¤‡æ•°ã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã«ãŠã„ã¦ä»•äº‹ã‚’ã—ã¦ã„ã‚‹ã¨ãã€æ£ã—ã„ファイルã¨æ£ã—ã„グループを関連ã¥ã‘ã‚‹ã“ã¨ã¯é›£ã—ã„ã§ã™ã€‚ã—ã‹ã—ãªãŒã‚‰ã€UPG スã‚ーマを用ã„ã‚‹ã¨ã€ã‚°ãƒ«ãƒ¼ãƒ—ã¯è‡ªå‹•çš„ã« <em class="firstterm">setgid</em> ビットãŒè¨å®šã•ã‚ŒãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã®ä¸ã«ä½œæˆã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã«å‰²ã‚Šå½“ã¦ã‚‰ã‚Œã¾ã™ã€‚ãã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã®ä¸ã«ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒä½œæˆã™ã‚‹ã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¤ãƒ«ã¯ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã‚’所有ã—ã¦ã„ã‚‹ã‚°ã
ƒ«ãƒ¼ãƒ—ã«ã‚ˆã‚Šæ‰€æœ‰ã•ã‚Œã‚‹ã®ã§ã€setgid ビットã¯å…±é€šã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã‚’共有ã™ã‚‹ã‚°ãƒ«ãƒ¼ãƒ—プãƒã‚¸ã‚§ã‚¯ãƒˆã®ç®¡ç†ã‚’éžå¸¸ã«ã‚·ãƒ³ãƒ—ルã«ã—ã¾ã™ã€‚
+ </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">
+ ユーザーがディレクトリの中にファイルを作成できるようして、setgid ビットを設定します:
+ </div><pre class="screen"><code class="command">chmod 2775 /opt/myproject</code></pre></li></ol></div><div class="para">
+ ここで、<code class="systemitem">myproject</code> グループのすべてのメンバーは、ユーザーが新しいファイルを作成するときはいつでも管理者がファイルのパーミッションを変更する必要がなく、<code class="filename">/opt/myproject/</code> ディレクトリにファイルを作成および編集できます。パーミッションが正しく設定されていることを確認するには、以下のコマンドを実行してください:
+ </div><pre class="screen">~]# <code class="command">ls -l /opt</code>
+total 4
+drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 myproject</pre></div></div><div class="section" id="s1-users-groups-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.5. その他のリソース</h2></div></div></div><a id="idm123234432" class="indexterm"></a><a id="idm123232992" class="indexterm"></a><div class="para">
+ ユーザーとグループの管理に関する詳細は以下のリソースを参照してください。
+ </div><div class="section" id="s2-users-groups-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.5.1. インストールされているドキュメント</h3></div></div></div><a id="idm137452256" class="indexterm"></a><a id="idm105536128" class="indexterm"></a><div class="para">
+ ユーザーとグループを管理するためのさまざまなユーティリティに関する詳細は、以下のマニュアルページを参照してください:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>chage</strong></span>(1) — パスワードのエージングポリシーとアカウントの期限切れ日を変更するためのコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>gpasswd</strong></span>(1) — <code class="filename">/etc/group</code> ファイルを管理するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>groupadd</strong></span>(8) — グループを追加するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>grpck</strong></span>(8) — <code class="filename">/etc/group</code> ファイルを検証するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>groupdel</strong></span>(8) — グループを削除するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>groupmod</strong></span>(8) — グループのメンバーを修正するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>pwck</strong></span>(8) — <code class="filename">/etc/passwd</code> と <code class="filename">/etc/shadow</code> ファイルを検証するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>pwconv</strong></span>(8) — 標準的なパスワードから shadow 形式のパスワードに変換するツールです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>pwunconv</strong></span>(8) — shadow 形式のパスワードから標準的なパスワードに変換するツールです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>useradd</strong></span>(8) — ユーザーを追加するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>userdel</strong></span>(8) — ユーザーを削除するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>usermod</strong></span>(8) — ユーザーを修正するコマンドです。
+ </div></li></ul></div><div class="para">
+ 関連する設定ファイルに関する詳細は、以下を参照してください:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>group</strong></span>(5) — システムのグループ情報を含むファイルです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>passwd</strong></span>(5) — システムのユーザー情報を含むファイルです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>shadow</strong></span>(5) — パスワードおよびシステムに対するアカウント期限切れ情報を含むファイルです。
+ </div></li></ul></div></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="idm91655888"><div></div><div class="para">
+ Fedora システムにおいてすべてのソフトウェアは、インストール、更新、または削除できる RPM パッケージに分割されています。このパートは Fedora において <span class="application"><strong>Yum</strong></span> およびグラフィカルなパッケージ管理ツールの <span class="application"><strong>PackageKit</strong></span> 製品群を使用してパッケージを管理する方法を説明しています。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="#ch-yum">4. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">4.1. パッケージの確認と更新</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">4.1.1. 更新の確認</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">4.1.2. パッケージの更新</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">4.1.3. 設定ファイル変更の保存</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">4.2. パッケージとパッケージ グループ</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Packages">4.2.1. パッケージの検索</a></span></dt><dt><span class="section"><a href="#sec-Listing_Packages">4.2.2. パッケージの一覧</a></span></dt><dt><span
class="section"><a href="#sec-Displaying_Package_Information">4.2.3. パッケージ情報の表示</a></span></dt><dt><span class="section"><a href="#sec-Installing">4.2.4. パッケージのインストール</a></span></dt><dt><span class="section"><a href="#sec-Removing">4.2.5. パッケージの削除</a></span></dt><dt><span class="section"><a href="#sec-Yum-Transaction_History">4.2.6. 処理とトランザクションの履歴</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">4.3. Yum と Yum リポジトリーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">4.3.1. [main] オプションの設定</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">4.3.2. [repository] オプションの設定</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">4.3.3. Yum 変数の使い方</a></span></dt><dt><span class="section"><a h
ref="#sec-Viewing_the_Current_Configuration">4.3.4. 現在の設定の表示</a></span></dt><dt><span class="section"><a href="#sec-Managing_Yum_Repositories">4.3.5. Yum リポジトリの追加・有効化および無効化</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">4.3.6. Yum リポジトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">4.4. Yum プラグイン</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Yum プラグインの無効化、有効化、設定</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">4.4.2. 追加の Yum プラグインのインストール</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">4.4.3. プラグインの説明</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Additional_Resources">4.5. その他のリソース</a
></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-PackageKit">5. PackageKit</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Updating_Packages_with_Software_Update">5.1. ソフトウェアã®æ›´æ–°ã‚’用ã„ãŸãƒ‘ッケージã®æ›´æ–°</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_preferences_for_checking_for_updates">5.1.1. æ›´æ–°ã®ç¢ºèªé–“éš”ã®è¨å®š</a></span></dt><dt><span class="section"><a href="#sec-Setting_preferences_for_software_sources">5.1.2. ソフトウェアソースã®è¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_Add_Remove_Software">5.2. ソフトウェアã®è¿½åŠ /削除ã®ä½¿ç”¨</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. ソフトウェアソースã®æ›´æ–° (Yum リãƒã‚¸ãƒˆãƒªãƒ¼)</a></span></dt><dt><span class="section"><a href="#sec-Finding_Packages_with_Filters">5.2.2. フィルターを用ã„ãŸãƒ
‘ッケージã®æ¤œç´¢</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Packages_and_Dependencies">5.2.3. パッケージ（ãŠã‚ˆã³ä¾å˜ã™ã‚‹ã‚‚ã®ï¼‰ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Package_Groups">5.2.4. パッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Transaction_Log">5.2.5. トランザクションãƒã‚°ã®è¡¨ç¤º</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-PackageKit_Architecture">5.3. PackageKit アーã‚テクãƒãƒ£ãƒ¼</a></span></dt><dt><span class="section"><a href="#ch-Graphical_Package_Management-sec-Additional_Resources">5.4. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd></dl></div></div><div xml:lang="ja-JP" class="chapter" id="ch-yum" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第4ç« Yum</h2></div></div></div><div class=
"toc"><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">4.1. パッケージの確認と更新</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">4.1.1. 更新の確認</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">4.1.2. パッケージの更新</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">4.1.3. 設定ファイル変更の保存</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">4.2. パッケージとパッケージ グループ</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Packages">4.2.1. パッケージの検索</a></span></dt><dt><span class="section"><a href="#sec-Listing_Packages">4.2.2. パッケージの一覧</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Package_Information">4.2.3. パッケージ情報の表示</a></span></dt><dt><span
class="section"><a href="#sec-Installing">4.2.4. パッケージのインストール</a></span></dt><dt><span class="section"><a href="#sec-Removing">4.2.5. パッケージの削除</a></span></dt><dt><span class="section"><a href="#sec-Yum-Transaction_History">4.2.6. 処理とトランザクションの履歴</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">4.3. Yum と Yum リポジトリーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">4.3.1. [main] オプションの設定</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">4.3.2. [repository] オプションの設定</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">4.3.3. Yum 変数の使い方</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Current_Configuration">4.3.4. 現在の設定の表示</a></span></dt><dt><span class="section"><a hre
f="#sec-Managing_Yum_Repositories">4.3.5. Yum リポジトリの追加・有効化および無効化</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">4.3.6. Yum リポジトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">4.4. Yum プラグイン</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Yum プラグインの無効化、有効化、設定</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">4.4.2. 追加の Yum プラグインのインストール</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">4.4.3. プラグインの説明</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Additional_Resources">4.5. その他のリソース</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> は、パッケージに関する情報を問い合わせる、リポジトリからパッケージを取得する、自動的に依存解決を使用してパッケージをインストールおよびアンインストールする、システム全体を最新の利用可能なパッケージに更新することができる、The Fedora Project パッケージマネージャーです。Yum は更新、インストール、削除しているパッケージの依存解決を自動的に実行します。このように、利用可能な依存するパッケージをすべて自動的に決定、取得、インストールできます。Yum は新規リポジトリ、追加リポジトリ、または<em class="firstterm">パッケージソース</em>を用いて設定できます。また、機能を向上および拡張させる多くのプラグインも提供します。Yum は <span class="application"><strong>RPM</s
trong></span> ができるのと同じ作業の多くを実行できます。さらに、同様のコマンドラインオプションを持ちます。Yum は単独のマシンまたはそれらのグループにおいて簡単でシンプルなパッケージ管理をできるようにします。
+ </div><div class="important" id="important-Secure_Package_Management_with_GPG-Signed_Packages"><div class="admonition_header"><h2>GPG 署名パッケージを用いたセキュアなパッケージ管理</h2></div><div class="admonition"><div class="para">
+ Yum 㯠GPG ç½²åã•ã‚ŒãŸãƒ‘ッケージã«ãŠã„㦠GPG (Gnu Privacy Guardã€GnuPGã¨ã—ã¦ã‚‚知られã¦ã„ã¾ã™) ç½²åã®æ¤œè¨¼ã‚’ã€ã™ã¹ã¦ã®ãƒ‘ッケージリãƒã‚¸ãƒˆãƒªã¾ãŸã¯å€‹ã€…ã®ãƒªãƒã‚¸ãƒˆãƒªã«å¯¾ã—ã¦æœ‰åŠ¹ã«ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã‚»ã‚ュアãªãƒ‘ッケージ管ç†ã‚’æä¾›ã—ã¾ã™ã€‚ç½²å検証ãŒæœ‰åŠ¹ã«ã•ã‚ŒãŸã¨ãã€Yum ã¯ãƒªãƒã‚¸ãƒˆãƒªã«å¯¾ã—ã¦æ£ã—ã„ã‚ーを用ã„㦠GPG ç½²åã•ã‚Œã¦ã„ãªã„ã‚らゆるパッケージをインストールã™ã‚‹ã“ã¨ã‚’æ‹’å¦ã—ã¾ã™ã€‚ã¤ã¾ã‚Šã€The Fedora Project ã®ã‚ˆã†ãªä¿¡é ¼ã•ã‚ŒãŸã‚½ãƒ¼ã‚¹ã‹ã‚‰ã‚·ã‚¹ãƒ†ãƒ ã«ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã—ã¦ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¦ã€è»¢é€ä¸ã«å¤‰æ›´ã•ã‚Œã¦ã„ãªã„ã“ã¨ã‚’ä¿¡é ¼ã§ãã¾ã™ã€‚Yum を用ã„ã¦ç½²å検証を有効ã«ã™ã‚‹ã“ã¨ã«é–¢ã™ã‚‹è©³ç´°ã¯<a class="xref" href="#sec-Configuring_Yum_and_Yum_Repositories">「Yum 㨠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¨å®šã€</a>ã‚’å‚ç…§ã—ã¦ãã ã•ã„ã€ã¾ãŸã¯ä¸€èˆ¬ã« GPG ç½²åã•ã‚Œã
Ÿ <span class="application"><strong>RPM</strong></span> パッケージを検証ã™ã‚‹ã“ã¨ã«ã¤ã„ã¦ã¯<a class="xref" href="#s1-check-rpm-sig">「パッケージã®ç½²åを確èªã™ã‚‹ã€</a>ã‚’å‚ç…§ã—ã¦ãã ã•ã„。
+ </div></div></div><div class="para">
+ Yum は他のマシンにある <span class="application"><strong>RPM</strong></span> パッケージのダウンロードとインストールのために自身のリポジトリを簡単に設定することができます。
+ </div><div class="para">
+ Yum はシステム管理作業を実行する最も速い方法であり、<span class="application"><strong>PackageKit</strong></span> グラフィカルパッケージ管理アプリケーションにより提供されるものを超えた機能を提供するので、Yum を学習することは価値のある投資です。<span class="application"><strong>PackageKit</strong></span> の使い方の詳細は<a class="xref" href="#ch-PackageKit">5章<em>PackageKit</em></a>を参照してください。
+ </div><div class="note" id="note-Note_Yum_and_Superuser_Privileges"><div class="admonition_header"><h2>Yum とスーパーユーザー権限</h2></div><div class="admonition"><div class="para">
+ インストールに <code class="command">yum</code> を使用するためには、スーパーユーザー権限を持っていなければいけません。本章にあるすべての例は、<code class="command">su</code> または <code class="command">sudo</code> コマンドを使用することにより、スーパーユーザー権限をすでに持っていることを前提にしています。
+ </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">4.1. パッケージの確認と更新</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">4.1.1. 更新の確認</h3></div></div></div><a id="idm71327600" class="indexterm"></a><div class="para">
+ システムにインストールされているパッケージが利用可能な更新があるかを確認するには、以下のコマンドを使用します
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">check-update</code></pre><div class="para">
+ 例:
+ </div><pre class="screen">~]# <code class="command">yum check-update</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+
+PackageKit.x86_64 0.6.14-2.fc15 fedora
+PackageKit-command-not-found.x86_64 0.6.14-2.fc15 fedora
+PackageKit-device-rebind.x86_64 0.6.14-2.fc15 fedora
+PackageKit-glib.x86_64 0.6.14-2.fc15 fedora
+PackageKit-gstreamer-plugin.x86_64 0.6.14-2.fc15 fedora
+PackageKit-gtk-module.x86_64 0.6.14-2.fc15 fedora
+PackageKit-gtk3-module.x86_64 0.6.14-2.fc15 fedora
+PackageKit-yum.x86_64 0.6.14-2.fc15 fedora
+PackageKit-yum-plugin.x86_64 0.6.14-2.fc15 fedora
+gdb.x86_64 7.2.90.20110429-36.fc15 fedora
+kernel.x86_64 2.6.38.6-26.fc15 fedora
+rpm.x86_64 4.9.0-6.fc15 fedora
+rpm-libs.x86_64 4.9.0-6.fc15 fedora
+rpm-python.x86_64 4.9.0-6.fc15 fedora
+yum.noarch 3.2.29-5.fc15 fedora</pre><div class="para">
+ 上の出力にあるパッケージは利用可能な更新があるものとして一覧化されています。一覧にある最初のパッケージは <span class="application"><strong>PackageKit</strong></span> というグラフィカルパッケージマネージャーです。出力例にある行は次のことを意味します:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">PackageKit</code> — パッケージの名前
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">x86_64</code> — パッケージがビルトされた対象の CPU アーキテクチャー
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">0.6.14</code> — インストールされる更新パッケージのバージョン
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">fedora</code> — 更新パッケージが置かれているリポジトリー
+ </div></li></ul></div><div class="para">
+ カーネル（kernel パッケージ）、Yum および <span class="application"><strong>RPM</strong></span> 自身（<code class="filename">yum</code> および <code class="filename">rpm</code> パッケージ）だけでなく、その依存物（<span class="package">kernel-firmware</span>, <span class="package">rpm-libs</span>, および <span class="package">rpm-python</span> パッケージのような）をすべて <code class="command">yum</code> を使用して更新できることを出力は示しています。
+ </div></div><div class="section" id="sec-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.2. パッケージの更新</h3></div></div></div><a id="idm82310384" class="indexterm"></a><div class="para">
+ 単一パッケージ、複数パッケージまたは全パッケージを一度に更新することを選べます。更新するパッケージに依存するあらゆるものに利用可能な更新があれば、それらも更新されます。
+ </div><h4 id="bh-Updating_a_Single_Package">シンプルなパッケージの更新</h4><a id="idm124622800" class="indexterm"></a><div class="para">
+ <code class="systemitem">root</code> で次のコマンドを実行し、ひとつのパッケージを更新します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">update</code> <em class="replaceable"><code>package_name</code></em></pre><div class="para">
+ たとえば、<span class="package">udev</span> パッケージを更新するには、次のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">yum update udev</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Updating Red Hat repositories.
+INFO:rhsm-app.repolib:repos updated: 0
+Setting up Update Process
+Resolving Dependencies
+--> Running transaction check
+---> Package gdb.x86_64 0:7.2.90.20110411-34.fc15 will be updated
+---> Package gdb.x86_64 0:7.2.90.20110429-36.fc15 will be an update
+--> Finished Dependency Resolution
+
+Dependencies Resolved
+
+================================================================================
+ Package Arch Version Repository Size
+================================================================================
+Updating:
+ gdb x86_64 7.2.90.20110429-36.fc15 fedora 1.9 M
+
+Transaction Summary
+================================================================================
+Upgrade 1 Package(s)
+
+Total download size: 1.9 M
+Is this ok [y/N]:</pre><div class="para">
+ この出力は関心がある項目をいくつか含んでいます:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="computeroutput">Loaded plugins:</code> — <code class="command">yum</code> はインストールされて有効にされている <span class="application"><strong>Yum</strong></span> プラグインを必ず通知します。ここでは、<code class="command">yum</code> が <span class="application"><strong>langpacks</strong></span>, <span class="application"><strong>presto</strong></span>, および <span class="application"><strong>refresh-packagekit</strong></span> プラグインを使用しています。<span class="application"><strong>Yum</strong></span> プラグインに関する一般的な情報は<a class="xref" href="#sec-Yum_Plugins">「Yum プラグイン」</a>を参照してください、または特定のプラグインの説明は<a class="xref" href="#sec-Plugin_Descriptions">「プラグインの説明」</a>を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">gdb.x86_64</code> — 新しい <span class="package">gdb</span> パッケージのダウンロードとインストールができます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum</code> は、更新の情報を表示して、更新を実行したいかどうかを確認します。<code class="command">yum</code> はデフォルトで対話的に動作します。どのトランザクションが実行する <code class="command">yum</code> 計画をすでに知っているならば、<code class="command">yum</code> が尋ねてくる質問にすべて <code class="command">yes</code> を答えるように <code class="option">-y</code> オプションを使用できます（非対話的に実行する場合です）。しかしながら、発生したあらゆる問題を簡単にトラブルシューティングできるように、どのような変更がシステムに対して行われるか <code class="command">yum</code> 計画を常に確認すべきです。
+ </div><div class="para">
+ トランザクションがうまくいかなければ、<a class="xref" href="#sec-Yum-Transaction_History">「処理とトランザクションの履歴」</a> に説明されているように <code class="command">yum history</code> コマンドを使用することにより、 Yum のトランザクション履歴を表示することができます。
+ </div></li></ol></div><div class="important" id="important-Important-Updating_and_Installing_Kernels_with_Yum"><div class="admonition_header"><h2>Yum でのカーネルのインストールとアップグレード</h2></div><div class="admonition"><div class="para">
+ コマンド <code class="command">rpm -i kernel</code> を使用するときに <span class="application"><strong>RPM</strong></span> が新しいカーネルをインストールするのと同じ意味で、<code class="command">yum</code> は必ず新しいカーネルを<span class="emphasis"><em>インストール</em></span>します。そのため、<code class="command">yum</code> を使用するときにカーネルを<span class="emphasis"><em>インストール</em></span>するのか<span class="emphasis"><em>更新</em></span>するのかについて心配する必要がありません。 <code class="command">yum update</code> または <code class="command">yum install</code> コマンドのどちらを使用しているかに関わらず、適切なものを実行します。
+ </div><div class="para">
+ 一方、<span class="application"><strong>RPM</strong></span> を使用しているときは、<code class="command">rpm -u kernel</code> (現在のカーネルを<span class="emphasis"><em>置き換えます</em></span>) の代わりに、<code class="command">rpm -i kernel</code> コマンド (新しいカーネルをインストールします) を使用することが重要です。<span class="application"><strong>RPM</strong></span> を用いたカーネルのインストール/アップグレードの詳細は<a class="xref" href="#sec-Installing_and_Upgrading">「インストールとアップグレード」</a>を参照してください。
+ </div></div></div><h4 id="bh-Updating_All_Packages_and_Their_Dependencies">全パッケージおよびそれらの依存性の更新</h4><a id="idm138241792" class="indexterm"></a><div class="para">
+ すべてのパッケージとそれに依存するものを更新するには、単に <code class="command">yum update</code> と入力します（引数は何もありません）:
+ </div><pre class="screen"><code class="command">yum update</code></pre><h4 id="bh-Updating_Security-Related_Packages">セキュリティ関連のパッケージの更新</h4><a id="idm108403936" class="indexterm"></a><a id="idm124639344" class="indexterm"></a><a id="idm124637968" class="indexterm"></a><div class="para">
+ 利用可能なセキュリティ更新を持つパッケージを発見すること、そしてそれらのパッケージを迅速かつ簡単に更新することは重要です。Yum はこの目的のためのプラグインを提供します。<span class="application"><strong>security</strong></span> プラグインはセキュリティ中心のコマンド、サブコマンドおよびオプションの組を用いて <code class="command">yum</code> コマンドを拡張します。具体的な情報は<a class="xref" href="#sec-Plugin_Descriptions">「プラグインの説明」</a>を参照してください。
+ </div></div><div class="section" id="sec-Preserving_Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.3. 設定ファイル変更の保存</h3></div></div></div><a id="idm132455904" class="indexterm"></a><div class="para">
+ あなたは自分の Fedora システムを使用するので、パッケージによりインストールされた設定ファイルに必ず変更するでしょう。Yum がシステムに変更を実行するために使用する <span class="application"><strong>RPM</strong></span> は、それらの完全性を保証するためのメカニズムを提供します。パッケージの更新をまたがり設定ファイルへの変更を管理する方法の詳細は<a class="xref" href="#sec-Installing_and_Upgrading">「インストールとアップグレード」</a>を参照してください。
+ </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">4.2. パッケージとパッケージ グループ</h2></div></div></div><a id="idm113841776" class="indexterm"></a><a id="idm93028864" class="indexterm"></a><div class="section" id="sec-Searching_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.1. パッケージの検索</h3></div></div></div><a id="idm89475264" class="indexterm"></a><a id="idm18196320" class="indexterm"></a><div class="para">
+ 次のコマンドですべての <acronym class="acronym">RPM</acronym> パッケージ名や説明、要約で検索できます。
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">search</code> <em class="replaceable"><code>term</code></em>…</pre><div class="para">
+ このコマンドは各項目に一致するものの一覧を表示します。たとえば、<span class="quote">「<span class="quote">meld</span>」</span> または <span class="quote">「<span class="quote">kompare</span>」</span> に一致するすべてのパッケージを一覧表示するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum 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="idm147813376" class="indexterm"></a><a id="idm134888768" class="indexterm"></a><div class="para">
+ <code class="command">yum search</code> コマンドは、名前はよくわからないが、関連する語句を知っているパッケージを検索するために有用です。
+ </div></div><div class="section" id="sec-Listing_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.2. パッケージの一覧</h3></div></div></div><a id="idm133361872" class="indexterm"></a><a id="idm115881168" class="indexterm"></a><div class="para">
+ <code class="command">yum list</code> および関連するコマンドは、パッケージ、パッケージのグループおよびリポジトリーに関する情報を提供します。
+ </div><div class="para">
+ すべての Yum の list コマンドは引数として複数の<em class="firstterm">グロブ表現</em>を追加することにより結果をフィルターできます。グロブ表現は、ワイルドカード文字 <code class="command">*</code> (あらゆる文字に複数回マッチするよう展開されます) および <code class="command">?</code> (あらゆる文字に1回マッチするよう展開されます) を複数含む文字列です。
+ </div><div class="note" id="note-Tip-Filtering_Results_with_Glob_Expressions"><div class="admonition_header"><h2>glob 表記で結果のフィルタリング</h2></div><div class="admonition"><a id="idm115232960" class="indexterm"></a><a id="idm106770800" class="indexterm"></a><div class="para">
+ 引数を <code class="command">yum</code> コマンドに渡すとき、グロブ表現をエスケープすることに注意してください。そうでなければ、Bash シェルはこれらの表現を<em class="firstterm">パス名 拡張</em>として解釈します。潜在的にグロブに一致する現在のディレクトリにあるすべてのファイルを <code class="command">yum</code> に渡します。グロブ表現が意図したとおり <code class="command">yum</code> に渡されることを確実にするには、次のようにします:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ バックスラッシュを手前につけることによりワイルドカード文字を
+ </div></li><li class="listitem"><div class="para">
+ グロブ表現全体を二重引用符または引用符でくくります
+ </div></li></ul></div><div class="para">
+ これらの方法の使用例は<a class="xref" href="#ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions">例4.1「すべての ABRT アドオンとプラグインのグロブ表現を用いた一覧表示」</a>および<a class="xref" href="#ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards">例4.4「エスケープされたワイルドカード文字を用いた単一グロブ表現を使用した利用可能なパッケージの一覧表示」</a>を参照してください。
+ </div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">yum list <em class="replaceable"><code>glob_expression</code></em>…</code></span></dt><dd><div class="para">
+ 全 glob 表記に一致するインストール済みと利用できるパッケージ情報の一覧です。
+ </div><div class="example" id="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions"><h6>例4.1 すべての ABRT アドオンとプラグインのグロブ表現を用いた一覧表示</h6><div class="example-contents"><div class="para">
+ さまざまな ABRT アドオンとプラグインを持つパッケージは <span class="quote">「<span class="quote">abrt-addon-</span>」</span> または <span class="quote">「<span class="quote">abrt-plugin-</span>」</span> から始まります。これらのパッケージを一覧表示するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum list abrt-addon\* abrt-plugin\*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+abrt-addon-ccpp.x86_64 2.0.2-5.fc15 @fedora
+abrt-addon-kerneloops.x86_64 2.0.2-5.fc15 @fedora
+abrt-addon-python.x86_64 2.0.2-5.fc15 @fedora
+abrt-plugin-bugzilla.x86_64 2.0.2-5.fc15 @fedora
+abrt-plugin-logger.x86_64 2.0.2-5.fc15 @fedora
+Available Packages
+abrt-plugin-mailx.x86_64 2.0.2-5.fc15 updates
+abrt-plugin-reportuploader.x86_64 2.0.2-5.fc15 updates
+abrt-plugin-rhtsupport.x86_64 2.0.2-5.fc15 updates</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm85337760" class="indexterm"></a>
+ <a id="idm85335872" class="indexterm"></a>
+ <code class="command">yum list all</code></span></dt><dd><div class="para">
+ インストール済み<span class="emphasis"><em>かつ</em></span>利用可能なパッケージの一覧です。
+ </div><div class="example" id="ex-Listing_all_installed_and_available_packages"><h6>例4.2 インストール済みと利用できる全パッケージの一覧</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum list all</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+ConsoleKit.x86_64 0.4.4-1.fc15 @fedora
+ConsoleKit-libs.x86_64 0.4.4-1.fc15 @fedora
+ConsoleKit-x11.x86_64 0.4.4-1.fc15 @fedora
+GConf2.x86_64 2.32.3-1.fc15 @fedora
+GConf2-gtk.x86_64 2.32.3-1.fc15 @fedora
+ModemManager.x86_64 0.4-7.git20110201.fc15 @fedora
+NetworkManager.x86_64 1:0.8.998-4.git20110427.fc15 @fedora
+NetworkManager-glib.x86_64 1:0.8.998-4.git20110427.fc15 @fedora
+NetworkManager-gnome.x86_64 1:0.8.998-4.git20110427.fc15 @fedora
+NetworkManager-openconnect.x86_64 0.8.1-9.git20110419.fc15 @fedora
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm116564768" class="indexterm"></a>
+ <a id="idm100324800" class="indexterm"></a>
+ <code class="command">yum list installed</code></span></dt><dd><div class="para">
+ システムにインストールされているすべてのパッケージを一覧表示します。出力の一番右の列は、パッケージが取得されたリポジトリーを表示します。
+ </div><div class="example" id="ex-Listing_installed_packages_using_a_double-quoted_glob_expression"><h6>例4.3 二重引用符のグロブ表現を用いたインストール済みパッケージの一覧表示</h6><div class="example-contents"><div class="para">
+ 厳密に <span class="quote">「<span class="quote">krb</span>」</span> から始まり1文字以上の文字とハイフンが続く、インストール済みパッケージをすべて表示するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum list installed "krb?-*"</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+krb5-libs.x86_64 1.9-7.fc15 @fedora</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm138515296" class="indexterm"></a>
+ <a id="idm138513408" class="indexterm"></a>
+ <code class="command">yum list available</code></span></dt><dd><div class="para">
+ 有効な全リポジトリーと利用できる全パッケージの一覧です。
+ </div><div class="example" id="ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards"><h6>例4.4 エスケープされたワイルドカード文字を用いた単一グロブ表現を使用した利用可能なパッケージの一覧表示</h6><div class="example-contents"><div class="para">
+ <span class="quote">「<span class="quote">gstreamer</span>」</span> とその後に <span class="quote">「<span class="quote">plugin</span>」</span> を含む名前を持つ利用可能なパッケージをすべて表示するには、以下のコマンドを実行します:
+ </div><pre class="screen">~]# <code class="command">yum list available gstreamer\*plugin\*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Available Packages
+gstreamer-plugin-crystalhd.x86_64 3.5.1-1.fc14 fedora
+gstreamer-plugins-bad-free.x86_64 0.10.22-1.fc15 updates
+gstreamer-plugins-bad-free-devel.x86_64 0.10.22-1.fc15 updates
+gstreamer-plugins-bad-free-devel-docs.x86_64 0.10.22-1.fc15 updates
+gstreamer-plugins-bad-free-extras.x86_64 0.10.22-1.fc15 updates
+gstreamer-plugins-base.x86_64 0.10.33-1.fc15 updates
+gstreamer-plugins-base-devel.x86_64 0.10.33-1.fc15 updates
+gstreamer-plugins-base-devel-docs.noarch 0.10.33-1.fc15 updates
+gstreamer-plugins-base-tools.x86_64 0.10.33-1.fc15 updates
+gstreamer-plugins-espeak.x86_64 0.3.3-3.fc15 fedora
+gstreamer-plugins-fc.x86_64 0.2-2.fc15 fedora
+gstreamer-plugins-good.x86_64 0.10.29-1.fc15 updates
+gstreamer-plugins-good-devel-docs.noarch 0.10.29-1.fc15 updates</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm86035904" class="indexterm"></a>
+ <a id="idm86034016" class="indexterm"></a>
+ <code class="command">yum grouplist</code></span></dt><dd><div class="para">
+ 全パッケージ グループの一覧です。
+ </div><div class="example" id="ex-Listing_all_package_groups"><h6>例4.5 全パッケージ グループの一覧</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum grouplist</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">[出力の省略]</span></em></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm115480592" class="indexterm"></a>
+ <a id="idm115478704" class="indexterm"></a>
+ <code class="command">yum repolist</code></span></dt><dd><div class="para">
+ <span class="emphasis"><em>有効な</em></span> 各リポジトリーに対してリポジトリー ID、名前、および提供されるパッケージ数を一覧表示します。
+ </div><div class="example" id="ex-Listing_enabled_repositories"><h6>例4.6 有効なリポジトリーの一覧表示</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum repolist</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+repo id repo name status
+fedora Fedora 15 - i386 19,365
+updates Fedora 15 - i386 - Updates 3,848
+repolist: 23,213</pre></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">4.2.3. パッケージ情報の表示</h3></div></div></div><a id="idm126284752" class="indexterm"></a><a id="idp1572560" class="indexterm"></a><div class="para">
+ 複数のパッケージに関する情報を表示するには（ここでもグロブ表現が有効です）、以下のコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">info</code> <em class="replaceable"><code>package_name</code></em>…</pre><div class="para">
+ たとえば、 <span class="package">abrt</span> パッケージに関する情報を表示するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum info abrt</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+Name : abrt
+Arch : x86_64
+Version : 2.0.1
+Release : 2.fc15
+Size : 806 k
+Repo : installed
+From repo : fedora
+Summary : Automatic bug detection and reporting tool
+URL : https://fedorahosted.org/abrt/
+License : GPLv2+
+Description : abrt is a tool to help users to detect defects in applications and
+ : to create a bug report with all informations needed by maintainer
+ : to fix it. It uses plugin system to extend its functionality.</pre><a id="idm124962224" class="indexterm"></a><a id="idm85674880" class="indexterm"></a><div class="para">
+ <code class="command">yum info <em class="replaceable"><code>package_name</code></em></code> コマンドは <code class="command">rpm -q --info <em class="replaceable"><code>package_name</code></em></code> コマンドに似ていますが、RPM パッケージが見つけられた Yum リポジトリの ID を追加情報として提供します。（出力において <code class="computeroutput">From repo:</code> 行を探してください）。
+ </div><div class="para">
+ 以下のコマンドを使用することにより、代替物とパッケージに関する有用な情報を Yum データベースに問い合わせすることもできます:
+ </div><pre class="synopsis"><code class="command">yumdb</code> <code class="option">info</code> <em class="replaceable"><code>package_name</code></em></pre><div class="para">
+ このコマンドは、パッケージのチェックサム（および、それを生成するために使用された SHA-256 のようなアルゴリズム）、パッケージをインストールするために呼び出されたコマンドラインに与えられたコマンド（もしあれば）、パッケージがシステムにインストールされた理由（ここで <code class="computeroutput">user</code> はユーザーによりインストールされたことを意味します、<code class="computeroutput">dep</code> は依存性のためもたらされたことを意味します。）を含め、パッケージに関するさらなる情報を提供します。たとえば、<span class="package">yum</span> パッケージに関するさらなる情報を表示するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yumdb info yum</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+yum-3.2.29-4.fc15.noarch
+ checksum_data = 249f21fb43c41381c8c9b0cd98d2ea5fa0aa165e81ed2009cfda74c05af67246
+ checksum_type = sha256
+ from_repo = fedora
+ from_repo_revision = 1304429533
+ from_repo_timestamp = 1304442346
+ installed_by = 0
+ reason = user
+ releasever = $releasever</pre><div class="para">
+ <code class="command">yumdb</code> コマンドの詳細は <span class="bold bold"><strong>yumdb</strong></span>(8) マニュアルページを参照してください。
+ </div></div><div class="section" id="sec-Installing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.4. パッケージのインストール</h3></div></div></div><a id="idm113474896" class="indexterm"></a><a id="idm113473488" class="indexterm"></a><div class="para">
+ Yum は単一のパッケージ、複数のパッケージ、および選択したパッケージのグループをインストールできます。
+ </div><h4 id="bh-Installing_Individual_packages">各パッケージのインストール</h4><div class="para">
+ 単一のパッケージおよびインストールされていない依存パッケージすべてをインストールするには、以下の形式でコマンドを入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">install</code> <em class="replaceable"><code>package_name</code></em></pre><div class="para">
+ 引数として名前を追加することにより、同時に複数のパッケージをインストールすることもできます:
+ </div><pre class="synopsis"><code class="command">yum</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">
+ AMD64 や Intel64 マシンのような <em class="firstterm">multilib</em> システムにおいてパッケージをインストールしているならば、パッケージ名に <em class="replaceable"><code>.arch</code></em> を追加することにより、（有効なリポジトリーにおいて利用可能ならば）パッケージのアーキテクチャーを指定できます。たとえば、<code class="systemitem">i586</code> の <span class="package">sqlite2</span> をインストールするには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum install sqlite2.i586</code></pre><div class="para">
+ 同じような名前の複数のパッケージを素早くインストールするためにグロブ表現を使用することができます:
+ </div><pre class="screen">~]# <code class="command">yum install audacious-plugins-\*</code></pre><div class="para">
+ パッケージ名とグロブ表現に加えて、ファイル名を <code class="command">yum install</code> に提供することもできます。インストールしたいバイナリの名前がわかっているならば、<code class="command">yum install</code> にパス名を与えることもできます:
+ </div><pre class="screen">~]# <code class="command">yum install /usr/sbin/named</code></pre><div class="para">
+ そして、<code class="command">yum</code> はそのパッケージ一覧を検索して、<code class="filename">/usr/sbin/named</code> を探して、もしあればインストールしたいかどうかを確認します。
+ </div><div class="note" id="note-Finding_which_package_owns_a_file"><div class="admonition_header"><h2>ファイルを所有するパッケージの検索</h2></div><div class="admonition"><div class="para">
+ <code class="filename">named</code> バイナリを含むパッケージをインストールしたいと思っているが、<code class="filename">bin</code> または <code class="filename">sbin</code> ディレクトリにインストールされるファイルがわからないならば、<code class="command">yum provides</code> コマンドをグロブ表現を用いて使用します:
+ </div><pre class="screen">~]# <code class="command">yum provides "*bin/named"</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+32:bind-9.8.0-3.P1.fc15.i686 : The Berkeley Internet Name Domain (BIND) DNS
+ : (Domain Name System) server
+Repo : fedora
+Matched from:
+Filename : /usr/sbin/named</pre><div class="para">
+ <code class="command">yum provides "*/<em class="replaceable"><code>file_name</code></em>"</code> は、<em class="replaceable"><code>file_name</code></em> を含むパッケージを探すための一般的かつ有用なテクニックです。
+ </div></div></div><h4 id="bh-Installing_a_Package_Group">パッケージグループのインストール</h4><a id="idm103972144" class="indexterm"></a><a id="idm122209200" class="indexterm"></a><div class="para">
+ パッケージグループはパッケージと似ています: それ自体は有用ではありませんが、あるものをインストールすることにより、共通の目的を取り扱っている依存したパッケージのグループを取ってきます。パッケージグループは名前と <em class="firstterm">groupid</em> を持ちます。<code class="command">yum grouplist -v</code> コマンドは、すべてのパッケージグループの名前と、それに続けて括弧内にグループ ID を一覧表示します。グループ ID は必ず、以下の例にある <code class="literal">kde-desktop</code> のように、括弧の最後の組にあります:
+ </div><pre class="screen">~]# <code class="command">yum -v grouplist kde\*</code>
+Not loading "blacklist" plugin, as it is disabled
+Loading "langpacks" plugin
+Loading "presto" plugin
+Loading "refresh-packagekit" plugin
+Not loading "whiteout" plugin, as it is disabled
+Adding en_US to language list
+Config time: 0.900
+Yum Version: 3.2.29
+Setting up Group Process
+rpmdb time: 0.002
+group time: 0.995
+Available Groups:
+ KDE Software Compilation (kde-desktop)
+ KDE Software Development (kde-software-development)
+Done</pre><div class="para">
+ 完全なグループ名を（グループ ID 部分なしで） <code class="command">groupinstall</code> に渡すことによりパッケージのグループをインストールできます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">groupinstall</code> <em class="replaceable"><code>group_name</code></em></pre><div class="para">
+ groupidを使用してインストールすることもできます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">groupinstall</code> <em class="replaceable"><code>groupid</code></em></pre><div class="para">
+ <span class="keysym">@</span>-記号（<code class="command">yum</code> に <code class="command">groupinstall</code> を実行したいことを伝えます）を前につけると、 <code class="command">install</code> コマンドにグループ ID を渡すこともできます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">install</code> @<em class="replaceable"><code>group</code></em></pre><div class="para">
+ たとえば、以下は代わりになりますが、<code class="literal">KDE Desktop</code> グループをインストールする同等の方法です:
+ </div><pre class="screen">~]# <code class="command">yum groupinstall "KDE Desktop"</code>
+~]# <code class="command">yum groupinstall kde-desktop</code>
+~]# <code class="command">yum install @kde-desktop</code></pre></div><div class="section" id="sec-Removing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.5. パッケージの削除</h3></div></div></div><a id="idm134242944" class="indexterm"></a><a id="idm134241536" class="indexterm"></a><div class="para">
+ パッケージのインストールと同様に、Yumは個別のパッケージとパッケージのグループをアンインストール (<span class="application"><strong>RPM</strong></span> と Yum の言葉においては削除) することができます。
+ </div><h4 id="bh-Removing_Individual_Packages">個別のパッケージの削除</h4><a id="idm96645872" class="indexterm"></a><a id="idm88939824" class="indexterm"></a><div class="para">
+ 特定のパッケージおよびそれに依存するあらゆるパッケージをアンインストールするには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">remove</code> <em class="replaceable"><code>package_name</code></em>…</pre><div class="para">
+ 複数のパッケージをインストールするときのように、複数のパッケージ名をコマンドに追加することにより同時に削除できます。たとえば、<span class="package">totem</span>, <span class="package">rhythmbox</span>, および <span class="package">sound-juicer</span> を削除するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum remove totem rhythmbox sound-juicer</code></pre><div class="para">
+ <code class="command">install</code> 同様、<code class="command">remove</code> もこれらの引数をとることができます:
+ </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></ul></div><div class="warning" id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It"><div class="admonition_header"><h2>他のパッケージに依存するときのパッケージの削除</h2></div><div class="admonition"><div class="para">
+ Yum はあるパッケージに依存しているパッケージを削除せずにそれを削除することはできません。この種の操作は <span class="application"><strong>RPM</strong></span> によってのみ実行できますが、推奨されません。そして、潜在的にシステムを機能しない状態にする可能性がありまる、またはアプリケーションを不正動作かつ/またはクラッシュさせる可能性があります。さらなる情報は <span class="application"><strong>RPM</strong></span> の章にある<a class="xref" href="#s2-rpm-uninstalling">「アンインストール」</a>を参照してください。
+ </div></div></div><h4 id="bh-Removing_a_Package_Group">パッケージ グループの削除</h4><div class="para">
+ <code class="command">install</code> 構文を用いて構文一致を使用してパッケージグループを削除できます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">groupremove</code> <em class="replaceable"><code>group</code></em></pre><pre class="synopsis"><code class="command">yum</code> <code class="option">remove</code> @<em class="replaceable"><code>group</code></em></pre><div class="para">
+ 以下はそれぞれ異なりますが、<code class="literal">KDE Desktop</code> グループを削除する同等の方法です:
+ </div><pre class="screen">~]# <code class="command">yum groupremove "KDE Desktop"</code>
+~]# <code class="command">yum groupremove kde-desktop</code>
+~]# <code class="command">yum remove @kde-desktop</code></pre><div class="important" id="important-Package_Group_Removal"><div class="admonition_header"><h2>インテリジェントなパッケージグループの削除</h2></div><div class="admonition"><a id="idm120921712" class="indexterm"></a><a id="idm120920304" class="indexterm"></a><div class="para">
+ <span class="application"><strong>yum</strong></span> にパッケージグループを削除するよう指示するとき、それらのパッケージが他のパッケージグループのメンバーであったり、他のインストールされているパッケージに依存したりしていても、そのグループにあるすべてのパッケージが削除されます。しかしながら、<code class="option">groupremove_leaf_only=1</code> ディレクティブを <code class="filename">/etc/yum.conf</code> 設定ファイルの <code class="literal">[main]</code> セクションに追加することにより、あらゆる他のパッケージやグループに必要とされないパッケージのみを削除するよう <code class="command">yum</code> に指示することもできます。このディレクティブの詳細は<a class="xref" href="#sec-Setting_main_Options">「[main] オプションの設定」</a>を参照してください。
+ </div></div></div></div><div class="section" id="sec-Yum-Transaction_History"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.6. 処理とトランザクションの履歴</h3></div></div></div><div class="para">
+ <code class="command">yum history</code> コマンドにより、ユーザーが時系列の Yum トランザクション、それらが発生した日時、影響されたパッケージの数、トランザクションが成功したか中断されたかどうか、およびトランザクション中に RPM データベースが変更されたかどうか、に関する情報を確認できます。加えて、このコマンドは特定のトランザクションを元に戻したり、再実行したりするために使用できます。
+ </div><h4 id="bh-Yum-Transaction_History-Listing">トランザクションの一覧</h4><div class="para">
+ 最新のトランザクション20個の一覧を表示するには、<code class="systemitem">root</code>として、引数なしで <code class="command">yum history</code> を実行します、またはシェルプロンプトにおいて以下のように入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">list</code></pre><div class="para">
+ すべてのトランザクションを表示するには、<code class="literal">all</code> キーワードを追加します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">list</code> <code class="option">all</code></pre><div class="para">
+ 与えられた範囲にあるトランザクションのみを表示するには、以下の形式でコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">yum</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">
+ 特定のパッケージに関するトランザクションのみを一覧表示することもできます。そうするには、パッケージ名またはグロブ表現とともにコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">list</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、以下のように最初の5トランザクションの一覧が表示されます:
+ </div><pre class="screen">~]# <code class="command">yum history list 1..5</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+ID | Login user | Date and time | Action(s) | Altered
+-------------------------------------------------------------------------------
+ 5 | Jaromir ... <jhradilek> | 2011-07-29 15:33 | Install | 1
+ 4 | Jaromir ... <jhradilek> | 2011-07-21 15:10 | Install | 1
+ 3 | Jaromir ... <jhradilek> | 2011-07-16 15:27 | I, U | 73
+ 2 | System <unset> | 2011-07-16 15:19 | Update | 1
+ 1 | System <unset> | 2011-07-16 14:38 | Install | 1106
+history list</pre><div class="para">
+ すべての形式の <code class="command">yum history list</code> コマンドは、以下の列から構成される各行をタブ区切りを生成します:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">ID</code> — 特定のトランザクションを識別する整数値です。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Login user</code> — トランザクションを初期化するために使用されたログインセッションのユーザー名です。この情報は一般的に<code class="computeroutput"><em class="replaceable"><code>Full Name</code></em> (完全名) <<em class="replaceable"><code>username</code></em> (ユーザー名) ></code> 形式で表現されます。（自動的なシステム更新のように）ユーザーにより発行されていないトランザクションは、<code class="computeroutput">System <unset></code> が代わりに使用されます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Date and time</code> — トランザクションが発行された日付と時刻です。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Action(s)</code> — <a class="xref" href="#tabl-Yum-Transaction_History-Actions">表4.1「Action(s) フィールドの取り得る値」</a>に説明されているように、トランザクション中に実行されたアクションの一覧です。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Altered</code> — トランザクションにより影響を受けるパッケージの数です。<a class="xref" href="#tabl-Yum-Transaction_History-Altered">表4.2「Altered フィールドの利用可能な値」</a>に記載されているように追加の情報を続けることができます。
+ </div></li></ul></div><div class="table" id="tabl-Yum-Transaction_History-Actions"><h6>表4.1 Action(s) フィールドの取り得る値</h6><div class="table-contents"><table summary="Action(s) フィールドの取り得る値" border="1"><colgroup><col width="20%" class="Action" /><col width="15%" class="Abbreviation" /><col width="65%" class="Description" /></colgroup><thead><tr><th class="">
+ アクション
+ </th><th class="">
+ 略号
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="literal">Downgrade</code>
+ </td><td class="">
+ <code class="literal">D</code>
+ </td><td class="">
+ 少なくとも1つのパッケージが古いバージョンにダウングレードされました。
+ </td></tr><tr><td class="">
+ <code class="literal">Erase</code>
+ </td><td class="">
+ <code class="literal">E</code>
+ </td><td class="">
+ 少なくとも 1 つのパッケージが削除されました。
+ </td></tr><tr><td class="">
+ <code class="literal">インストール</code>
+ </td><td class="">
+ <code class="literal">I</code>
+ </td><td class="">
+ 少なくとも 1 つの新規パッケージがインストールされました。
+ </td></tr><tr><td class="">
+ <code class="literal">Obsoleting</code>
+ </td><td class="">
+ <code class="literal">O</code>
+ </td><td class="">
+ 少なくとも一つのパッケージに推奨されないという印がついています。
+ </td></tr><tr><td class="">
+ <code class="literal">再インストール</code>
+ </td><td class="">
+ <code class="literal">R</code>
+ </td><td class="">
+ 少なくとも 1 つのパッケージを再インストールしました。
+ </td></tr><tr><td class="">
+ <code class="literal">アップグレード</code>
+ </td><td class="">
+ <code class="literal">U</code>
+ </td><td class="">
+ 少なくとも 1 つのパッケージを新しいバージョンに更新しました。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table" id="tabl-Yum-Transaction_History-Altered"><h6>表4.2 Altered フィールドの利用可能な値</h6><div class="table-contents"><table summary="Altered フィールドの利用可能な値" border="1"><colgroup><col width="20%" class="Symbol" /><col width="80%" class="Description" /></colgroup><thead><tr><th class="">
+ シンボル
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="literal"><</code>
+ </td><td class="">
+ トランザクションの終了前で、データベース <code class="filename">rpmdb</code> が Yum 以外で変更されました。
+ </td></tr><tr><td class="">
+ <code class="literal">></code>
+ </td><td class="">
+ トランザクションの終了後、<code class="filename">rpmdb</code> データベースが Yum 以外で更新されました
+ </td></tr><tr><td class="">
+ <code class="literal">*</code>
+ </td><td class="">
+ トランザクションの終了に失敗しました。
+ </td></tr><tr><td class="">
+ <code class="literal">#</code>
+ </td><td class="">
+ トランザクションの実行に成功しましたが、<code class="command">yum</code> は 0 以外の終了コードを返しました。
+ </td></tr><tr><td class="">
+ <code class="literal">E</code>
+ </td><td class="">
+ トランザクションの終了に成功しましたが、エラーか警告が表示されました。
+ </td></tr><tr><td class="">
+ <code class="literal">P</code>
+ </td><td class="">
+ トランザクションが正常に終了しましたが、問題はすでに<code class="filename">rpmdb</code> データベースに存在しました。
+ </td></tr><tr><td class="">
+ <code class="literal">s</code>
+ </td><td class="">
+ トランザクションが正常に終了しました。ただし、<code class="option">--skip-broken</code> コマンドラインオプションが使用され、特定のパッケージがスキップされました。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Yum は過去のトランザクションすべての概要を表示することもできます。そうするには、<code class="systemitem">root</code> として以下の形式でコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">summary</code></pre><div class="para">
+ 指定した範囲のトランザクションのみを表示するには、次のように入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">summary</code> <em class="replaceable"><code>start_id</code></em>..<em class="replaceable"><code>end_id</code></em></pre><div class="para">
+ <code class="command">yum history list</code> コマンドと同様に、パッケージ名またはグロブ表現を与えることにより特定のパッケージに関するトランザクションの概要を表示することもできます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">summary</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、上に表示されたトランザクション履歴の概要は以下にあるように見えます:
+ </div><pre class="screen">~]# <code class="command">yum history summary 1..5</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Login user | Time | Action(s) | Altered
+-------------------------------------------------------------------------------
+Jaromir ... <jhradilek> | Last day | Install | 1
+Jaromir ... <jhradilek> | Last week | Install | 1
+Jaromir ... <jhradilek> | Last 2 weeks | I, U | 73
+System <unset> | Last 2 weeks | I, U | 1107
+history summary</pre><div class="para">
+ すべての形式の <code class="command">yum history summary</code> コマンドは <code class="command">yum history list</code> の出力と似ているものを単純化されたタブ区切りの出力を生成します。
+ </div><div class="para">
+ 上で示したように、<code class="command">yum history list</code> と <code class="command">yum history summary</code> はどちらもトランザクション指向です。与えられたパッケージに関連するトランザクションのみを表示できますが、パッケージのバージョンのような重要な詳細が不足しています。パッケージの観点からトランザクションを一覧表示するには、以下のコマンドを <code class="systemitem">root</code> として実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">package-list</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、<span class="package">subscription-manager</span> と関連するパッケージの履歴を追跡するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum history package-list subscription-manager\*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+ID | Action(s) | Package
+-------------------------------------------------------------------------------
+ 3 | Updated | subscription-manager-0.95.11-1.el6.x86_64
+ 3 | Update | 0.95.17-1.el6_1.x86_64
+ 3 | Updated | subscription-manager-firstboot-0.95.11-1.el6.x86_64
+ 3 | Update | 0.95.17-1.el6_1.x86_64
+ 3 | Updated | subscription-manager-gnome-0.95.11-1.el6.x86_64
+ 3 | Update | 0.95.17-1.el6_1.x86_64
+ 1 | Install | subscription-manager-0.95.11-1.el6.x86_64
+ 1 | Install | subscription-manager-firstboot-0.95.11-1.el6.x86_64
+ 1 | Install | subscription-manager-gnome-0.95.11-1.el6.x86_64
+history package-list</pre><div class="para">
+ この例では、3つのパッケージがシステムの初期インストール中にインストールされました: <span class="package">subscription-manager</span>, <span class="package">subscription-manager-firstboot</span>, および <span class="package">subscription-manager-gnome</span>。3回目のトランザクションにおいて、すべてのパッケージがバージョン 0.95.11 からバージョン 0.95.17 に更新されました。
+ </div><h4 id="bh-Yum-Transaction_History-Examining">トランザクションの検証</h4><div class="para">
+ 単一のトランザクションの概要を表示するには、<code class="systemitem">root</code> として <code class="command">yum history summary</code> コマンドを以下の形式で使用します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">summary</code> <em class="replaceable"><code>id</code></em></pre><div class="para">
+ 特定のトランザクションを詳細に確認するには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">info</code> <em class="replaceable"><code>id</code></em>…</pre><div class="para">
+ <em class="replaceable"><code>id</code></em> 引数はオプションです。省略したとき、<code class="command">yum</code> は自動的に最後のトランザクションを使用します。複数のトランザクションを指定するときに、範囲を使用することもできることに注意してください:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">info</code> <em class="replaceable"><code>start_id</code></em>..<em class="replaceable"><code>end_id</code></em></pre><div class="para">
+ 以下は、2つのトランザクションのサンプル出力です。それぞれ新規パッケージを1つインストールしています:
+ </div><pre class="screen">~]# <code class="command">yum history info 4..5</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Transaction ID : 4..5
+Begin time : Thu Jul 21 15:10:46 2011
+Begin rpmdb : 1107:0c67c32219c199f92ed8da7572b4c6df64eacd3a
+End time : 15:33:15 2011 (22 minutes)
+End rpmdb : 1109:1171025bd9b6b5f8db30d063598f590f1c1f3242
+User : Jaromir Hradilek <jhradilek>
+Return-Code : Success
+Command Line : install screen
+Command Line : install yum-plugin-fs-snapshot
+Transaction performed with:
+ Installed rpm-4.8.0-16.el6.x86_64
+ Installed yum-3.2.29-17.el6.noarch
+ Installed yum-metadata-parser-1.1.2-16.el6.x86_64
+Packages Altered:
+ Install screen-4.0.3-16.el6.x86_64
+ Install yum-plugin-fs-snapshot-1.1.30-6.el6.noarch
+history info</pre><div class="para">
+ トランザクションを実行したときに使用された設定オプションや、どのリポジトリからパッケージがインストールされたか、特定のパッケージがなぜインストールされたか、などのような追加の情報を表示することもできます。特定のトランザクションに対してどの追加の情報が利用可能であるかを決めるには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">addon-info</code> <em class="replaceable"><code>id</code></em></pre><div class="para">
+ <code class="command">yum history info</code> と同様、<em class="replaceable"><code>id</code></em> を与えないとき、<code class="command">yum</code> は自動的に最後のトランザクションを使用します。最後のトランザクションを参照する別の方法は <code class="literal">last</code> キーワードを使用することです:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">addon-info</code> <code class="option">last</code></pre><div class="para">
+ たとえば、前の例にある最初のトランザクションに対して、<code class="command">yum history addon-info</code> コマンドは以下のように出力します:
+ </div><pre class="screen">~]# <code class="command">yum history addon-info 4</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Transaction ID: 4
+Available additional history information:
+ config-main
+ config-repos
+ saved_tx
+
+history addon-info</pre><div class="para">
+ この例では、3種類の情報が利用可能です:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">config-main</code> — トランザクション中に使用される Yum 全体オプションです。全体オプションを変更する方法については<a class="xref" href="#sec-Setting_main_Options">「[main] オプションの設定」</a>を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">config-repos</code> — 各 Yum リポジトリーに対するオプションです。各リポジトリーに対するオプションを変更する方法については<a class="xref" href="#sec-Setting_repository_Options">「[repository] オプションの設定」</a>を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">saved_tx</code> — 他のマシンにおいてトランザクションを繰り返すために <code class="command">yum load-transaction</code> コマンドにより使用できるデータです（以下、参照）。
+ </div></li></ul></div><div class="para">
+ 選択した形式の追加の情報を表示するには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">addon-info</code> <em class="replaceable"><code>id</code></em> <em class="replaceable"><code>information</code></em></pre><h4 id="bh-Yum-Transaction_History-Reverting">トランザクションの復帰および繰り返し</h4><div class="para">
+ トランザクション履歴の確認のほか、<code class="command">yum history</code> コマンドは選択したトランザクションの復帰および繰り返しをする手段を提供します。トランザクションを復帰するには、シェルプロンプトにおいて以下のコマンドを <code class="systemitem">root</code> として入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">undo</code> <em class="replaceable"><code>id</code></em></pre><div class="para">
+ 特定のトランザクションを繰り返すには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">redo</code> <em class="replaceable"><code>id</code></em></pre><div class="para">
+ どちらのコマンドも、最後に実行したトランザクションを取り消すまたは繰り返すために、<code class="literal">last</code> キーワードを受け付けます。
+ </div><div class="para">
+ <code class="command">yum history undo</code> と <code class="command">yum history redo</code> コマンドはどちらも単にトランザクション中に実行された手順を復帰または繰り返すだけであることに注意してください。トランザクションが新しいパッケージをインストールしているならば、<code class="command">yum history undo</code> コマンドはそれをアンインストールします。逆もまた同様です。可能ならば、このコマンドはすべての更新したパッケージをそれらの前のバージョンにダウングレードしようとしますが、これらの古いパッケージはもはや利用可能ではないかもしれません。もしシステムを更新前の状態に復元できる必要があるならば、<a class="xref" href="#sec-Plugin_Descriptions">「プラグインの説明」</a>において説明されている <span class="application"><strong>fs-
snapshot</strong></span> プラグインの使用を検討してください。
+ </div><div class="para">
+ いくつかの同一システムを管理するとき、Yumはそのうちのどれか１つにおいてトランザクションを実行し、トランザクションの詳細をファイルに保存し、テスト後に同じトランザクションを残りのシステムにおいて同じように繰り返すこともできるようにします。トランザクションの詳細をファイルに保存するには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">-q</code> <code class="option">history</code> <code class="option">addon-info</code> <em class="replaceable"><code>id</code></em> <code class="option">saved_tx</code> > <code class="filename">file_name</code></pre><div class="para">
+ 一度このファイルを対象システムにコピーすると、<code class="systemitem">root</code> として以下のコマンドを使用することによりトランザクションを繰り返すことができます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">load-transaction</code> <em class="replaceable"><code>file_name</code></em></pre><div class="para">
+ しかしながら、ファイルに保存されている <code class="literal">rpmdb</code> バージョンは対象システムにおけるバージョンと同一でなければいけません。<code class="command">yum version nogroups</code> コマンドを使用することにより <code class="literal">rpmdb</code> のバージョンを確認できます。
+ </div><h4 id="bh-Yum-Transaction_History-New">新規トランザクション履歴の開始</h4><div class="para">
+ Yum はトランザクション履歴を単独の SQLite データベースファイルに保存します。新規トランザクション履歴を開始するには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">new</code></pre><div class="para">
+ これにより、新しい空のデータベースファイルが <code class="filename">/var/lib/yum/history/</code> ディレクトリに作成されます。古いトランザクション履歴は保持されますが、新しいデータベースがディレクトリに存在する限りアクセスできません。
+ </div></div></div><div class="section" id="sec-Configuring_Yum_and_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Yum と Yum リポジトリーの設定</h2></div></div></div><a id="idm88774416" class="indexterm"></a><a id="idm88773008" class="indexterm"></a><div class="para">
+ <code class="command">yum</code> と関連ユーティリティの設定ファイルは <code class="filename">/etc/yum.conf</code> にあります。このファイルは、必須の <code class="literal">[main]</code> セクション（全体に影響を持つ Yum オプションを設定できます）を含みます。また1つ以上の <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクション（リポジトリ固有のオプションを設定できます）を含むかもしれません。しかしながら、ベストプラクティスは <code class="filename">/etc/yum.repos.d/</code> ディレクトリに新規または既存の <code class="filename">.repo</code> ファイルにおいてそれぞれのリポジトリを定義することです。<code class="filename">/etc/yum.conf</code> ファイルの <code class="literal">[main]</code> セクションにおいて定義した値は、それぞれの <code class="liter
al">[<em class="replaceable"><code>repository</code></em>]</code> セクションにおいて設定した値をオーバーライドするかもしれません。
+ </div><div class="para">
+ このセクションは以下の方法を説明します:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/yum.conf</code> 設定ファイルの <code class="literal">[main]</code> セクションを編集することにより、Yum の全体オプションを設定します;
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/yum.conf</code> および <code class="filename">/etc/yum.repos.d/</code> ディレクトリの <code class="filename">.repo</code> にある <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションを編集することにより各リポジトリに対するオプションを設定します;
+ </div></li><li class="listitem"><div class="para">
+ バージョンとアーキテクチャーを動的に正しく取り扱えるように <code class="filename">/etc/yum.conf</code> および <code class="filename">/etc/yum.repos.d/</code> ディレクトリにあるファイルに Yum 変数を使用します;
+ </div></li><li class="listitem"><div class="para">
+ コマンドラインで Yum リポジトリの追加、有効化および無効化をします、また、
+ </div></li><li class="listitem"><div class="para">
+ 独自 Yum リポジトリを導入します。
+ </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">4.3.1. [main] オプションの設定</h3></div></div></div><a id="idm120553952" class="indexterm"></a><div class="para">
+ <code class="filename">/etc/yum.conf</code> 設定ファイルはちょうど一つの <code class="literal">[main]</code> セクションを含みます。このセクションにあるキー・バリューの組のいくつかは、<code class="command">yum</code> がどのように動作するかに影響します。その他は Yum がリポジトリをどのように取り扱うかに影響します。<code class="filename">/etc/yum.conf</code> の先頭にある <code class="literal">[main]</code> セクションの下に数多くの追加のオプションを追加できます。
+ </div><div class="para">
+ サンプル <code class="filename">/etc/yum.conf</code> 設定ファイルはこのようなものです:
+ </div><pre class="programlisting">[main]
+cachedir=/var/cache/yum/$basearch/$releasever
+keepcache=0
+debuglevel=2
+logfile=/var/log/yum.log
+exactarch=1
+obsoletes=1
+gpgcheck=1
+plugins=1
+installonly_limit=3
+
+<em class="lineannotation"><span class="lineannotation">[コメントの省略]</span></em>
+
+# PUT YOUR REPOS HERE OR IN separate files named file.repo
+# in /etc/yum.repos.d</pre><div class="para">
+ 以下は <code class="literal">[main]</code> セクションにおいて最も一般的に使用されるオプションです:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">assumeyes</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — <code class="command">yum</code> はクリティカルなアクションの実行について確認のプロンプトを表示します。これがデフォルトです。
+ </div><div class="para">
+ <code class="literal">1</code> — クリティカルな <code class="command">yum</code> アクションについて確認のプロンプトを表示します。もし <code class="option">assumeyes=1</code> が設定されていると、<code class="command">yum</code> はコマンドラインにおいて <code class="option">-y</code> オプションをつけたときと同じ方法の動作をします。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">cachedir</code>=<em class="replaceable"><code>directory</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>directory</code></em> は、Yum がキャッシュとデータベースファイルを保存するディレクトリの絶対パスです。Yum のキャッシュディレクトリはデフォルトで <code class="filename">/var/cache/yum/$basearch/$releasever</code> です。
+ </div><div class="para">
+ <code class="varname">$basearch</code> および <code class="varname">$releasever</code> Yum 変数の記述については<a class="xref" href="#sec-Using_Yum_Variables">「Yum 変数の使い方」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">debuglevel</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は <code class="literal">1</code> から <code class="literal">10</code> の間の整数です。<code class="option">debuglevel</code> 値により大きな値を設定することにより、<code class="command">yum</code> がより詳細なデバッグ情報を表示します。<code class="option">debuglevel=0</code> はデバッグ出力を無効にします。<code class="option">debuglevel=2</code> がデフォルトです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">exactarch</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — パッケージを更新するときに、厳密なアーキテクチャーを考慮しません。
+ </div><div class="para">
+ <code class="literal">1</code> — パッケージを更新するときに、厳密なアーキテクチャーを考慮します。この設定をすると、<code class="command">yum</code> は、システムにすでにインストールされている i386 パッケージを更新するために、i686 パッケージをインストールすることはしません。これがデフォルトです。
+ </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">
+ このオプションはインストール/更新中にキーワードによりパッケージを除外できます。スペース区切りでパッケージの一覧をクオートすることにより、除外する複数のパッケージを一覧にできます。ワイルドカード (たとえば、<code class="literal">*</code> および <code class="literal">?</code>) を使用するシェルのグロブ表現が許可されます。
+ </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">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — ローカルパッケージのインストールを含め、すべてのリポジトリーにおいてパッケージの GPG 署名検証を無効にします。
+ </div><div class="para">
+ <code class="literal">1</code> — ローカルパッケージのインストールを含め、すべてのリポジトリーにおいてすべてのパッケージの GPG 署名検証を有効にします。<code class="option">gpgcheck=1</code> がデフォルトで、すべてのパッケージの署名がチェックされます。
+ </div><div class="para">
+ このオプションが <code class="filename">/etc/yum.conf</code> の <code class="literal">[main]</code> セクションにおいて設定されていると、すべてのリポジトリに対して GPG チェックのルールを設定します。しかしながら、代わりに各リポジトリに対して <code class="option">gpgcheck=<em class="replaceable"><code>value</code></em></code> を設定することもできます。つまり、あるリポジトリにおいて GPG チェックを有効にしながら、他において無効にすることができます。もし <code class="filename">/etc/yum.conf</code> にあるならば、各リポジトリに対して対応する <code class="filename">.repo</code> ファイルにおいて <code class="option">gpgcheck=<em class="replaceable"><code>value</code></em></code> を設定することによりデフォルトをオーバーライドします。
+ </div><div class="para">
+ GPG 署名チェックに関する詳細は<a class="xref" href="#s1-check-rpm-sig">「パッケージの署名を確認する」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">groupremove_leaf_only</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — <code class="command">yum</code> はパッケージグループを削除するとき各パッケージの依存物を確認<span class="emphasis"><em>しません</em></span>。この設定を用いると、<code class="command">yum</code> は、他のパッケージやグループにより必要とされるパッケージかどうかによらず、パッケージグループにあるすべてのパッケージを削除します。<code class="option">groupremove_leaf_only=0</code> はデフォルトです。
+ </div><div class="para">
+ <code class="literal">1</code> — <code class="command">yum</code> は、パッケージグループを削除するとき各パッケージの依存性を確認して、あらゆる他のパッケージやグループにより必要とされないパッケージのみを削除します。
+ </div><div class="para">
+ パッケージの削除に関する詳細は<a class="xref" href="#important-Package_Group_Removal">インテリジェントなパッケージグループの削除</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">
+ ここに <code class="command">yum</code> が<span class="emphasis"><em>インストール</em></span>できるが、<span class="emphasis"><em>更新</em></span>しないパッケージの一覧を空白区切りで提供できます。デフォルトでインストールのみとなっているパッケージの一覧は <span class="bold bold"><strong>yum.conf</strong></span>(5) マニュアルページを参照してください。
+ </div><div class="para">
+ <code class="option">installonlypkgs</code> ディレクティブを <code class="filename">/etc/yum.conf</code> に追加したければ、<span class="bold bold"><strong>yum.conf</strong></span>(5) の <code class="literal">installonlypkgs</code> の中に一覧化されているものすべてを含めて、インストールのみにする<span class="emphasis"><em>すべて</em></span>のパッケージを一覧にすることを確認します。とくに、kernel パッケージは必ず <code class="option">installonlypkgs</code> (デフォルトであります) に一覧化すべきです。また、デフォルトのカーネルが起動に失敗した場合に、バックアップのカーネルが必ず利用可能であるよう、\n<code class="option">installonly_limit</code> は必ず <code class="literal">2</code> よりも大きな値に設定すべきです。
+ </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">
+ …ここで <em class="replaceable"><code>value</code></em> は <code class="option">installonlypkgs</code> ディレクティブに一覧されている単一パッケージすべてに対して同時にインストールできるバージョンの最大数を表す整数です。
+ </div><div class="para">
+ <code class="option">installonlypkgs</code> ディレクティブのデフォルトはそれぞれの異なる kernel パッケージを含みます。そのため、<code class="option">installonly_limit</code> の値を変更することにより、あらゆる単一の kernel パッケージについてインストールされたバージョンの最大数にも影響します。<code class="filename">/etc/yum.conf</code> に記載されたデフォルト値は <code class="option">installonly_limit=3</code> です。そして、この値を減らすこと、特に <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">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — 正常にインストールされた後、ヘッダーとパッケージのキャッシュを保持しません。これがデフォルトです。
+ </div><div class="para">
+ <code class="literal">1</code> — 正常にインストールした後、キャッシュを保持します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">logfile</code>=<em class="replaceable"><code>file_name</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>file_name</code></em> は <code class="command">yum</code> がログ出力を書き込むファイルの絶対パスです。デフォルトで <code class="command">yum</code> は <code class="filename">/var/log/yum.log</code> にログをとります。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">multilib_policy</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">best</code> — このシステムに最適なアーキテクチャーをインストールします。たとえば、AMD64 システムにおいて <code class="option">multilib_policy=best</code> を設定することにより、<code class="command">yum</code> はすべてのパッケージの 64 ビットバージョンをインストールします。
+ </div><div class="para">
+ <code class="literal">all</code> — 常にすべてのパッケージについてすべての利用可能なアーキテクチャーをインストールします。たとえば、AMD64 システムにおいて <code class="option">multilib_policy</code> を <code class="literal">all</code> に設定すると、<code class="command">yum</code> は、i586 と AMD64 の両方が利用可能ならば、パッケージの両方のバージョンをインストールします。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">obsoletes</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — 更新を実行するとき <code class="command">yum</code> の推奨されない処理ロジックを無効にします。
+ </div><div class="para">
+ <code class="literal">1</code> — 更新を実行するときに <code class="command">yum</code> の推奨されない処理ロジックを有効にします。あるパッケージが他のパッケージを<em class="firstterm">推奨しない</em>よう SPEC ファイルにおいて宣言するとき、後者のパッケージは前者のパッケージがインストールされるときに前者のパッケージにより置き換えられます。たとえば、パッケージが名前変更されるとき、推奨しないことが宣言されます。<code class="option">obsoletes=1</code> がデフォルトです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">plugins</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — Yum プラグイン全体を無効にします。
+ </div><div class="important" id="important-Disabling_all_plugins_is_not_advised-main_options"><div class="admonition_header"><h2>すべてのプラグインを無効にすることは推奨されません</h2></div><div class="admonition"><div class="para">
+ あるプラグインは重要な <code class="command">Yum</code> サービスを提供するので、すべてのプラグインを無効にすることは推奨されません。プラグインを全体的に無効にすることは、便利なオプションとして提供され、一般的に <code class="command">Yum</code> に関する潜在的な問題を診断するときにのみ推奨されます。
+ </div></div></div><div class="para">
+ <code class="literal">1</code> — すべての Yum プラグインを有効にします。<code class="option">plugins=1</code> を用いても、プラグインの設定ファイルにおいて <code class="option">enabled=0</code> と設定されている特定の Yum プラグインを無効にすることもできます。
+ </div><div class="para">
+ さまざまな Yum プラグインの詳細は<a class="xref" href="#sec-Yum_Plugins">「Yum プラグイン」</a>を参照してください。プラグインの制御に関する詳細は<a class="xref" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">「Yum プラグインの無効化、有効化、設定」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">reposdir</code>=<em class="replaceable"><code>directory</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>directory</code></em> は <code class="filename">.repo</code> ファイルが置かれる場所の絶対パスです。すべての <code class="filename">.repo</code> ファイルはリポジトリの情報（<code class="filename">/etc/yum.conf</code> の <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションと似ています）を含みます。<code class="command">yum</code> はトランザクションのために使用するリポジトリのマスター一覧を作成するために、<code class="filename">.repo</code> ファイルと <code class="filename">/etc/yum.conf</code> ファイルの <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションからすべてのリポジトリの情報を収集します。<code class="literal">reposdir</code> が設定されていなければ、<code class="command">yum</code> はデフォル
トの <code class="filename">/etc/yum.repos.d/</code> ディレクトリを使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">retries</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は <code class="literal">0</code> 以上の整数です。この値は <code class="command">yum</code> がエラーを返す前にファイルの取得を試みる回数を設定します。これを <code class="literal">0</code> に設定することにより、<code class="command">yum</code> が無限に再試行します。デフォルト値は <code class="literal">10</code> です。
+ </div></dd></dl></div><div class="para">
+ 利用可能な <code class="literal">[main]</code> オプションの完全な一覧は、<span class="bold bold"><strong>yum.conf</strong></span>(5) マニュアルページの <code class="literal">[main] OPTIONS</code> セクションを参照してください。
+ </div></div><div class="section" id="sec-Setting_repository_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.2. [repository] オプションの設定</h3></div></div></div><a id="idm105641552" class="indexterm"></a><div class="para">
+ <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクション、ここで <em class="replaceable"><code>repository</code></em> は <code class="literal">my_personal_repo</code> のような一意なリポジトリ ID です（空白は許可されません）、は個々の Yum リポジトリを定義できます。
+ </div><div class="para">
+ 以下は <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションが受け取る形式のごく最低限の例です:
+ </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">
+ すべての <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションは以下のディレクティブを必ず含まなければいけません:
+ </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">
+ …ここで <em class="replaceable"><code>repository_name</code></em> は人間が読みやすいリポジトリの説明文です。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">baseurl</code>=<em class="replaceable"><code>repository_url</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>repository_url</code></em> はリポジトリの repodata ディレクトリが置かれているディレクトリへの URL です:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ リポジトリが HTTP 経由で利用可能ならば、次を使用します: <code class="literal">http://path/to/repo</code>
+ </div></li><li class="listitem"><div class="para">
+ リポジトリが FTP で利用可能ならば、次を使用します: <code class="literal">ftp://path/to/repo</code>
+ </div></li><li class="listitem"><div class="para">
+ リポジトリがマシンのローカルならば、次を使用します: <code class="literal">file:///path/to/local/repo</code>
+ </div></li><li class="listitem"><div class="para">
+ 特定のオンラインのリポジトリが HTTP ベーシック認証を必要とするならば、<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> のように URL の前にユーザー名とパスワードを指定できます。たとえば、http://www.example.com/repo/ にあるリポジトリが、ユーザー名 <span class="quote">「<span class="quote">user</span>」</span> とパスワード <span class="quote">「<span class="quote">password</span>」</span> を必要とするならば、 <code class="option">baseurl</code> リンクは <code class="option">http://<strong class="userinput"><code>user</code></strong>:<strong class="userinput"><code>password</code></strong>@www.example.com/repo/</code> のように指定できます。
+ </div></li></ul></div><div class="para">
+ この URL は通常次のような HTTP リンクです:
+ </div><pre class="programlisting">baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</pre><div class="para">
+ Yum は必ず URL にある <code class="varname">$releasever</code>, <code class="varname">$arch</code>, および <code class="varname">$basearch</code> 変数を展開します。Yum 変数の詳細は <a class="xref" href="#sec-Using_Yum_Variables">「Yum 変数の使い方」</a> を参照してください。
+ </div></dd></dl></div><div class="para">
+ 他の有用な <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> ディレクティブは以下です:
+ </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">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — 更新およびインストールを実行するとき派ケージソースとしてこのリポジトリを含めません。これは素早くリポジトリをオンオフする簡単な情報です。これは更新またはインストールのために有効にしたくないリポジトリから単一のパッケージを希望するときに有用です。
+ </div><div class="para">
+ <code class="literal">1</code> — このリポジトリをパッケージソースとして含めます。
+ </div><div class="para">
+ リポジトリを有効または無効にするには、<code class="option">--enablerepo=<em class="replaceable"><code>repo_name</code></em></code> or <code class="option">--disablerepo=<em class="replaceable"><code>repo_name</code></em></code> オプションを <code class="command">yum</code> に渡すことにより、または、<span class="application"><strong>PackageKit</strong></span> ユーティリティの<span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span> ウィンドウにより実行できます。
+ </div></dd></dl></div><div class="para">
+ さらに多くの <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> オプションが存在します。完全な一覧は <span class="bold bold"><strong>yum.conf</strong></span>(5) マニュアルページの <code class="literal">[repository] OPTIONS</code> セクションを参照してください。
+ </div></div><div class="section" id="sec-Using_Yum_Variables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.3. Yum 変数の使い方</h3></div></div></div><a id="idm129334752" class="indexterm"></a><div class="para">
+ <code class="command">yum</code> コマンドと Yum 設定ファイル（つまり、<code class="filename">/etc/yum.conf</code> および <code class="filename">/etc/yum.repos.d/</code> ディレクトリにあるすべての <code class="filename">.repo</code> ファイル）において以下の組み込み変数を使用および参照できます:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="varname">$releasever</code></span></dt><dd><div class="para">
+ Fedora のリリースバージョンを参照するためにこの変数を使用できます。Yum は <code class="filename">/etc/yum.conf</code> 設定ファイルの <code class="literal">distroverpkg=<em class="replaceable"><code>value</code></em></code> 行から <code class="varname">$releasever</code> の値を取得します。もし <code class="filename">/etc/yum.conf</code> にそのような行がなければ、<code class="command">yum</code> は <span class="package">redhat-release</span> パッケージからバージョン番号を取り出すことにより正しい値を推測します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="varname">$arch</code></span></dt><dd><div class="para">
+ Python の <code class="methodname">os.uname()</code> 関数を呼び出すとき返されるように、システムの CPU アーキテクチャーを参照するためにこの値を使用できます。<code class="varname">$arch</code> の有効な値は次のとおりです: <code class="literal">i586</code>, <code class="literal">i686</code> および <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">
+ システムの基本アーキテクチャーを参照するために <code class="varname">$basearch</code> を使用できます。たとえば、i686 と i586 のマシンはどちらも <code class="literal">i386</code> の基本アーキテクチャーを持ちます。また、AMD64 と Intel64 のマシンは <code class="literal">x86_64</code> の基本アーキテクチャーを持ちます。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="varname">$YUM0-9</code></span></dt><dd><div class="para">
+ これらの10個の変数は、同じ名前のシェル環境変数の値でそれぞれ置き換えられます。これらの変数のどれかが（たとえば <code class="filename">/etc/yum.conf</code> において）参照され、同じ名前を持つシェル環境変数が存在しなければ、設定ファイルの変数は置き換えられません。
+ </div></dd></dl></div><div class="para">
+ 個別の変数を定義する、または既存のものの値を上書きするには、<code class="filename">/etc/yum/vars/</code> ディレクトリに、変数と同じ名前を持つファイルを（<span class="quote">「<span class="quote"><code class="literal">$</code></span>」</span> 記号なしで）作成します。そして、その最初の行に希望する値を追加します。
+ </div><div class="para">
+ たとえば、リポジトリ記述はしばしばオペレーティングシステム名を含みます。<code class="varname">$osname</code> という新しい変数を定義するには、最初の行に <span class="quote">「<span class="quote">Fedora</span>」</span> を持つ新しいファイルを作成して、<code class="filename">/etc/yum/vars/osname</code> として保存します:
+ </div><pre class="screen">~]# <code class="command">echo "Fedora" > /etc/yum/vars/os名</code></pre><div class="para">
+ <span class="quote">「<span class="quote">Fedora 17</span>」</span> の代わりに、<code class="filename">.repo</code> ファイルにおいて以下を使用することができます:
+ </div><pre class="programlisting">name=$osname $releasever</pre></div><div class="section" id="sec-Viewing_the_Current_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.4. 現在の設定の表示</h3></div></div></div><div class="para">
+ Yum の全体オプション（つまり、<code class="filename">/etc/yum.conf</code> ファイルの <code class="literal">[main]</code> セクションにおいて指定されているオプション）の現在の値を表示するには、コマンドラインのオプションなしで <code class="command">yum-config-manager</code> を実行します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code></pre><div class="para">
+ 異なる設定セクションの内容を一覧表示するには、以下の形式でコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <em class="replaceable"><code>section</code></em>…</pre><div class="para">
+ すべての一致するセクションの設定を表示するためにグロブ表現を使用することもできます:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、すべての設定オプションとそれぞれ対応する値を一覧表示するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]$ <code class="command">yum-config-manager main \*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+================================== main ===================================
+[main]
+alwaysprompt = True
+assumeyes = False
+bandwith = 0
+bugtracker_url = https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%206&component=yum
+cache = 0
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre></div><div class="section" id="sec-Managing_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.5. Yum リポジトリの追加・有効化および無効化</h3></div></div></div><a id="idm124137184" class="indexterm"></a><div class="para">
+ <a class="xref" href="#sec-Setting_repository_Options">「[repository] オプションの設定」</a>は Yum リポジトリを定義するために使用できるさまざまなオプションを説明しています。このセクションは <code class="command">yum-config-manager</code> コマンドを使用することによりリポジトリを追加、有効化、および無効化する方法について説明しています。
+ </div><h4 id="bh-Managing_Yum_Repositories-Adding">Yum リポジトリの追加</h4><div class="para">
+ 新しいリポジトリを定義するには、<code class="filename">/etc/yum.conf</code> ファイルに <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションを追加するか、<code class="filename">/etc/yum.repos.d/</code> ディレクトリに <code class="filename">.repo</code> ファイルを追加します。このディレクトリにある <code class="filename">.repo</code> ファイル拡張子を持つすべてのファイルは <code class="command">yum</code> により読み込まれます。<code class="filename">/etc/yum.conf</code> にリポジトリを定義する代わりに、ここに定義することが最も良いです。
+ </div><div class="warning"><div class="admonition_header"><h2>信頼できないソフトウェア提供元を使用するとき注意してください</h2></div><div class="admonition"><div class="para">
+ 検証されていない、もしくは信頼されていないソフトウェア提供元からソフトウェアを取得またはインストールすることは、潜在的なセキュリティリスクになります、または、セキュリティ、安定性、互換性およびメンテナンス性の問題を引き起こす可能性があります。
+ </div></div></div><div class="para">
+ Yum リポジトリは一般的に自身の <code class="filename">.repo</code> ファイルを提供します。そのようなリポジトリをシステムに追加して有効にするには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--add-repo</code> <em class="replaceable"><code>repository_url</code></em></pre><div class="para">
+ …ここで <em class="replaceable"><code>repository_url</code></em> は <code class="filename">.repo</code> ファイルへのリンクです。たとえば、http://www.example.com/example.repo にあるリポジトリを追加するには、シェルプロンプトにおいて以下のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">yum-config-manager --add-repo http://www.example.com/example.repo</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+adding repo from: http://www.example.com/example.repo
+grabbing file http://www.example.com/example.repo to /etc/yum.repos.d/example.repo
+example.repo | 413 B 00:00
+repo saved to /etc/yum.repos.d/example.repo</pre><h4 id="bh-Managing_Yum_Repositories-Enabling">Yum リポジトリーの有効化</h4><div class="para">
+ 特定のリポジトリーを有効にするには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--enable</code> <em class="replaceable"><code>repository</code></em>…</pre><div class="para">
+ …ここで <em class="replaceable"><code>repository</code></em> は一意なリポジトリ ID です（利用可能なリポジトリ ID を一覧表示するには <code class="command">yum repolist all</code> を使用します）。代わりに、すべての一致するリポジトリを有効にするためにグロブ表現を使用できます。
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--enable</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、<code class="literal">[example]</code>, <code class="literal">[example-debuginfo]</code>, および <code class="literal">[example-source]</code> セクションに定義されたリポジトリーを無効にするには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum-config-manager --enable example\*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+============================== repo: example ==============================
+[example]
+bandwidth = 0
+base_persistdir = /var/lib/yum/repos/x86_64/6Server
+baseurl = http://www.example.com/repo/6Server/x86_64/
+cache = 0
+cachedir = /var/cache/yum/x86_64/6Server/example
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre><div class="para">
+ 成功したとき、<code class="command">yum-config-manager --enable</code> コマンドが現在のリポジトリ設定を表示します。
+ </div><h4 id="bh-Managing_Yum_Repositories-Disabling">Yum リポジトリの無効化</h4><div class="para">
+ Yum リポジトリを無効にするには、<code class="systemitem">root</code>として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--disable</code> <em class="replaceable"><code>repository</code></em>…</pre><div class="para">
+ …ここで <em class="replaceable"><code>repository</code></em> は一意なリポジトリ ID です（利用可能なリポジトリ ID を一覧表示するには <code class="command">yum repolist all</code> を使用します）。<code class="command">yum-config-manager --enable</code> と同様に、すべての一致するリポジトリを同時に無効にするためにグロブ表現を使用できます。
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--disable</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ 成功したとき、<code class="command">yum-config-manager --disable</code> コマンドが現在のリポジトリ設定を表示します。
+ </div></div><div class="section" id="sec-Creating_a_Yum_Repository"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.6. Yum リポジトリーの作成</h3></div></div></div><a id="idm131225584" class="indexterm"></a><div class="para">
+ Yum リポジトリーを構築するには、これらの手順に従ってください:
+ </div><div class="procedure" id="procedure-Setting_Up_a_Yum_repository"><ol class="1"><li class="step"><div class="para">
+ <span class="package">createrepo</span> パッケージのインストール:
+ </div><pre class="screen">~]# <code class="command">yum install createrepo</code></pre></li><li class="step"><div class="para">
+ <code class="filename">/mnt/local_repo/</code> のような 1 つのディレクトリーに全パッケージをコピーします。
+ </div></li><li class="step"><div class="para">
+ そのディレクトリーで <code class="command">createrepo --database</code> を実行します:
+ </div><pre class="screen">~]# <code class="command">createrepo --database /mnt/local_repo</code></pre></li></ol></div><div class="para">
+ This creates the necessary metadata for your Yum repository, as well as the <span class="application"><strong>sqlite</strong></span> database for speeding up <code class="command">yum</code> operations.
+ </div></div></div><div class="section" id="sec-Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Yum プラグイン</h2></div></div></div><a id="idm126828272" class="indexterm"></a><div class="para">
+ Yum はその機能を拡張および向上させるプラグインを提供します。特定のプラグインはデフォルトでインストールされます。あらゆる <code class="command">yum</code> コマンドを呼び出すときは必ず、Yum はプラグインがあればどれが読み込まれて有効化されているかを必ず通知します。たとえば:
+ </div><pre class="screen">~]# <code class="command">yum info yum</code>
+ロードされたプラグイン: langpacks, presto, refresh-packagekit
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre><div class="para">
+ <code class="command">Loaded plugins</code> に続くプラグイン名は <code class="option">--disableplugins=<em class="replaceable"><code>plugin_name</code></em></code> オプションに対して提供できる名前であることに注意してください。
+ </div><div class="section" id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.4.1. Yum プラグインの無効化、有効化、設定</h3></div></div></div><a id="idm116375632" class="indexterm"></a><a id="idm116374224" class="indexterm"></a><a id="idm97123968" class="indexterm"></a><div class="para">
+ Yum プラグインを有効にするには、<code class="filename">/etc/yum.conf</code> の <code class="literal">[main]</code> セクションに <code class="command">plugins=</code> で始まる行が存在して、その値が <code class="literal">1</code> に設定されていることを確実にします:
+ </div><pre class="programlisting">plugins=1</pre><div class="para">
+ この行を <code class="command">plugins=0</code> に変更することにより、すべてのプラグインを無効にできます。
+ </div><div class="important" id="important-Disabling_all_plugins_is_not_advised-plugins"><div class="admonition_header"><h2>すべてのプラグインを無効にすることは推奨されません</h2></div><div class="admonition"><div class="para">
+ あるプラグインは重要な <code class="command">Yum</code> サービスを提供するので、すべてのプラグインを無効にすることは推奨されません。プラグインを全体的に無効にすることは、便利なオプションとして提供され、一般的に <code class="command">Yum</code> に関する潜在的な問題を診断するときにのみ推奨されます。
+ </div></div></div><div class="para">
+ すべてのインストールされたプラグインは <code class="filename">/etc/yum/pluginconf.d/</code> ディレクトリに自身の設定ファイルを持ちます。これらのファイルにプラグイン固有のオプションを設定できます。たとえば、これは <span class="application"><strong>refresh-packagekit</strong></span> プラグインの <code class="filename">refresh-packagekit.conf</code> 設定ファイルです:
+ </div><pre class="programlisting">[main]
+enabled=1</pre><div class="para">
+ プラグインの設定ファイルは必ず <code class="literal">[main]</code> セクション（Yum の <code class="filename">/etc/yum.conf</code> ファイルと似ています）を含みます。<code class="command">yum</code> コマンドを実行するときにプラグインを有効にするかどうかを制御する <code class="literal">enabled=</code> オプションがあります（もしなければ置くことができます）。
+ </div><div class="para">
+ <code class="filename">/etc/yum.conf</code> において <code class="command">enabled=0</code> を設定することにより、すべてのプラグインを無効にしているならば、すべてのプラグインは各設定ファイルにおいて有効にしているかどうかによらず無効にされます。
+ </div><div class="para">
+ 単に1回の <code class="command">yum</code> コマンドのためにすべての Yum プラグインを無効にしたいならば、<code class="option">--noplugins</code> オプションを使用します。
+ </div><div class="para">
+ 1回の <code class="command">yum</code> コマンドのために1つかそれ以上の Yum プラグインを無効にしたいならば、コマンドに <code class="option">--disableplugin=<em class="replaceable"><code>plugin_name</code></em></code> オプションを追加します。たとえば、システムを更新中に <span class="application"><strong>presto</strong></span> プラグインを無効にするには、次のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">yum update --disableplugin=presto</code></pre><div class="para">
+ <code class="option">--disableplugin=</code> オプションに提供するプラグイン名は、すべての <code class="command">yum</code> コマンドの出力において <code class="command">Loaded plugins</code> 行に表示される名前と同じものです。複数のプラグインの名前をコンマで区切ることにより、それらを無効にできます。さらに、グロブ表現を使用することにより、複数のプラグイン名に一致されたり、長いものを省略したりできます:
+ </div><pre class="screen">~]# <code class="command">yum update --disableplugin=presto,refresh-pack*</code></pre></div><div class="section" id="sec-Installing_More_Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.4.2. 追加の Yum プラグインのインストール</h3></div></div></div><div class="para">
+ Yum プラグインは通常 <code class="filename">yum-plugin-<em class="replaceable"><code>plugin_name</code></em></code> パッケージ命名規約に従いますが、必ずしもそうとは限りません。たとえば、<span class="application"><strong>presto</strong></span> プラグインを提供するパッケージは <code class="filename">yum-presto</code> という名前です。他のパッケージをインストールする方法と同じように Yum プラグインをインストールできます。たとえば、<span class="application"><strong>security</strong></span> プラグインをインストールするには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum install yum-plugin-security</code></pre></div><div class="section" id="sec-Plugin_Descriptions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.4.3. プラグインの説明</h3></div></div></div><div class="para">
+ 以下の一覧は有用な Yum プラグインのいくつかを説明しています:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm58352544" class="indexterm"></a>
+ <span class="application"><strong>fs-snapshot</strong></span> (<span class="package">yum-plugin-fs-snapshot</span>)</span></dt><dd><div class="para">
+ <span class="application"><strong>fs-snapshot</strong></span> プラグインは、システムの更新やパッケージの削除のようなトランザクションを進める前にファイルシステムのスナップショットを作成するよう Yum を拡張します。トランザクションにより行われた変更が期待しないものとユーザーが思えば、このメカニズムによりユーザーがスナップショットに保存されている変更をロールバックできるようになります。
+ </div><div class="para">
+ プラグインが機能するためには、ルートファイルシステム（つまり、<code class="filename">/</code>）が <code class="systemitem">LVM</code> (Logical Volume Manager) または <code class="systemitem">Btrfs</code> ボリューム上になければいけません。LVM ボリュームにおいて <span class="application"><strong>fs-snapshot</strong></span> プラグインを使用するには、以下の手順に従います:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ ルートファイルシステムを持つボリュームグループが十分な空きエクステントを持つことを確実にします。必要な容量は、スナップショットのライフサイクルにおいて予想される、元の論理ボリュームへの変更量によります。適切なデフォルトは元の論理ボリューム容量の 50–80 % です。
+ </div><div class="para">
+ 特定のボリュームグループに関する詳細な情報を表示するには、<code class="systemitem">root</code> として以下の形式で <code class="command">vgdisplay</code> コマンドを実行します:
+ </div><pre class="synopsis"><code class="command">vgdisplay</code> <em class="replaceable"><code>volume_group</code></em></pre><div class="para">
+ フリーなエクステント数は <code class="literal">Free PE / Size</code> 行に一覧表示されます。
+ </div></li><li class="step"><div class="para">
+ ルートファイルシステムを持つボリュームグループが十分な空きエクステントを持たなければ、新しい物理ボリュームを追加します:
+ </div><ol class="a"><li class="step"><div class="para">
+ 論理ボリュームマネージャーを用いた物理ボリュームを初期化するには、<code class="systemitem">root</code> として、以下の形式で <code class="command">pvcreate</code> コマンドを実行します。
+ </div><pre class="synopsis"><code class="command">pvcreate</code> <em class="replaceable"><code>device</code></em></pre></li><li class="step"><div class="para">
+ 物理ボリュームをボリュームグループに追加するには、<code class="systemitem">root</code> として以下の形式で <code class="command">vgextend</code> コマンドを使用します:
+ </div><pre class="synopsis"><code class="command">vgextend</code> <em class="replaceable"><code>volume_group</code></em> <em class="replaceable"><code>physical_volume</code></em></pre></li></ol></li><li class="step"><div class="para">
+ <code class="filename">/etc/yum/pluginconf.d/fs-snapshot.conf</code> に置かれている設定ファイルを編集します。そして、以下の変更を <code class="literal">[lvm]</code> セクションに行います:
+ </div><ol class="a"><li class="step"><div class="para">
+ <code class="option">enabled</code> オプションの値を <code class="literal">1</code> に変更します:
+ </div><pre class="programlisting">enabled = 1</pre></li><li class="step"><div class="para">
+ <code class="option">lvcreate_size_args</code> 行の先頭からハッシュ記号（つまり、<code class="literal">#</code>）を削除し、論理エクステントの数をスナップショットのために割り当てるよう調整します。たとえば、元の論理ボリュームの容量の 80 % を割り当てるには、以下を使用します:
+ </div><pre class="programlisting">lvcreate_size_args = -l 80%ORIGIN</pre></li></ol><div class="para">
+ 利用可能な設定オプションの完全な一覧は<a class="xref" href="#tabl-Yum-Plugin_Descriptions-fs-snapshot">表4.3「サポートされる <code class="filename">fs-snapshot.conf</code> ディレクティブ」</a>を参照してください。
+ </div></li><li class="step"><div class="para">
+ 希望する <code class="command">yum</code> コマンドを実行し、変更を確認してトランザクションを進める前に、<span class="application"><strong>fs-snapshot</strong></span> が読み込んだプラグイン（<code class="literal">Loaded plugins</code> 行）の一覧に含まれることを確実にします。<span class="application"><strong>fs-snapshot</strong></span> プラグインは、それぞれの影響する論理ボリュームに対して以下の形式で行を表示します:
+ </div><pre class="synopsis">fs-snapshot: snapshotting <em class="replaceable"><code>file_system</code></em> (/dev/<em class="replaceable"><code>volume_group</code></em>/<em class="replaceable"><code>logical_volume</code></em>): <em class="replaceable"><code>logical_volume</code></em>_yum_<em class="replaceable"><code>timestamp</code></em></pre></li><li class="step"><div class="para">
+ システムが期待するとおりに動作していることを確認します:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ 変更を保持することを決めたならば、<code class="systemitem">root</code> として <code class="command">lvremove</code> コマンドを実行することにより、スナップショットを削除します:
+ </div><pre class="synopsis"><code class="command">lvremove</code> /dev/<em class="replaceable"><code>volume_group</code></em>/<em class="replaceable"><code>logical_volume</code></em>_yum_<em class="replaceable"><code>timestamp</code></em></pre></li>
+ <li class="step"><div class="para">
+ 変更を元に戻して、スナップショットに保存された状態にファイルシステムを復元することを決めたならば、以下の手順をとります:
+ </div><ol class="a"><li class="step"><div class="para">
+ スナップショットを元々の論理ボリュームに統合するには、<code class="systemitem">root</code> として、以下の形式でコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">lvconvert</code> <code class="option">--merge</code> /dev/<em class="replaceable"><code>volume_group</code></em>/<em class="replaceable"><code>logical_volume</code></em>_yum_<em class="replaceable"><code>timestamp</code></em></pre><div class="para">
+ <code class="command">lvconvert</code> コマンドは変更を反映するために必要となる再起動を促します。
+ </div></li><li class="step"><div class="para">
+ 指示されたとおりシステムを再起動します。シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力することに実行することもできます:
+ </div><pre class="synopsis"><code class="command">reboot</code></pre></li></ol></li>
+
+ </ul></li></ol></div><div class="para">
+ Btrfs ファイルシステムにおいて <span class="application"><strong>fs-snapshot</strong></span> を使用するには、以下の手順を実行します:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ 希望する <code class="command">yum</code> コマンドを実行し、変更を確認してトランザクションを進める前に、<span class="application"><strong>fs-snapshot</strong></span> が読み込んだプラグイン（<code class="literal">Loaded plugins</code> 行）の一覧に含まれることを確実にします。<span class="application"><strong>fs-snapshot</strong></span> プラグインは、それぞれの影響するファイルシステムに対して以下の形式で行を表示します:
+ </div><pre class="synopsis">fs-snapshot: snapshotting <em class="replaceable"><code>file_system</code></em>: <em class="replaceable"><code>file_system</code></em>/yum_<em class="replaceable"><code>timestamp</code></em></pre></li><li class="step"><div class="para">
+ システムが期待するとおりに動作していることを確認します:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ 変更を保持することを決めたならば、オプションで期待しないスナップショットを削除できます。Btrfs スナップショットを削除するには、<code class="systemitem">root</code> として以下の形式でコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">btrfs</code> <code class="option">subvolume</code> <code class="option">delete</code> <em class="replaceable"><code>file_system</code></em>/yum_<em class="replaceable"><code>timestamp</code></em></pre></li>
+ <li class="step"><div class="para">
+ 変更を元に戻して、スナップショットに保存されている状態にファイルシステムを戻すことを決めたならば、以下の手順をとります:
+ </div><ol class="a"><li class="step"><div class="para">
+ <code class="systemitem">root</code> として以下のコマンドを使用することにより特定のスナップショットの識別子を確認できます:
+ </div><pre class="synopsis"><code class="command">btrfs</code> <code class="option">subvolume</code> <code class="option">list</code> <em class="replaceable"><code>file_system</code></em></pre></li><li class="step"><div class="para">
+ <code class="systemitem">root</code> として、このスナップショットをデフォルトでマウントするようシステムを設定します:
+ </div><pre class="synopsis"><code class="command">btrfs</code> <code class="option">subvolume</code> <code class="option">set-default</code> <em class="replaceable"><code>id</code></em> <em class="replaceable"><code>file_system</code></em></pre></li><li class="step"><div class="para">
+ システムを再起動します。シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力することにより実行できます:
+ </div><pre class="synopsis"><code class="command">reboot</code></pre></li></ol></li>
+
+ </ul></li></ol></div><div class="para">
+ 論理ボリューム管理、Btrfs、およびファイルシステムスナップショットの詳細は <a href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/"><em class="citetitle">Fedora 17 Storage Administration Guide</em></a> を参照してください。プラグインとその設定に関する詳細は、<span class="bold bold"><strong>yum-fs-snapshot</strong></span>(1) および <span class="bold bold"><strong>yum-fs-snapshot.conf</strong></span>(5) のマニュアルページを参照してください。
+ </div><div class="table" id="tabl-Yum-Plugin_Descriptions-fs-snapshot"><h6>表4.3 サポートされる <code class="filename">fs-snapshot.conf</code> ディレクティブ</h6><div class="table-contents"><table summary="サポートされる fs-snapshot.conf ディレクティブ" border="1"><colgroup><col width="15%" class="section" /><col width="35%" class="directive" /><col width="50%" class="description" /></colgroup><thead><tr><th class="">
+ セクション
+ </th><th class="">
+ ｄ
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="" rowspan="2" valign="middle">
+ <code class="literal">[main]</code>
+ </td><td class="">
+ <code class="option">enabled</code>=<em class="replaceable"><code>value</code></em>
+ </td><td class="">
+ プラグインの有効化または無効化をできます。<em class="replaceable"><code>value</code></em> は <code class="literal">1</code> (有効) または <code class="literal">0</code> (無効) でなければいけません。インストールされるとき、プラグインはデフォルトで有効になっています。
+ </td></tr><tr><td class="">
+ <code class="option">exclude</code>=<em class="replaceable"><code>list</code></em>
+ </td><td class="">
+ 特定のファイルシステムを除外できます。値はスナップショットを<span class="emphasis"><em>したくない</em></span>マウントポイント（たとえば、<code class="literal">/srv /mnt/backup</code>）のスペース区切りの <em class="replaceable"><code>list</code></em> でなければいけません。このオプションはデフォルトにより設定ファイルに含まれません。
+ </td></tr><tr><td class="" rowspan="2" valign="middle">
+ <code class="literal">[lvm]</code>
+ </td><td class="">
+ <code class="option">enabled</code>=<em class="replaceable"><code>value</code></em>
+ </td><td class="">
+ LVM ボリュームにおいてプラグインの使用を有効化または無効化できます。<em class="replaceable"><code>value</code></em> は <code class="literal">1</code> (有効) または <code class="literal">0</code> (無効) のどちらかでなければいけません。このオプションはデフォルトで無効にされています。
+ </td></tr><tr><td class="">
+ <code class="option">lvcreate_size_args</code>=<em class="replaceable"><code>value</code></em>
+ </td><td class="">
+ 論理ボリュームのスナップショットの容量を指定できます。\n<em class="replaceable"><code>value</code></em> は有効な引数が続けられる <span class="application"><strong>lvcreate</strong></span> ユーティリティに対する <code class="option">-l</code> または <code class="option">-L</code> コマンドラインオプション（たとえば、<code class="literal">-l 80%ORIGIN</code>）でなければいけません。
+ </td></tr></tbody></table></div></div><br class="table-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm119454400" class="indexterm"></a>
+ <span class="application"><strong>presto</strong></span> (<span class="package">yum-presto</span>)</span></dt><dd><div class="para">
+ <span class="application"><strong>presto</strong></span> プラグインは、<span class="application"><strong>presto</strong></span> メタ情報を有効にしたリポジトリから更新している間に、<em class="firstterm">delta RPM</em> パッケージのダウンロードすることに関するサポートを Yum に追加します。delta RPM は、RPM パッケージを要求しているクライアントにインストールされているパッケージのバージョンとリポジトリにある更新されたバージョンの間の差異のみを含みます。
+ </div><div class="para">
+ delta RPM をダウンãƒãƒ¼ãƒ‰ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€æ›´æ–°ã•ã‚ŒãŸãƒ‘ッケージ全体をダウンãƒãƒ¼ãƒ‰ã™ã‚‹ã‚ˆã‚Šã‚‚ã‹ãªã‚Šæ—©ããªã‚Šã€æ›´æ–°ã‚’相対的ã«é€Ÿåº¦å‘上ã§ãã¾ã™ã€‚一度 delta RPM ãŒãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã•ã‚Œã‚‹ã¨ã€ç¾åœ¨ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るパッケージã«å¤‰æ›´ç‚¹ã‚’é©ç”¨ã™ã‚‹ãŸã‚ã«ãƒªãƒ“ルドã—ãªã‘ã‚Œã°ã„ã‘ã¾ã›ã‚“ã€ã“ã®ã‚ˆã†ã«å®Œå…¨ã‹ã¤æ›´æ–°ã•ã‚ŒãŸãƒ‘ッケージを作æˆã—ã¾ã™ã€‚ã“ã®ãƒ—ãƒã‚»ã‚¹ã¯ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¦ã„るマシンã«ãŠã„㦠CPU 時間を使用ã—ã¾ã™ã€‚ãã®ãŸã‚ã€delta RPM を使用ã™ã‚‹ã“ã¨ã¯ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æŽ¥ç¶šã«ä¾å˜ã™ã‚‹ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰æ™‚é–“ã€ãŠã‚ˆã³ CPU ã®é™ç•Œã«ã‚ˆã‚‹ãƒªãƒ“ルド時間ã®ãƒˆãƒ¬ãƒ¼ãƒ‰ã‚ªãƒ•ã«ãªã‚Šã¾ã™ã€‚<span class="application"><strong>presto</strong></span> プラグインを使用ã™ã‚‹ã“ã¨ã¯ã€æ¯”較的低速ãªãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æŽ¥ç¶šã‚’æŒã¤é«˜é€Ÿãªãƒžã‚·ãƒ³ã¨ã‚·ã‚¹ãƒ†ãƒ ã®ãŸã‚ã«æŽ¨å¥¨ã•ã‚
Œã¾ã™ã€‚一方ã€éžå¸¸ã«é«˜é€ŸãªæŽ¥ç¶šã‚’æŒã¤æ¯”較的低速ãªãƒžã‚·ãƒ³ã¯ã€é€šå¸¸ã® RPM パッケージをダウンãƒãƒ¼ãƒ‰ã™ã‚‹ã“ã¨ã€ã¤ã¾ã‚Š <span class="application"><strong>presto</strong></span> を無効ã«ã™ã‚‹ã“ã¨ã®æ©æµã‚’å—ã‘られる<span class="emphasis"><em>ã‹ã‚‚</em></span>ã—ã‚Œã¾ã›ã‚“。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm93394432" class="indexterm"></a>
+ <span class="application"><strong>refresh-packagekit</strong></span> (<span class="package">PackageKit-yum-plugin</span>)</span></dt><dd><div class="para">
+ <span class="application"><strong>refresh-packagekit</strong></span> プラグインは <code class="command">yum</code> を実行するときに必ず <span class="application"><strong>PackageKit</strong></span> の管理情報を更新します。<span class="application"><strong>refresh-packagekit</strong></span> プラグインはデフォルトでインストールされます。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm110362848" class="indexterm"></a>
+ <span class="application"><strong>rhnplugin</strong></span> (<span class="package">yum-rhn-plugin</span>)</span></dt><dd><div class="para">
+ <span class="application"><strong>rhnplugin</strong></span> は <code class="systemitem">RHN Classic</code> への接続サポートを提供します。これにより、<code class="systemitem">RHN Classic</code> を用いて登録されたシステムはこのシステムからパッケージを更新およびインストールできるようになります。
+ </div><div class="para">
+ プラグインに関する詳細は<span class="bold bold"><strong>rhnplugin</strong></span>(8) マニュアルページを参照してください。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm84676784" class="indexterm"></a>
+ <span class="application"><strong>security</strong></span> (<span class="package">yum-plugin-security</span>)</span></dt><dd><div class="para">
+ セキュリティ更新に関する情報を探して、簡単に適用することは、すべてのシステム管理者に対してしばしば重要になります。このため、Yum は <span class="application"><strong>security</strong></span> プラグインを提供します。これは非常に有用なセキュリティ関連のコマンド、サブコマンドおよびオプションを用いて <code class="command">yum</code> を拡張します。
+ </div><div class="para">
+ 以下のようにセキュリティ関連の更新をチェックできます:
+ </div><pre class="screen">~]# <code class="command">yum check-update --security</code>
+Loaded plugins: langpacks, presto, refresh-packagekit, security
+Limiting package lists to security relevant ones
+updates-testing/updateinfo | 329 kB 00:00
+9 package(s) needed for security, out of 270 available
+
+ConsoleKit.x86_64 0.4.5-1.fc15 updates
+ConsoleKit-libs.x86_64 0.4.5-1.fc15 updates
+ConsoleKit-x11.x86_64 0.4.5-1.fc15 updates
+NetworkManager.x86_64 1:0.8.999-2.git20110509.fc15 updates
+NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre><div class="para">
+ セキュリティ・アドバイザリにより影響されるパッケージを更新するには <code class="command">yum update --security</code> または <code class="command">yum update-minimal --security</code> を使用できます。これらのコマンドはどちらも、システムにあるセキュリティ・アドバイザリが発行されたパッケージをすべて更新します。<code class="command">yum update-minimal --security</code> はセキュリティ・アドバイザリの一部として公開された最新のパッケージに更新します。ここで <code class="command">yum update --security</code> はセキュリティ・アドバイザリにより影響されるすべてのパッケージを<span class="emphasis"><em>その利用可能なパッケージの最新バージョンに</em></span>更新します。
+ </div><div class="para">
+ 言い換えると、たとえば:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">kernel-2.6.38.4-20</span> パッケージはシステムにインストールされました;
+ </div></li><li class="listitem"><div class="para">
+ the <span class="package">kernel-2.6.38.6-22</span> パッケージがセキュリティアップデートとしてリリースされました;
+ </div></li><li class="listitem"><div class="para">
+ then <span class="package">kernel-2.6.38.6-26</span> はバグ修正アップデートとしてリリースされました、
+ </div></li></ul></div><div class="para">
+ ...そして <code class="command">yum update-minimal --security</code> は <span class="package">kernel-2.6.38.6-22</span> に更新します。また、<code class="command">yum update --security</code> は <span class="package">kernel-2.6.38.6-26</span> に更新します。保守的な管理者はできる限りパッケージを更新することにより生じるリスクを減らすために <code class="command">update-minimal</code> を使用したいと思うかもしれません。
+ </div><div class="para">
+ <span class="application"><strong>security</strong></span> プラグインが <code class="command">yum</code> に追加する機能改善に関する使用法の詳細とさらなる説明は、<span class="bold bold"><strong>yum-security</strong></span>(8) マニュアルページを参照してください。
+ </div></dd></dl></div></div></div><div class="section" id="sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.5. その他のリソース</h2></div></div></div><a id="idm124485120" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl.org/wiki/Guides</a></span></dt><dd><div class="para">
+ Yum wiki の <code class="literal">Yum Guides</code> セクションはさらなるドキュメントが含まれます。
+ </div></dd></dl></div></div></div><div xml:lang="ja-JP" class="chapter" id="ch-PackageKit" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第5章 PackageKit</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sec-Updating_Packages_with_Software_Update">5.1. ソフトウェアの更新を用いたパッケージの更新</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_preferences_for_checking_for_updates">5.1.1. 更新の確認間隔の設定</a></span></dt><dt><span class="section"><a href="#sec-Setting_preferences_for_software_sources">5.1.2. ソフトウェアソースの設定</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_Add_Remove_Software">5.2. ソフトウェアの追加/削除の使用</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. ソフトウェアソースの更新 (Yum リポジトリー)</a></span><
/dt><dt><span class="section"><a href="#sec-Finding_Packages_with_Filters">5.2.2. フィルターを用いたパッケージの検索</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Packages_and_Dependencies">5.2.3. パッケージ（および依存するもの）のインストールおよび削除</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Package_Groups">5.2.4. パッケージグループのインストールおよび削除</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Transaction_Log">5.2.5. トランザクションログの表示</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-PackageKit_Architecture">5.3. PackageKit アーキテクチャー</a></span></dt><dt><span class="section"><a href="#ch-Graphical_Package_Management-sec-Additional_Resources">5.4. その他のリソース</a></span></dt></dl></div><a id="idm131782800" class="indexterm"></a><a id="idm113045824"
class="indexterm"></a><a id="idm129482512" class="indexterm"></a><a id="idm51865872" class="indexterm"></a><a id="idm119445008" class="indexterm"></a><a id="idm96114816" class="indexterm"></a><a id="idm133038656" class="indexterm"></a><a id="idm111054656" class="indexterm"></a><a id="idm121724176" class="indexterm"></a><a id="idm119652816" class="indexterm"></a><a id="idm120072992" class="indexterm"></a><div class="para">
+ Fedora は、あなたのシステムと互換性のあるパッケージを表示、管理、更新、インストールおよびアンインストールするために <span class="application"><strong>PackageKit</strong></span> を提供します。<span class="application"><strong>PackageKit</strong></span> は、GNOME パネルメニューから、または <span class="application"><strong>PackageKit</strong></span> が更新を利用可能であることを通知するときに通知領域から開くことができるグラフィカルインターフェースがいくつかから構成されます。<span class="application"><strong>PackageKit</strong></span> のアーキテクチャーおよび利用可能なフロントエンドの詳細は、<a class="xref" href="#sec-PackageKit_Architecture">「PackageKit アーキテクチャー」</a>を参照してください。
+ </div><div class="section" id="sec-Updating_Packages_with_Software_Update"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. ソフトウェアの更新を用いたパッケージの更新</h2></div></div></div><a id="idm124346032" class="indexterm"></a><a id="idm118645312" class="indexterm"></a><div class="para">
+ <span class="guimenu"><strong>Activities</strong></span> メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの更新</strong></span>をクリックすることにより、<span class="application"><strong>ソフトウェアの更新</strong></span>を開くことができます。またはシェルプロンプトにおいて、<code class="command">gpk-update-viewer</code> コマンドを実行します。<span class="guilabel"><strong>ソフトウェアの更新</strong></span>ウィンドウにおいて、すべての利用可能な更新を、更新されるパッケージ（<code class="filename">.rpm</code> を除き、CPU アーキテクチャーを含みます）、パッケージの概要、および一般的に更新が提供する変更の概要とともに一覧表示します。インストー
ルしたくないすべての更新は、更新に対応するチェックボックスをチェック解除することにより、ここで選択解除できます。
+ </div><div class="figure" id="fig-Graphical_Package_Management-software_update"><div class="figure-contents"><div class="mediaobject"><img src="images/software-update.png" alt="ソフトウェアの更新を用いたアップデートのインストール" /><div class="longdesc"><div class="para">
+ installing 56 updates with PackageKit's software update window
+ </div></div></div></div><h6>図5.1 ソフトウェアの更新を用いたアップデートのインストール</h6></div><br class="figure-break" /><div class="para">
+ <span class="guilabel"><strong>ソフトウェアの更新</strong></span>ウィンドウのみに表示された更新は、利用可能な更新に対して現在インストールされているパッケージを表しています。
+ <a id="idm123837952" class="indexterm"></a>
+ <a id="idm108634880" class="indexterm"></a>
+ それらのパッケージに依存するもの（システムにある既存のパッケージか新しいものかどちらか）は、<span class="guibutton"><strong>更新のインストール</strong></span>をクリックするまで表示されません。
+ </div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> <a id="idm104249328" class="indexterm"></a>
+ <a id="idm123338640" class="indexterm"></a>
+ <a id="idm123337232" class="indexterm"></a>
+ は、システムに変更を加える要求をするときは必ず <span class="application"><strong>PolicyKit</strong></span> ツールキットにより提供される精密なユーザー認証
+ <a id="idm131021760" class="indexterm"></a>
+ 機能を使用します。<span class="application"><strong>PackageKit</strong></span> にパッケージの更新、インストールまたは削除を指示すると必ず、システムに変更を加える前にスーパーユーザーのパスワードを入力するよう要求されます。
+ </div><div class="para">
+ <code class="filename">kernel</code> パッケージを更新するよう <span class="application"><strong>PackageKit</strong></span> に指示すると、インストール後にプロンプトが表示され、システムを再起動して、新しくインストールしたカーネルから起動したいかどうかを尋ねられます。
+ </div><div class="section" id="sec-Setting_preferences_for_checking_for_updates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.1.1. 更新の確認間隔の設定</h3></div></div></div><a id="idm114542848" class="indexterm"></a><div class="para">
+ <span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>その他</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの更新</strong></span>を選択することにより、<span class="guilabel"><strong>ソフトウェアの更新の設定</strong></span>ウィンドウが開きます。<span class="guilabel"><strong>更新の設定</strong></span>タブにより、<span class="application"><strong>PackageKit</strong></span> がパッケージの更新を確認する間隔、およびすべての更新またはセキュリティ更新のみを自動的にインストールするかどうかを定義できます。<span class="guilabel"><strong>モバイル接続を使用するとき更新を確認する</strong></span>ボックスをチェック解除しておくことにより、ダウンロードするデータ
量に対して課金される無線接続を使用しているときに、膨大な帯域使用を避けるために適しています。
+ </div><div class="figure" id="fig-Graphical_Package_Management-Software_Update_Preferences"><div class="figure-contents"><div class="mediaobject"><img src="images/software-update-preferences.png" alt="PackageKit の更新の確認間隔の設定" /><div class="longdesc"><div class="para">
+ Setting the update-checking interval for PackageKit
+ </div></div></div></div><h6>図5.2 PackageKit の更新の確認間隔の設定</h6></div><br class="figure-break" /></div><div class="section" id="sec-Setting_preferences_for_software_sources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.1.2. ソフトウェアソースの設定</h3></div></div></div><div class="para">
+ ソフトウェアの更新をインストールするために使用するパッケージリポジトリを選択するには、<span class="guimenu"><strong>Activities</strong></span> メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>その他</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの更新</strong></span>を選択し、<span class="guilabel"><strong>ソフトウェアの更新の設定</strong></span>の<span class="guilabel"><strong>ソフトウェアのソース</strong></span>をクリックします。
+ </div><div class="figure" id="fig-Graphical_Package_Management-Software_Update_Software_Sources"><div class="figure-contents"><div class="mediaobject"><img src="images/software-update-software-sources.png" alt="PackageKit のソフトウェアソースの設定" /><div class="longdesc"><div class="para">
+ Setting the software sources for PackageKit
+ </div></div></div></div><h6>図5.3 PackageKit のソフトウェアソースの設定</h6></div><br class="figure-break" /><a id="idm21022832" class="indexterm"></a><a id="idm132998800" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> はソフトウェアのソースとして\n <span class="application"><strong>Yum</strong></span> リポジトリを参照します。すべてのソフトウェアを有効なソフトウェアのソースから取得します。<span class="guilabel"><strong>ソフトウェアのソース</strong></span>タブは、<code class="filename">/etc/yum.conf</code> 設定ファイルおよび <code class="filename">/etc/yum.repos.d/</code> ディレクトリにあるすべての <code class="filename"><em class="replaceable"><code>repository</code></em>.repo</code> にあるすべての [<em class="replaceable"><code>repository</code></em>] セクションの <code class="computeroutput">name=<em class="replaceable"><code>My Repository Name</code></em></code> 項目に書かれているようにリポジトリ名を表示します。
+ </div><div class="para">
+ <span class="guilabel"><strong>有効化</strong></span>ã®åˆ—ã«ãƒã‚§ãƒƒã‚¯ãŒã¤ã„ã¦ã„ã‚‹é …ç›®ã¯ã€å¯¾å¿œã™ã‚‹ãƒªãƒã‚¸ãƒˆãƒªãŒã™ã¹ã¦ã®æ›´æ–°ã¨ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã®è¦æ±‚（ä¾å˜é–¢ä¿‚ã®è§£æ±ºã‚’å«ã‚）を満ãŸã™ãƒ‘ッケージã®ä½ç½®ã‚’決ã‚ã‚‹ãŸã‚ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚<span class="guilabel"><strong>有効化</strong></span>ã®åˆ—㯠[<em class="replaceable"><code>repository</code></em>] セクションã«ãŠã‘ã‚‹ <code class="computeroutput">enabled=<em class="replaceable"><code><1 ã¾ãŸã¯ 0></code></em></code> é …ç›®ã«å¯¾å¿œã—ã¾ã™ã€‚ãƒã‚§ãƒƒã‚¯ãƒœãƒƒã‚¯ã‚¹ã‚’ãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€Yum リãƒã‚¸ãƒˆãƒªã‚’有効ã«ã—ã¾ã™ã€‚ã¾ãŸã€ãƒã‚§ãƒƒã‚¯è§£é™¤ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šç„¡åŠ¹ã«ã—ã¾ã™ã€‚リãƒã‚¸ãƒˆãƒªã‚’有効ã¾ãŸã¯ç„¡åŠ¹ã«ã™ã‚‹ã©ã¡ã‚‰ã‹ã®æ©Ÿèƒ½ã‚’実行ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€<span class="application"><strong>PolicyKit</strong></span> ãŒã‚¹ãƒ¼ãƒ‘ーユーザーã®èªè¨¼ã‚’ダイアãƒã‚°ã«è¦æ±‚ã
—ã¾ã™ã€‚<span class="application"><strong>PackageKit</strong></span> ã¯å®Ÿéš›ã« <code class="literal">enabled=<em class="replaceable"><code><1 ã¾ãŸã¯ 0></code></em></code> ãŒå˜åœ¨ã—ãªã‘ã‚Œã°ãã®è¡Œã‚’é©åˆ‡ãª [<em class="replaceable"><code>repository</code></em>] セクションã«æŒ¿å…¥ã—ã¾ã™ã€‚ã¾ãŸã¯ã€å˜åœ¨ã™ã‚Œã°å€¤ã‚’変更ã—ã¾ã™ã€‚ã¤ã¾ã‚Šã€<span class="guilabel"><strong>ソフトウェアã®ã‚½ãƒ¼ã‚¹</strong></span>ウィンドウを通ã—ã¦ãƒªãƒã‚¸ãƒˆãƒªã‚’有効化ã¾ãŸã¯ç„¡åŠ¹åŒ–ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚¦ã‚£ãƒ³ãƒ‰ã‚¦ã‚’é–‰ã˜ãŸå¾Œã¾ãŸã¯ã‚·ã‚¹ãƒ†ãƒ ã‚’å†èµ·å‹•ã—ãŸå¾Œã«å¤‰æ›´ã‚’永続化ã•ã›ã¾ã™ã€‚å¿…è¦ã«å¿œã˜ã¦ãƒªãƒã‚¸ãƒˆãƒªã‚’ç°¡å˜ã«æœ‰åŠ¹åŒ–ã¾ãŸã¯ç„¡åŠ¹åŒ–ã™ã‚‹æ©Ÿèƒ½ã¯ <span class="application"><strong>PackageKit</strong></span> ã®éžå¸¸ã«ä¾¿åˆ©ãªæ©Ÿèƒ½ã§ã™ã€‚
+ </div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> を通して <span class="application"><strong>Yum</strong></span> リポジトリの追加または削除ができないことに注意してください。
+ </div><div class="note" id="note-Showing_Source_RPM_and_Test_Repositories"><div class="admonition_header"><h2>source RPM, test, および debuginfo リポジトリの表示</h2></div><div class="admonition"><div class="para">
+ <span class="guilabel"><strong>ソフトウェアのソース</strong></span> タブの下部にあるボックスをチェックすることにより、<span class="application"><strong>PackageKit</strong></span> が source RPM, testing および debuginfo リポジトリを同じように表示するようになります。このボックスはデフォルトでチェックされていません。
+ </div></div></div></div></div><div class="section" id="sec-Using_Add_Remove_Software"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. ソフトウェアの追加/削除の使用</h2></div></div></div><a id="idm108392816" class="indexterm"></a><a id="idm83980064" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> の <span class="application"><strong>ソフトウェアの更新</strong></span> GUI ウィンドウは、直感的に同じようなインターフェースを持ちますが、<span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>アプリケーションと独立したアプリケーションです。新しいパッケージを検索およびインストールするには、<span class="guimenu"><strong>Activities</strong></span> メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの追加/削除</strong></span>を選択するか、シェルプロンプトにおいて <code class="command">gpk-application</code> コマンドを実行します。
+ </div><div class="figure" id="fig-Graphical_Package_Management-add_remove_software"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software.png" alt="PackageKit のソフトウェアの追加/削除ウィンドウ" /><div class="longdesc"><div class="para">
+ Viewing PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>図5.4 PackageKit のソフトウェアの追加/削除ウィンドウ</h6></div><br class="figure-break" /><div class="section" id="sec-Refreshing_Software_Sources_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.1. ソフトウェアソースの更新 (Yum リポジトリー)</h3></div></div></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> リポジトリを有効化または無効化するには、<span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアのソース</strong></span>をクリックしてダイアログボックスを開き、<span class="guilabel"><strong>ソフトウェアのソース</strong></span>タブを選択します。利用可能な設定オプションの詳細は<a class="xref" href="#sec-Setting_preferences_for_software_sources">「ソフトウェアソースの設定」</a>を参照してください。
+ </div><div class="para">
+ 適切な <span class="application"><strong>Yum</strong></span> リポジトリの有効化・無効化後、利用可能なパッケージの最新一覧を持っていることを確実にしなければいけません。<span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>パッケージ一覧の更新</strong></span>をクリックすると、<span class="application"><strong>PackageKit</strong></span> は、すべての利用可能なソフトウェアのソース、つまり <span class="application"><strong>Yum</strong></span> リポジトリからパッケージの最新一覧を取得します。
+ </div></div><div class="section" id="sec-Finding_Packages_with_Filters"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.2. フィルターを用いたパッケージの検索</h3></div></div></div><a id="idm95094304" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>を開き、<span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアのソース</strong></span>をクリックすることにより、すべての<span class="emphasis"><em>設定済み</em></span>かつフィルターされていない（以下参照） <span class="application"><strong>Yum</strong></span> リポジトリの一覧を表示できます。一度ソフトウェアのソースが更新されると、<span class="application"><strong>PackageKit</strong></span> が<span class="guilabel"><strong>検索</strong></span>の問い合わせ結果をより速く取得できるよう、いくつかのフィルターを適用することに有益です。これはとくに、多くのパッケージ検索を実行するときに助けになります。<span class="guimenu"><strong>フィルター</strong></span>ドロップダウ
ンメニューにある4つのフィルターは一つの基準に一致するまたは一致しないことにより結果を分割するために使用されます。デフォルトで、<span class="application"><strong>PackageKit</strong></span> が起動するとき、これらのフィルターはすべて適用されませんが（<span class="guibutton"><strong>フィルターなし</strong></span>）、一度それらのどれかによりフィルターすると、そのフィルターは変更するか <span class="application"><strong>PackageKit</strong></span> を閉じるまで設定されたままになります。
+ </div><div class="para">
+ 通常システムにインストールされて<span class="emphasis"><em>いない</em></span>利用可能なパッケージを検索するので、<span class="guimenu"><strong>フィルター</strong></span> → <span class="guimenuitem"><strong>インストール済</strong></span> を選択し、<span class="guimenuitem"><strong>利用可能なもののみ</strong></span>ラジオボタンを選択します。
+ <a id="idm129481104" class="indexterm"></a>
+ <a id="idm129479216" class="indexterm"></a>
+ <a id="idm127357968" class="indexterm"></a>
+ <a id="idm133186864" class="indexterm"></a>
+ <a id="idm133185008" class="indexterm"></a>
+ </div><div class="figure" id="Graphical_Package_Management-filters-only_available"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-filters-available.png" alt="すでにインストールされているパッケージのフィルター" /><div class="longdesc"><div class="para">
+ filtering out packages which are already installed
+ </div></div></div></div><h6>図5.5 すでにインストールされているパッケージのフィルター</h6></div><br class="figure-break" /><div class="para">
+ <a id="idm108307376" class="indexterm"></a>
+ <a id="idm131566992" class="indexterm"></a>
+ <a id="idm131565104" class="indexterm"></a>
+ また、C ヘッダーファイルのように開発版が必要でなければ、<span class="guimenu"><strong>エンドユーザーのファイルのみ</strong></span>のためにフィルターできます。そして、そうするとき、興味がない <code class="filename"><em class="replaceable"><code>package_name</code></em>-devel</code> をすべてフィルターで消します。
+ </div><div class="figure" id="fig-Graphical_Package_Management-filters-only_end_user"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-filters-end-user.png" alt="検索結果の一覧からの開発パッケージのフィルター" /><div class="longdesc"><div class="para">
+ filtering out development packages from our results
+ </div></div></div></div><h6>図5.6 検索結果の一覧からの開発パッケージのフィルター</h6></div><br class="figure-break" /><div class="para">
+ サブメニューにある残り 2 つのフィルターは次のとおりです:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guisubmenu"><strong>グラフィカル</strong></span> <a id="idm108597232" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ GUI インターフェースを提供するアプリケーション（<span class="guibutton"><strong>グラフィカルなもののみ</strong></span>）、またはそうではないものに検索を絞ります。このフィルターは特別な機能を実行する GUI アプリケーションを閲覧するときに有用です。
+ </div></dd><dt class="varlistentry"><span class="term"><span class="guisubmenu"><strong>Free</strong></span> <a id="idm83194112" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ フリーソフトウェアであると考えられるパッケージを検索します。承認されたライセンスの詳細は <a href="https://fedoraproject.org/wiki/Licensing#SoftwareLicenses">Fedora Licensing List</a> を参照してください。
+ </div></dd></dl></div><div class="para">
+ 残りのチェックボックスのフィルターは必ずチェックまたは解除されます。それらは以下のものです:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guimenuitem"><strong>サブパッケージを隠す</strong></span></span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>サブパッケージを隠す</strong></span> <a id="idm85493104" class="indexterm"></a>
+ チェックボックスをチェックすることにより、一般的に必要なパッケージの依存性のみである、興味のないパッケージをフィルターします。たとえば、<span class="guimenuitem"><strong>サブパッケージを隠す</strong></span>をチェックして、 <code class="filename"><em class="replaceable"><code>package</code></em> </code> を検索することにより、以下の関連パッケージを<span class="guibutton"><strong>検索</strong></span>結果からフィルターで隠します（もし存在すれば）:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code>package</code></em>-devel</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code>package</code></em>-libs</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code>package</code></em>-libs-devel</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code>package</code></em>-debuginfo</code>
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><span class="guimenuitem"><strong>最新パッケージのみ</strong></span></span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>最新パッケージのみ</strong></span> <a id="idm108378944" class="indexterm"></a>
+ を選択すると、結果の一覧から同じパッケージの古いバージョンはすべてフィルターされます。これは一般的に期待することでしょう。
+ </div><div class="important" id="important-Using_the_Only_newest_items_filter"><div class="admonition_header"><h2>最新パッケージのみフィルターの使用</h2></div><div class="admonition"><div class="para">
+ <span class="guimenuitem"><strong>最新パッケージのみ</strong></span>を選択すると、結果の一覧からあらゆるパッケージの最新のバージョン以外はフィルターされます。このフィルターは、新しい（インストールされていない）パッケージの利用可能な最新バージョンを検索するために、しばしば<span class="guimenuitem"><strong>利用可能なもののみ</strong></span> フィルターと組み合わせられます。
+ </div></div></div></dd><dt class="varlistentry"><span class="term">ディストリ固有のパッケージのみ</span></dt><dd><div class="para">
+ 複数ライブラリのシステムにおいて<span class="guimenuitem"><strong>ディストリ固有のパッケージのみ</strong></span> <a id="idm104311184" class="indexterm"></a>
+ ボックスをãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€<span class="application"><strong>PackageKit</strong></span> ãŒ<span class="emphasis"><em>互æ›ãƒ¢ãƒ¼ãƒ‰</em></span>ã«ãŠã„ã¦å®Ÿè¡Œã™ã‚‹ã‚¢ãƒ¼ã‚テクãƒãƒ£ãƒ¼ã®ãŸã‚ã«ã‚³ãƒ³ãƒ‘イルã—ãŸãƒ‘ッケージã«å¯¾ã™ã‚‹çµæžœã‚’一覧表示ã™ã‚‹ã“ã¨ã‚’çœç•¥ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€AMD64 CPU ã‚’æŒã¤ 64ビットシステムã«ãŠã„ã¦ã“ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’有効ã«ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€AMD64 マシンã«ãŠã„ã¦å®Ÿè¡Œã§ãるパッケージã§ã‚ã£ã¦ã‚‚ã€32ビット x86 CPU アーã‚テクãƒãƒ£ãƒ¼ã®ãŸã‚ã«ãƒ“ルドã•ã‚ŒãŸãƒ‘ッケージをã™ã¹ã¦çµæžœã®ä¸€è¦§ã«è¡¨ç¤ºã—ãªã„よã†ã«ã—ã¾ã™ã€‚アーã‚テクãƒãƒ£ãƒ¼éžä¾å˜ã®ï¼ˆã¤ã¾ã‚Šã€<code class="filename">crontabs-1.10-32.1.el6.noarch.rpm</code> ã®ã‚ˆã†ãª <em class="firstterm">noarch</em>ã®ï¼‰ãƒ‘ッケージã¯ã€<span class="guimenuitem"><strong>ディストリ固有ã®ãƒ‘ッケージã®ã¿</strong></span>ã‚’ãƒã‚§ã
ƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã•ã‚Œã¾ã›ã‚“。ã“ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã¯ x86 マシンã®ã‚ˆã†ãªéžè¤‡æ•°ãƒ©ã‚¤ãƒ–ラリã®ã‚·ã‚¹ãƒ†ãƒ ã«å½±éŸ¿ã—ã¾ã›ã‚“。
+ </div></dd></dl></div></div><div class="section" id="sec-Installing_and_Removing_Packages_and_Dependencies"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.3. パッケージ（および依存するもの）のインストールおよび削除</h3></div></div></div><a id="idm95214112" class="indexterm"></a><a id="idm95212624" class="indexterm"></a><div class="para">
+ 2つのフィルター、<span class="guibutton"><strong>利用可能なもののみ</strong></span>および<span class="guibutton"><strong>エンドユーザーのファイルのみ</strong></span>を選択すると、<span class="application"><strong>htop</strong></span> 対話式プロセスビューアーを検索して、パッケージをハイライトします。いくつかの非常に有用な情報を得ることができます。これは、クリック可能なプロジェクトのホームページ、もしあれば、見つかった <span class="application"><strong>Yum</strong></span> パッケージグループ、パッケージのライセンス、適用できれば、アプリケーションを開ける GNOME メニュー位置、およびダウンロードしてインストールするときに関連するパッケージの容量を含みます。
+ </div><div class="figure" id="fig-Graphical_Package_Management-install"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-install.png" alt="PackageKit のソフトウェアの追加/削除ウィンドウを用いたパッケージの表示およびインストール" /><div class="longdesc"><div class="para">
+ PackageKit のソフトウェアの追加/削除ウィンドウを用いたパッケージの表示およびインストール
+ </div></div></div></div><h6>図5.7 PackageKit のソフトウェアの追加/削除ウィンドウを用いたパッケージの表示およびインストール</h6></div><br class="figure-break" /><div class="para">
+ パッケージã¾ãŸã¯ã‚°ãƒ«ãƒ¼ãƒ—ã®éš£ã«ã‚ã‚‹ãƒã‚§ãƒƒã‚¯ãƒœãƒƒã‚¯ã‚¹ã‚’ãƒã‚§ãƒƒã‚¯ã•ã‚Œã¦ã„ã‚‹ã¨ãã€ãã®é …ç›®ã¯ã™ã§ã«ã‚·ã‚¹ãƒ†ãƒ ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã¾ã™ã€‚ãƒã‚§ãƒƒã‚¯ã•ã‚Œã¦ãªã„ボックスをãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹ã¨ã„ã†<span class="emphasis"><em>å°ã‚’ã¤ã‘ã‚‹</em></span>ã“ã¨ã«ãªã‚Šã¾ã™ã€‚インストールã¯<span class="guibutton"><strong>é©ç”¨</strong></span>ボタンãŒã‚¯ãƒªãƒƒã‚¯ã•ã‚ŒãŸã¨ãã®ã¿å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚ã“ã®ã‚ˆã†ã«ã€å®Ÿéš›ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã®ãƒˆãƒ©ãƒ³ã‚¶ã‚¯ã‚·ãƒ§ãƒ³ã‚’実行ã™ã‚‹å‰ã«è¤‡æ•°ã®ãƒ‘ッケージã¾ãŸã¯ãƒ‘ッケージグループを検索ãŠã‚ˆã³é¸æŠžã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã•ã‚‰ã«ã€ãƒã‚§ãƒƒã‚¯ãƒœãƒƒã‚¯ã‚¹ã®ãƒã‚§ãƒƒã‚¯ã‚’解除ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸãƒ‘ッケージを削除ã§ãã¾ã™ã€‚ã¾ãŸã€å‰Šé™¤ã¯<span class="guibutton"><strong>é©ç”¨</strong></span>ãŒæŠ¼ã•ã‚ŒãŸã¨ãã«ã™ã¹ã¦ã
®ä¿ç•™ã«ãªã£ã¦ã„るインストールã¨ã¨ã‚‚ã«å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚ä¾å˜æ€§ã®è§£æ±º
+ <a id="idm130064656" class="indexterm"></a>
+ （これはインストールまたは削除される追加のパッケージを追加するかもしれません）、<span class="guibutton"><strong>適用</strong></span>を押した後に実行されます。その後、<span class="application"><strong>PackageKit</strong></span> はインストールまたは削除するそれらの追加のパッケージを一覧表示するウィンドウを表示して、進めるかどうかを確認します。
+ </div><div class="para">
+ <span class="application"><strong>htop</strong></span> ã‚’ãƒã‚§ãƒƒã‚¯ã—ã¦ã€<span class="guibutton"><strong>é©ç”¨</strong></span>ボタンをクリックã—ã¾ã™ã€‚スーパーユーザーã®ãƒ‘スワードを入力è¦æ±‚ã•ã‚Œã¾ã™ã€‚ãれを入力ã™ã‚‹ã¨ã€<span class="application"><strong>PackageKit</strong></span> 㯠<span class="application"><strong>htop</strong></span> をインストールã—ã¾ã™ã€‚<span class="application"><strong>PackageKit</strong></span> ã®ç´ 晴らã—ã„機能ã®ä¸€ã¤ã¯ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã«å¾“ã£ã¦ã€ã¨ãã©ãæ–°ã—ãインストールã•ã‚ŒãŸã‚¢ãƒ—リケーションã®ä¸€è¦§ã‚’表示ã—ã¦ã€ãれらを直ã¡ã«å®Ÿè¡Œã™ã‚‹ã‚ˆã†é¸æŠžã‚’æ案ã™ã‚‹ã“ã¨ã§ã™ã€‚代ã‚ã‚Šã«ã€<span class="guilabel"><strong>ソフトウェアã®è¿½åŠ /削除</strong></span>ウィンドウã«ãŠã„ã¦ã€ãƒ‘ッケージを検索ã—ã¦é¸æŠžã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚¢ãƒ—リケーションã®ã‚·ãƒ§ãƒ¼ãƒˆã‚«ãƒƒãƒˆãŒç½®ã‹ã‚Œã‚‹ GNOME ã
ƒ¡ãƒ‹ãƒ¥ãƒ¼ã®<span class="guilabel"><strong>å ´æ‰€</strong></span>を示ã™ã“ã¨ã‚’覚ãˆã¦ãŠã„ã¦ãã ã•ã„。ãã‚Œã¯ã‚¢ãƒ—リケーションを実行ã—ãŸã„ã¨ãã«å½¹ç«‹ã¡ã¾ã™ã€‚
+ </div><div class="para">
+ 一度インストールすると、シェルプロンプトにおいて次のように入力することにより、<code class="command">top</code> プロセスビューアーのカラフルかつ高度なバージョンである <code class="command">htop</code> を実行できます:
+ </div><pre class="screen"><code class="command">htop</code></pre><div class="para">
+ <span class="application"><strong>htop</strong></span> は素晴らしいですが、<code class="command">top</code> で十分であるため、アンインストールすることにします。<span class="guibutton"><strong>利用可能なもののみ</strong></span>フィルターを<span class="guimenu"><strong>フィルター</strong></span> → <span class="guimenuitem"><strong>インストール済み</strong></span> install it to <span class="guibutton"><strong>インズトール済のもののみ</strong></span>に忘れずに変更することにより、再び <span class="application"><strong>htop</strong></span> を検索して、チェック解除します。プログラムはそれ自身の依存するものを何もインストールしません。もしあれば、システムにインストールされた他のパッケージにそれが何も依存していなければ、自動的に同じように削除されます。
+ </div><div class="warning" id="warning-PackageKit-Removing_a_Package_Without_Removing_Packages_Depending_on_It"><div class="admonition_header"><h2>他のパッケージに依存するときにパッケージを削除する</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> がパッケージのインストール中および削除中に自動的に依存関係を解決しますが、それに依存するパッケージも削除することなくパッケージを削除することはできません。この種の操作は <span class="application"><strong>RPM</strong></span> によってのみ実行できますが、推奨されません。これにより、システムが潜在的に機能しない状態になったり、アプリケーションが誤動作やクラッシュを起こしたりする可能性があります。
+ </div></div></div><div class="figure" id="fig-Graphical_Package_Management-removing_a_package"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-remove.png" alt="PackageKit のソフトウェアの追加/削除を用いたパッケージの削除" /><div class="longdesc"><div class="para">
+ Removing the htop package with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>図5.8 PackageKit のソフトウェアの追加/削除を用いたパッケージの削除</h6></div><br class="figure-break" /></div><div class="section" id="sec-Installing_and_Removing_Package_Groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.4. パッケージグループのインストールおよび削除</h3></div></div></div><a id="idm131706816" class="indexterm"></a><a id="idm131705328" class="indexterm"></a><a id="idm115517728" class="indexterm"></a><a id="idm130347440" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> は、<span class="guilabel"><strong>パッケージコレクション</strong></span>と呼ばれる <span class="application"><strong>Yum</strong></span> パッケージグループをインストールする機能もあります。<span class="guilabel"><strong>ソフトウェアの更新</strong></span>ウィンドウにおいてカテゴリーの左上の一覧にある<span class="guilabel"><strong>パッケージコレクション</strong></span>をクリックすることにより、インストールしたいパッケージグループをスクロールして検索することができます。この場合、チェコ語の言語サポート（<span class="guilabel"><strong>チェコ語のサポート</strong></span>グループ）をインストールしたいです。ボックスをチェックして、<span class="guibutton"><strong>適用</strong></span>をクリックすることにより、パッ
ケージグループの依存関係を満たすためにインストールしなければいけない<span class="emphasis"><em>追加の</em></span>パッケージの数を表示します。
+ </div><div class="figure" id="fig-Graphical_Package_Management-installing_a_package_group"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-package-group.png" alt="チェコ語サポートのパッケージグループのインストール" /><div class="longdesc"><div class="para">
+ Using PackageKit to install Czech language support with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>図5.9 チェコ語サポートのパッケージグループのインストール</h6></div><br class="figure-break" /><div class="para">
+ 同様に、インストールされたパッケージグループは、<span class="guilabel"><strong>パッケージコレクション</strong></span>を選択し、適切なチェックボックスをチェック解除し、適用することによりアンインストールできます。
+ </div></div><div class="section" id="sec-Viewing_the_Transaction_Log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.5. トランザクションログの表示</h3></div></div></div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> は実行したトランザクションのログ
+ <a id="idm99902864" class="indexterm"></a>
+ <a id="idm99901456" class="indexterm"></a>
+ を維持します。ログを表示するには、<span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>ウィンドウから<span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアのログ</strong></span>をクリックします、またはシェルプロンプトにおいて <code class="command">gpk-log</code> コマンドを実行します。
+ </div><div class="para">
+ <span class="guilabel"><strong>ソフトウェア更新履歴ビューアー</strong></span>は、<code class="literal">更新されたパッケージ</code>や<code class="literal">インストール済みパッケージ</code>、アクションが実行された<span class="guilabel"><strong>日付</strong></span>、アクションを実行した<span class="guilabel"><strong>ユーザー名</strong></span>、およびユーザーが使用したフロントエンドの<span class="guilabel"><strong>アプリケーション</strong></span>（たとえば、<code class="literal">ソフトウェアの追加/削除</code>や<code class="literal">システムの更新</code>）のような<span class="guilabel"><strong>アクション</strong></span>を表示します。<span class="guilabel"><strong>詳細</strong></span>の列は、トランザクションが実行されたパッケージの一覧と同じように、<code class="literal">更新</code>、<code class="lite
ral">インストール</code>、または<code class="literal">削除</code>のような、トランザクションの種類を提供します。
+ </div><div class="figure" id="fig-Graphical_Package_Management-Software_Log_Viewer"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-log.png" alt="ソフトウェアログビューアーを用いたパッケージ管理トランザクションのログの表示" /><div class="longdesc"><div class="para">
+ Viewing the log of package management transactions with PackageKit's Software Log Viewer window
+ </div></div></div></div><h6>図5.10 ソフトウェアログビューアーを用いたパッケージ管理トランザクションのログの表示</h6></div><br class="figure-break" /><div class="para">
+ 上部のテキスト入力フィールドにパッケージの名前を入力することにより、パッケージに影響するトランザクションの一覧をフィルターします。
+ </div></div></div><div class="section" id="sec-PackageKit_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.3. PackageKit アーキテクチャー</h2></div></div></div><a id="idm98750640" class="indexterm"></a><div class="para">
+ Fedora は、システムと互換性のあるパッケージおよびパッケージグループを表示、更新、インストールおよびアンインストールするためのアプリケーションである <span class="application"><strong>PackageKit</strong></span> スイートを提供します。アーキテクチャーとして、<span class="application"><strong>PackageKit</strong></span> は <code class="command">packagekitd</code> デーモンのバックエンドと通信するグラフィカルなフロントエンドいくつかから構成されます。これは、いパッケージのインストールや削除などのような、実際のトランザクションを実行するために <span class="application"><strong>Yum</strong></span> を利用する、パッケージマネージャー固有のバックエンドと通信します。
+ </div><div class="para">
+ <a class="xref" href="#table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands">表5.1「PackageKit GUI ウィンドウ、メニュー位置、およびシェルプロンプトコマンド」</a>は、GUI ウィンドウの名前、GNOME デスクトップまたは<span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>ウィンドウからウィンドウを起動する方法、およびウィンドウを開くコマンドラインアプリケーションの名前を示しています。
+ </div><div class="table" id="table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands"><h6>表5.1 PackageKit GUI ウィンドウ、メニュー位置、およびシェルプロンプトコマンド</h6><div class="table-contents"><table summary="PackageKit GUI ウィンドウ、メニュー位置、およびシェルプロンプトコマンド" border="1"><colgroup><col align="left" class="col1" width="25%" /><col align="left" class="col2" width="25%" /><col align="left" class="col3" width="25%" /><col align="left" class="col4" width="25%" /></colgroup><thead><tr><th class="" align="left">
+ ウィンドウタイトル
+ </th><th class="" align="left">
+ 機能
+ </th><th class="" align="left">
+ 開き方
+ </th><th class="" align="left">
+ シェルコマンド
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ ソフトウェアの追加/削除
+ </td><td class="" align="left">
+ パッケージ情報のインストール、削除、または表示
+ </td><td class="" align="left">
+ <div class="para">
+ GNOME パネルから: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>管理</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの追加/削除</strong></span>
+ </div>
+
+ </td><td class="" align="left">
+ gpk-application
+ </td></tr><tr><td class="" align="left">
+ ソフトウェアの更新
+ </td><td class="" align="left">
+ パッケージの更新の実行
+ </td><td class="" align="left">
+ <div class="para">
+ GNOME パネルから: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>管理</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの更新</strong></span>
+ </div>
+
+ </td><td class="" align="left">
+ gpk-update-viewer
+ </td></tr><tr><td class="" align="left">
+ ソフトウェア提供元
+ </td><td class="" align="left">
+ <span class="application"><strong>Yum</strong></span> リポジトリーの有効化および無効化
+ </td><td class="" align="left">
+ <div class="para">
+ <span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>から: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアリポジトリ</strong></span>
+ </div>
+
+ </td><td class="" align="left">
+ gpk-repo
+ </td></tr><tr><td class="" align="left">
+ ソフトウェア更新履歴ビューアー
+ </td><td class="" align="left">
+ トランザクションログの表示
+ </td><td class="" align="left">
+ <div class="para">
+ <span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>から: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアログ</strong></span>
+ </div>
+
+ </td><td class="" align="left">
+ gpk-log
+ </td></tr><tr><td class="" align="left">
+ ソフトウェアの更新の設定
+ </td><td class="" align="left">
+ <span class="application"><strong>PackageKit</strong></span> の設定
+ </td><td class="" align="left">
+ </td><td class="" align="left">
+ gpk-prefs
+ </td></tr><tr><td class="" align="left">
+ (通知エリアの警告)
+ </td><td class="" align="left">
+ 更新が利用可能なときに警告する
+ </td><td class="" align="left">
+ <div class="para">
+ GNOME パネルから: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>設定</strong></span> → <span class="guimenuitem"><strong>スタートアップアプリケーション</strong></span>, <span class="guilabel"><strong>スタートアッププログラム</strong></span> タブ
+ </div>
+
+ </td><td class="" align="left">
+ gpk-update-icon
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ <code class="command">packagekitd</code> デーモンは、ユーザーセッションの外で実行され、さまざまなグラフィカルフロントウィンドウと通信します。<code class="command">packagekitd</code> デーモン<a href="#ftn.footnote-Daemons" class="footnote"><sup class="footnote" id="footnote-Daemons">[1]</sup></a> <span class="application"><strong>DBus</strong></span> システムメッセージバス経由で他のバックエンドを通信します。これは、システムに問い合わせを実行したり、変更を加えるために <span class="application"><strong>Yum</strong></span> の Python API を利用します。Red Hat Enterprise Linux と Fedora 以外の Linux システムにおいて、<code class="command">packagekitd</code> は、そのシステム固有のパッケージマネージャーを使用できる他のバックエンドと通信できます。このモジュール型アーキテクチャーは、同じ
種類のパッケージ管理タスクを基本的に実行できるよう、多くの異なるパッケージマネージャーとともに機能するために必要なグラフィカルインターフェースの抽象化を提供します。<span class="application"><strong>PackageKit</strong></span> フロントエンドをどのように使用するかを学ぶことは、<span class="application"><strong>Yum</strong></span> 以外のディストリビューション固有のパッケージマネージャーを利用するときさえ、多くの異なる Linux ディストリビューションにわたり同じようなグラフィカルインターフェースを使用できることを意味します。
+ </div><div class="para">
+ さらに、<span class="application"><strong>PackageKit</strong></span> の関心の分離により、GUI ウィンドウ—またはユーザーの X Window セッション—のどれかのクラッシュに信頼性を与えます。これは、ユーザーセッションの外側で実行する <code class="command">packagekitd</code> デーモンにより管理されるあらゆるパッケージ管理タスクに影響しません。
+ </div><div class="para">
+ 本章で説明されるフロントエンドのグラフィカルアプリケーションはすべて <span class="application"><strong>PackageKit</strong></span> とその依存パッケージの代わりに <code class="filename">gnome-packagekit</code> パッケージにより提供されます。KDE 環境を利用しているユーザーは、<span class="application"><strong>PackageKit</strong></span> の KDE インターフェースを提供する <code class="filename">kpackagekit</code> パッケージをインストールしたいかもしれません。
+ </div><div class="para">
+ 最後に、<span class="application"><strong>PackageKit</strong></span> は <code class="command">pkcon</code> というコンソールベースのフロントエンドからも利用できます。
+ </div></div><div class="section" id="ch-Graphical_Package_Management-sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. その他のリソース</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="application"><strong>PackageKit</strong></span> ホームページ — <a href="http://www.packagekit.org/index.html">http://www.packagekit.org/index.html</a></span></dt><dd><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> のメーリングリストに関する情報です。
+ </div></dd><dt class="varlistentry"><span class="term"><span class="application"><strong>PackageKit</strong></span> FAQ — <a href="http://www.packagekit.org/pk-faq.html">http://www.packagekit.org/pk-faq.html</a></span></dt><dd><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> ソフトウェアスイートのよくある質問の参考一覧です。
+ </div></dd><dt class="varlistentry"><span class="term"><span class="application"><strong>PackageKit</strong></span> 機能マトリクス — <a href="http://www.packagekit.org/pk-matrix.html">http://www.packagekit.org/pk-matrix.html</a></span></dt><dd><div class="para">
+ パッケージ管理のバックエンドの長い一覧を持つ、<span class="application"><strong>PackageKit</strong></span> が提供する機能の相互参照です。
+ </div></dd></dl></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="footnote-Daemons" class="footnote"><div class="para"><a href="#footnote-Daemons" class="para"><sup class="para">[1] </sup></a>
+ システムデーモンは一般的に、ユーザーや他のプログラムにサービスを提供し、しばしば起動時に開始される、長時間実行されるプロセスです。デーモンは <code class="command">systemctl</code> コマンドに応答し、<code class="command">systemctl enable</code> または <code class="command">systemctl disable</code> コマンドを使用することにより永続的に無効化または有効化できます。一般的に <code class="command">packagekitd</code> デーモンのように <span class="quote">「<span class="quote"><span class="emphasis"><em>d</em></span></span>」</span> を付け加えることにより認識できます。システムサービスに関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div></div></div></div><div class="part" id="part-Networking"><div class="titlepage"><div><div text-align="center"><h1 class="title">パート III. ネットワーク</h1></div></div></div><div class="partintro" id="idm97605184"><div></div><div class="para">
+ このパートは Fedora においてネットワークを設定する方法を説明しています。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="#ch-NetworkManager">6. NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-The_NetworkManager_Daemon">6.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">6.2. Interacting with NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network">6.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connections">6.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automatically">6.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="#sec-User_and_System_Connections">6.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Establi
shing_Connections">6.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Wired_Ethernet_Connection">6.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Wireless_Connection">6.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">6.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">6.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">6.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_Routes">6.3.6. Establishing Routes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">6.4. Configuring Connection Settings</a></span></dt><dd>
<dl><dt><span class="section"><a href="#sec-Configuring_802.1x_Security">6.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Wireless_Security">6.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_PPP_Point-to-Point_Settings">6.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv4_Settings">6.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_Settings">6.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-NetworkManager_Architecture">6.5. NetworkManager Architecture</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Network_Interfaces">7. ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ»ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-networkscripts-files">7.1. ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯è¨å®šãƒ•ã‚¡ã‚¤ã
ƒ«</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-interfaces">7.2. インターフェースè¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-networkscripts-interfaces-eth0">7.2.1. イーサãƒãƒƒãƒˆ インターフェース</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-chan">7.2.2. ãƒãƒ£ãƒ³ãƒãƒ«ãƒ»ãƒœãƒ³ãƒ‡ã‚£ãƒ³ã‚°ãƒ»ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces_network-bridge">7.2.3. ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ–リッジ</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces_802.1q-vlan-tagging">7.2.4. Setting up 802.1q VLAN tagging</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-alias">7.2.5. エイリアス ファイルã¨ã‚¯ãƒãƒ¼ãƒ³ ファイル</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-ppp0">7.2.6. ダイヤルアップ インターフã
‚§ãƒ¼ã‚¹</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-other">7.2.7. ä»–ã®ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-networkscripts-control">7.3. インターフェース制御スクリプト</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-static-routes">7.4. スタティック ルートã®è¨å®š</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-functions">7.5. ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æ©Ÿèƒ½ãƒ•ã‚¡ã‚¤ãƒ«</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-resources">7.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-networkscripts-docs-inst">7.6.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt></dl></dd></dl></dd></dl></div></div><div xml:lang="ja-JP" class="chapter" id="ch-NetworkManager" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第6ç« NetworkManager</h2></div>
</div></div><div class="toc"><dl><dt><span class="section"><a href="#sec-The_NetworkManager_Daemon">6.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">6.2. Interacting with NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network">6.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connections">6.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automatically">6.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="#sec-User_and_System_Connections">6.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Establishing_Connections">6.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishin
g_a_Wired_Ethernet_Connection">6.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Wireless_Connection">6.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">6.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">6.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">6.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_Routes">6.3.6. Establishing Routes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">6.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_802.1x_Security">6.4.1. Configuring 802.1x Security</a></span></dt>
<dt><span class="section"><a href="#sec-Configuring_Wireless_Security">6.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_PPP_Point-to-Point_Settings">6.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv4_Settings">6.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_Settings">6.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-NetworkManager_Architecture">6.5. NetworkManager Architecture</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> is a dynamic network control and configuration system that attempts to keep network devices and connections up and active when they are available. <span class="application"><strong>NetworkManager</strong></span> consists of a core daemon, a GNOME Notification Area applet that provides network status information, and graphical configuration tools that can create, edit and remove connections and interfaces. <span class="application"><strong>NetworkManager</strong></span> can be used to configure the following types of connections: Ethernet, wireless, mobile broadband (such as cellular 3G), and <code class="systemitem">DSL</code> and <code class="systemitem">PPPoE</code> (Point-to-Point over Ethernet). In addition, <span class="application"><strong>NetworkManager</strong></span> allows for the configuration of network aliases, static routes, DNS information and VPN connections, as well as many connection-specifi
c parameters. Finally, <span class="application"><strong>NetworkManager</strong></span> provides a rich API via D-Bus which allows applications to query and control network configuration and state.
+ </div><div class="para">
+ Previous versions of Fedora included the <span class="application"><strong>Network Administration Tool</strong></span>, which was commonly known as <code class="command">system-config-network</code> after its command line invocation. In Fedora 17, <span class="application"><strong>NetworkManager</strong></span> replaces the former <span class="application"><strong>Network Administration Tool</strong></span> while providing enhanced functionality, such as user-specific and mobile broadband configuration. It is also possible to configure the network in Fedora 17 by editing interface configuration files; refer to <a class="xref" href="#ch-Network_Interfaces">7章<em>ネットワーク・インターフェース</em></a> for more information.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> may be installed by default on Fedora. To ensure that it is, first run the following command as the root user:
+ </div><pre class="screen">~]# <code class="command">yum install NetworkManager</code>
+</pre><div class="section" id="sec-The_NetworkManager_Daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. The NetworkManager Daemon</h2></div></div></div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> daemon runs with root privileges and is usually configured to start up at boot time. You can determine whether the <span class="application"><strong>NetworkManager</strong></span> daemon is running by entering this command as root:
+ </div><pre class="screen">~]# <code class="command">service NetworkManager status</code>
+NetworkManager (pid 1527) is running...
+</pre><div class="para">
+ The <code class="command">service</code> command will report <code class="computeroutput">NetworkManager is stopped</code> if the <span class="application"><strong>NetworkManager</strong></span> service is not running. To start it for the current session:
+ </div><pre class="screen">~]# <code class="command">service NetworkManager start</code>
+</pre><div class="para">
+ Run the <code class="command">chkconfig</code> command to ensure that <span class="application"><strong>NetworkManager</strong></span> starts up every time the system boots:
+ </div><pre class="screen">~]# <code class="command">chkconfig NetworkManager on</code>
+</pre><div class="para">
+ For more information on starting, stopping and managing services and runlevels, refer to <a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>.
+ </div></div><div class="section" id="sec-Interacting_with_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Interacting with NetworkManager</h2></div></div></div><div class="para">
+ Users do not interact with the <span class="application"><strong>NetworkManager</strong></span> system service directly. Instead, you can perform network configuration tasks via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet. The applet has multiple states that serve as visual indicators for the type of connection you are currently using.
+ </div><div class="figure" id="exam-Interacting_with_NetworkManager"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-AppletStates_Gnome3"><img src="images/Network_Configuration-NM-AppletStates_Gnome3.png" alt="NetworkManager applet states" /><div class="longdesc"><div class="para">
+ A row of four icons representing NetworkManager applet states
+ </div></div></div></div><h6>図6.1 NetworkManager applet states</h6></div><br class="figure-break" /><div class="para">
+ If you do not see the <span class="application"><strong>NetworkManager</strong></span> applet in the GNOME panel, and assuming that the <span class="application"><strong>NetworkManager</strong></span> package is installed on your system, you can start the applet by running the following command as a normal user (not root):
+ </div><pre class="screen">~]$ <code class="command">nm-applet &</code>
+</pre><div class="para">
+ After running this command, the applet appears in your Notification Area.
+ </div><div class="section" id="sec-Connecting_to_a_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.1. Connecting to a Network</h3></div></div></div><div class="para">
+ When you click on the applet icon, you are presented with:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a list of categorized networks you are currently connected to (such as <span class="guilabel"><strong>Wired</strong></span> and <span class="guilabel"><strong>Wireless</strong></span>);
+ </div></li><li class="listitem"><div class="para">
+ a list of all <span class="guilabel"><strong>Available Networks</strong></span> that <span class="application"><strong>NetworkManager</strong></span> has detected;
+ </div></li><li class="listitem"><div class="para">
+ options for connecting to any configured Virtual Private Networks (VPNs); and,
+ </div></li><li class="listitem"><div class="para">
+ options for connecting to hidden or new wireless networks.
+ </div></li></ul></div><div class="para">
+ If you are connected to a network, its name is presented first under its network type, such as <span class="guilabel"><strong>Wired</strong></span> or <span class="guilabel"><strong>Wireless</strong></span> with a bulletpoint to the left. When many networks are available, such as wireless access points, the <span class="guilabel"><strong>More</strong></span> networks expandable menu entry appears.
+ </div><div class="figure" id="exam-Connecting_to_a_Network"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3"><img src="images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png" alt="The NetworkManager applet's drop-down menu, showing all available and connected-to networks" /><div class="longdesc"><div class="para">
+ A screen shot of the NetworkManager applet's drop-down menu, showing all available and connected-to networks
+ </div></div></div></div><h6>図6.2 The <span class="application">NetworkManager</span> applet's drop-down menu, showing all available and connected-to networks</h6></div><br class="figure-break" /></div><div class="section" id="sec-Configuring_New_and_Editing_Existing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.2. Configuring New and Editing Existing Connections</h3></div></div></div><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet to open the drop-down menu, this is the main point of entry for interacting with <span class="application"><strong>NetworkManager</strong></span> to configure connections.
+ </div><div class="para">
+ If the system has detected a wired connection, the <span class="guilabel"><strong>Wired</strong></span> menu entry will appear. If the system has detected a wireless card, then you will also see a <span class="guilabel"><strong>Wireless</strong></span> menu entry. Clicking the <span class="guilabel"><strong>Wired</strong></span> and <span class="guilabel"><strong>Wireless</strong></span> labels or the associated ON OFF indicator to the right will toggle the status between ON and OFF.
+ </div><div class="para">
+ Finally, clicking on the <span class="guilabel"><strong>Network Settings</strong></span> menu entry opens the <span class="guilabel"><strong>Network</strong></span> window, from where you can view some basic network configuration information and initiate configuration tasks.
+ </div><div class="figure" id="exam-Network_Configuration_NM_Network_Wired_Gnome3"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_Network_Wired_Gnome3_Fed17"><img src="images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png" alt="Configure networks using the Network window" /><div class="longdesc"><div class="para">
+ A screen shot of NetworkManager's Network window.
+ </div></div></div></div><h6>図6.3 Configure networks using the Network window</h6></div><br class="figure-break" /><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ wired Ethernet connections, click on <span class="guilabel"><strong>Wired</strong></span> followed by <span class="guilabel"><strong>Options</strong></span> and proceed to <a class="xref" href="#sec-Establishing_a_Wired_Ethernet_Connection">「Establishing a Wired (Ethernet) Connection」</a>;
+ </div></li><li class="listitem"><div class="para">
+ wireless connections, click on <span class="guilabel"><strong>Wireless</strong></span> followed by <span class="guilabel"><strong>Options</strong></span> and proceed to <a class="xref" href="#sec-Establishing_a_Wireless_Connection">「Establishing a Wireless Connection」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ mobile broadband connections, proceed to <a class="xref" href="#sec-Establishing_a_Mobile_Broadband_Connection">「Establishing a Mobile Broadband Connection」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ VPN connections, click on the <span class="guilabel"><strong>VPN</strong></span> menu entry followed by <span class="guilabel"><strong>Options</strong></span> and proceed to <a class="xref" href="#sec-Establishing_a_VPN_Connection">「Establishing a VPN Connection」</a>. If there is no VPN menu entry click on the plus sign at the bottom. A dialog box appears. Ensure the interface is set to VPN. Click the <span class="guibutton"><strong>Create</strong></span> button to open the <span class="guilabel"><strong>Choose a VPN Connection Type</strong></span> assistant. Proceed to <a class="xref" href="#Network_Configuration-VPN-step2">ステップ 5</a>
+ </div></li></ul></div></div><div class="section" id="sec-Connecting_to_a_Network_Automatically"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.3. Connecting to a Network Automatically</h3></div></div></div><div class="para">
+ For any connection type you add or configure, you can choose whether you want <span class="application"><strong>NetworkManager</strong></span> to try to connect to that network automatically when it is available.
+ </div><div class="procedure" id="procedure-Configuring_NetworkManager_to_Connect_to_a_Network_Automatically_When_Detected"><h6>手順6.1 Configuring NetworkManager to Connect to a Network Automatically When Detected</h6><ol class="1"><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guilabel"><strong>Network Settings</strong></span>.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Network </strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the type of connection from the left-hand-side menu.
+ </div></li><li class="step"><div class="para">
+ Click on <span class="guilabel"><strong>Configure</strong></span>
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Connect automatically</strong></span> to cause <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the connection whenever <span class="application"><strong>NetworkManager</strong></span> detects that it is available. Unselect the checkbox if you do not want <span class="application"><strong>NetworkManager</strong></span> to connect automatically. If the box is unchecked, you will have to select that connection manually in the <span class="application"><strong>NetworkManager</strong></span> applet's initial menu to cause it to connect.
+ </div></li></ol></div></div><div class="section" id="sec-User_and_System_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.4. User and System Connections</h3></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> connections are always either <span class="emphasis"><em>user connections</em></span> or <span class="emphasis"><em>system connections</em></span>. Depending on the system-specific policy that the administrator has configured, users may need root privileges to create and modify system connections. <span class="application"><strong>NetworkManager</strong></span>'s default policy enables users to create and modify user connections, but requires them to have root privileges to add, modify or delete system connections.
+ </div><div class="para">
+ User connections are so-called because they are specific to the user who creates them. In contrast to system connections, whose configurations are stored under the <code class="filename">/etc/sysconfig/network-scripts/</code> directory (mainly in <code class="filename">ifcfg-<em class="replaceable"><code><network_type></code></em> </code> interface configuration files), user connection settings are stored in the GConf configuration database and the GNOME keyring, and are only available during login sessions for the user who created them. Thus, logging out of the desktop session causes user-specific connections to become unavailable.
+ </div><div class="note" id="note-Tip-Increase_security_by_making_VPN_connections_user-specific"><div class="admonition_header"><h2>Increase security by making VPN connections user-specific</h2></div><div class="admonition"><div class="para">
+ Because <span class="application"><strong>NetworkManager</strong></span> uses the GConf and GNOME keyring applications to store user connection settings, and because these settings are specific to your desktop session, it is highly recommended to configure your personal VPN connections as user connections. If you do so, other non-root users on the system cannot view or access these connections in any way.
+ </div></div></div><div class="para">
+ System connections, on the other hand, become available at boot time and can be used by other users on the system without first logging in to a desktop session.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> can quickly and conveniently convert user to system connections and vice versa. Converting a user connection to a system connection causes <span class="application"><strong>NetworkManager</strong></span> to create the relevant interface configuration files under the <code class="filename">/etc/sysconfig/network-scripts/</code> directory, and to delete the GConf settings from the user's session. Conversely, converting a system to a user-specific connection causes <span class="application"><strong>NetworkManager</strong></span> to remove the system-wide configuration files and create the corresponding GConf/GNOME keyring settings.
+ </div><div class="figure" id="exam-User_and_System_Connections"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-Available_to_all_users"><img src="images/Network_Configuration-NM-Available_to_all_users_Gnome3.png" alt="The Available to all users checkbox controls whether connections are user-specific or system-wide" /><div class="longdesc"><div class="para">
+ A screen shot of the Available to all users checkbox
+ </div></div></div></div><h6>図6.4 The <span class="guilabel">Available to all users</span> checkbox controls whether connections are user-specific or system-wide</h6></div><br class="figure-break" /><div class="procedure" id="procedure-Changing_a_Connection_to_be_User-Specific_instead_of_System-Wide_or_Vice-Versa"><h6>手順6.2 Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa</h6><div class="note" id="note-Depending_on_the_systems_policy_root_privileges_may_be_required"><div class="admonition_header"><h2>Root privileges may be required</h2></div><div class="admonition"><div class="para">
+ Depending on the system's policy, you may need root privileges on the system in order to change whether a connection is user-specific or system-wide.
+ </div></div></div><ol class="1"><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Network Settings</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the menu entry for the type of network connection you want to configure.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Configure</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Check the <span class="guilabel"><strong>Available to all users</strong></span> checkbox to ask <span class="application"><strong>NetworkManager</strong></span> to make the connection a system-wide connection. Depending on system policy, you may then be prompted for the root password by the <span class="application"><strong>PolicyKit</strong></span> application. If so, enter the root password to finalize the change.
+ </div><div class="para">
+ Conversely, uncheck the <span class="guilabel"><strong>Available to all users</strong></span> checkbox to make the connection user-specific.
+ </div></li></ol></div></div></div><div class="section" id="sec-Establishing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Establishing Connections</h2></div></div></div><div class="section" id="sec-Establishing_a_Wired_Ethernet_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.1. Establishing a Wired (Ethernet) Connection</h3></div></div></div><div class="para">
+ To establish a wired network connection, click on the <span class="application"><strong>NetworkManager</strong></span> applet to open its menu, then click on <span class="guilabel"><strong>Network Settings</strong></span>. This opens the <span class="guilabel"><strong>Network</strong></span> window.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Wired</strong></span> menu entry and then click <span class="guilabel"><strong>Configure</strong></span>.
+ </div><div class="figure" id="exam-Establishing_a_Wired_Ethernet_Connection"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-Editing_Wired_Connection_Gnome3"><img src="images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png" alt="Editing the newly-created Wired connection 1" /><div class="longdesc"><div class="para">
+ A screen shot of Network Manager's Wired tab
+ </div></div></div></div><h6>図6.5 Editing the newly-created Wired connection 1</h6></div><br class="figure-break" /><div class="para">
+ The system startup scripts create and configure a single wired connection called <span class="guilabel"><strong>System eth0</strong></span> by default on all systems. Although you can edit <span class="guilabel"><strong>System eth0</strong></span>, creating a new wired connection for your custom settings is recommended. You can create a new wired connection by selecting the <span class="guilabel"><strong>Wired</strong></span> tab and clicking the <span class="guibutton"><strong>Add</strong></span> button.
+ </div><div class="note" id="note-The_dialog_for_adding_and_editing_connections_is_the_same"><div class="admonition_header"><h2>The dialog for adding and editing connections is the same</h2></div><div class="admonition"><div class="para">
+ When you add a new connection by clicking the <span class="guibutton"><strong>Add</strong></span> button, <span class="application"><strong>NetworkManager</strong></span> creates a new configuration file for that connection and then opens the same dialog that is used for editing an existing connection. There is no difference between these dialogs. In effect, you are always editing a connection; the difference only lies in whether that connection previously existed or was just created by <span class="application"><strong>NetworkManager</strong></span> when you clicked <span class="guibutton"><strong>Add</strong></span>.
+ </div></div></div><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wired">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>Wired</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">「Connecting to a Network Automatically」</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-User_and_System_Connections">「User and System Connections」</a> for details.
+ </div></li></ul></div><h4 id="bh-Configuring_the_Wired_Tab">Configuring the Wired Tab</h4><div class="para">
+ The final two configurable settings are located within the <span class="guilabel"><strong>Wired</strong></span> tab itself: the first is a text-entry field where you can specify a MAC (Media Access Control) address, and the second allows you to specify the MTU (Maximum Transmission Unit) value. Normally, you can leave the <span class="guilabel"><strong>MAC address</strong></span> field blank and the <span class="guilabel"><strong>MTU</strong></span> set to <strong class="userinput"><code>automatic</code></strong>. These defaults will suffice unless you are associating a wired connection with a second or specific NIC, or performing advanced networking. In such cases, refer to the following descriptions:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MAC Address</strong></span> </span></dt><dd><div class="para">
+ Network hardware such as a Network Interface Card (NIC) has a unique MAC address (Media Access Control; also known as a <em class="firstterm">hardware address</em>) that identifies it to the system. Running the <code class="command">ip addr</code> command will show the MAC address associated with each interface. For example, in the following <code class="command">ip addr</code> output, the MAC address for the <span class="guilabel"><strong>eth0</strong></span> interface (which is <code class="computeroutput"> 52:54:00:26:9e:f1</code>) immediately follows the <code class="computeroutput">link/ether</code> keyword:
+ </div><pre class="screen">~]# <code class="command">ip addr</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+ link/ether <span class="emphasis"><em>52:54:00:26:9e:f1</em></span> brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.251/24 brd 192.168.122.255 scope global eth0
+ inet6 fe80::5054:ff:fe26:9ef1/64 scope link
+ valid_lft forever preferred_lft forever</pre><div class="para">
+ A single system can have one or more NICs installed on it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific NIC with a specific connection (or connections). As mentioned, you can determine the MAC address using the <code class="command">ip addr</code> command, and then copy and paste that value into the <span class="guilabel"><strong>MAC address</strong></span> text-entry field.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ The MTU (Maximum Transmission Unit) value represents the size in bytes of the largest packet that the connection will use to transmit. This value defaults to <code class="constant">1500</code> when using IPv4, or a variable number <code class="constant">1280</code> or higher for IPv6, and does not generally need to be specified or changed.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-Wired">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your wired connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="#sec-Connecting_to_a_Network">「Connecting to a Network」</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port-based Network Access Control (PNAC), click the <span class="guilabel"><strong>802.1x Security</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_802.1x_Security">「Configuring 802.1x Security」</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">「Configuring IPv4 Settings」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">「Configuring IPv6 Settings」</a>.
+ </div></li></ul></div></div><div class="section" id="sec-Establishing_a_Wireless_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.2. Establishing a Wireless Connection</h3></div></div></div><div class="para">
+ This section explains how to use <span class="application"><strong>NetworkManager</strong></span> to configure a wireless (also known as Wi-Fi or 802.1<em class="replaceable"><code>a/b/g/n</code></em>) connection to an Access Point.
+ </div><div class="para">
+ To configure a mobile broadband (such as 3G) connection, refer to <a class="xref" href="#sec-Establishing_a_Mobile_Broadband_Connection">「Establishing a Mobile Broadband Connection」</a>.
+ </div><h4 id="bh-Quickly_Connecting_to_an_Available_Access_Point">Quickly Connecting to an Available Access Point</h4><div class="para">
+ The easiest way to connect to an available access point is to click on the <span class="application"><strong>NetworkManager</strong></span> applet, locate the <em class="firstterm">Service Set Identifier</em> (SSID) of the access point in the list of available networks, and click on it. If the access point is secured, a dialog prompts you for authentication.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> tries to auto-detect the type of security used by the access point. If there are multiple possibilities, <span class="application"><strong>NetworkManager</strong></span> guesses the security type and presents it in the <span class="guilabel"><strong>Wireless security</strong></span> dropdown menu. To see if there are multiple choices, click the <span class="guilabel"><strong>Wireless security</strong></span> dropdown menu and select the type of security the access point is using. If you are unsure, try connecting to each type in turn. Finally, enter the key or passphrase in the <span class="guilabel"><strong>Password</strong></span> field. Certain password types, such as a 40-bit WEP or 128-bit WPA key, are invalid unless they are of a requisite length. The <span class="guilabel"><strong>Connect</strong></span> button will remain inactive until you enter a key of the length required for the selected securit
y type. To learn more about wireless security, refer to <a class="xref" href="#sec-Configuring_Wireless_Security">「Configuring Wireless Security」</a>.
+ </div><div class="para">
+ If <span class="application"><strong>NetworkManager</strong></span> connects to the access point successfully, its applet icon will change into a graphical indicator of the wireless connection's signal strength.
+ </div><div class="figure" id="exam-Establishing_a_Wireless_Connection_Signal-Strength-Applet-icon"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_AppletStates_WiFi_Gnome3"><img src="images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png" alt="Applet icon indicating wireless connection signal strength" /><div class="longdesc"><div class="para">
+ A screen shot of the Signal Strength Applet icon indicating wireless connection signal strength
+ </div></div></div></div><h6>図6.6 Applet icon indicating wireless connection signal strength</h6></div><br class="figure-break" /><h4 id="bh-Connecting_to_a_Hidden_Wireless_Network">Connecting to a Hidden Wireless Network</h4><div class="para">
+ All access points have a <em class="firstterm">Service Set Identifier</em> (SSID) to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID, authentication method, and secrets.
+ </div><div class="para">
+ To connect to a hidden wireless network, click <span class="application"><strong>NetworkManager</strong></span>'s applet icon and then click <span class="guilabel"><strong>Network Settings</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears. Select the <span class="guilabel"><strong>Wireless</strong></span> menu entry and then click to the right of the <span class="guilabel"><strong>Network Name</strong></span> to activate the drop-down list. Select <span class="guilabel"><strong>Other</strong></span>. The <span class="guilabel"><strong>Hidden wireless network</strong></span> dialog window appears.
+ </div><div class="figure" id="exam-Establishing_a_Wireless_Connection_Wireless-Tab"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3"><img src="images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png" alt="Hidden wireless network dialog window" /><div class="longdesc"><div class="para">
+ A screen shot of NetworkManager's Hidden wireless network dialog window
+ </div></div></div></div><h6>図6.7 Hidden wireless network dialog window</h6></div><br class="figure-break" /><div class="para">
+ If you have connected to the hidden network before, use the <span class="guilabel"><strong>Connection</strong></span> drop-down list to select it, and click <span class="guibutton"><strong>Connect</strong></span>. If you have not, leave the <span class="guilabel"><strong>Connection</strong></span> dropdown as <span class="guimenuitem"><strong>New...</strong></span>, enter the SSID of the hidden network, select its <span class="guilabel"><strong>Wireless security</strong></span> method, enter the correct authentication secrets, and click <span class="guibutton"><strong>Connect</strong></span>.
+ </div><div class="para">
+ For more information on wireless security settings, refer to <a class="xref" href="#sec-Configuring_Wireless_Security">「Configuring Wireless Security」</a>.
+ </div><h4 id="bh-Editing_a_Connection_or_Creating_a_Completely_New_One">Editing a Connection, or Creating a Completely New One</h4><div class="para">
+ You can create a new connection by clicking on the <span class="application"><strong>NetworkManager</strong></span> applet to open its menu.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Network Settings</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Wireless</strong></span> menu entry.
+ </div></li><li class="step"><div class="para">
+ Click to the right of the <span class="guilabel"><strong>Network Name</strong></span> to activate the drop-down list.
+ </div></li><li class="step"><div class="para">
+ Select the SSID you want to connect to.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Configure</strong></span> button. The editing a wireless connection window appears.
+ </div></li></ol></div><div class="figure" id="exam-Network_Connections_Window_Wireless-Tab"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-Editing_Wireless_Connection_Gnome3"><img src="images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png" alt="Editing the newly-created Wireless connection" /><div class="longdesc"><div class="para">
+ A screen shot of the NetworkManager's editing a wireless connection window. The Wireless tab has been selected on the left.
+ </div></div></div></div><h6>図6.8 Editing the newly-created Wireless connection</h6></div><br class="figure-break" /><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wireless">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>Wireless</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window. By default, wireless connections are named the same as the <em class="firstterm">SSID</em> of the wireless access point. You can rename the wireless connection without affecting its ability to connect, as in the example above, but it is recommended to retain the SSID name.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">「Connecting to a Network Automatically」</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-User_and_System_Connections">「User and System Connections」</a> for details.
+ </div></li></ul></div><h4 id="bh-Configuring_the_Wireless_Tab">Configuring the Wireless Tab</h4><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>SSID</strong></span> </span></dt><dd><div class="para">
+ All access points have a <em class="firstterm">Service Set identifier</em> to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID (and authentication secrets).
+ </div><div class="para">
+ For information on connecting to a hidden wireless network, refer to <a class="xref" href="#bh-Connecting_to_a_Hidden_Wireless_Network">6.3.2項「Connecting to a Hidden Wireless Network」</a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Mode</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Infrastructure</strong></span> — Set <span class="guilabel"><strong>Mode</strong></span> to <span class="guimenuitem"><strong>Infrastructure</strong></span> if you are connecting to a dedicated wireless access point or one built into a network device such as a router or a switch.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Ad-hoc</strong></span> — Set <span class="guilabel"><strong>Mode</strong></span> to <span class="guimenuitem"><strong>Ad-hoc</strong></span> if you are creating a peer-to-peer network for two or more mobile devices to communicate directly with each other. If you use <span class="guimenuitem"><strong>Ad-hoc</strong></span> mode, referred to as <em class="firstterm">Independent Basic Service Set</em> (<acronym class="acronym">IBSS</acronym>) in the 802.11 standard, you must ensure that the same <span class="guilabel"><strong>SSID</strong></span> is set for all participating wireless devices, and that they are all communicating over the same channel.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>BSSID</strong></span> </span></dt><dd><div class="para">
+ The Basic Service Set Identifier (BSSID) is the MAC address of the specific wireless access point you are connecting to when in <span class="guilabel"><strong>Infrastructure</strong></span> mode. This field is blank by default, and you are able to connect to a wireless access point by <span class="guilabel"><strong>SSID</strong></span> without having to specify its <span class="guilabel"><strong>BSSID</strong></span>. If the BSSID is specified, it will force the system to associate to a specific access point only.
+ </div><div class="para">
+ For ad-hoc networks, the <span class="guilabel"><strong>BSSID</strong></span> is generated randomly by the mac80211 subsystem when the ad-hoc network is created. It is not displayed by <span class="application"><strong>NetworkManager</strong></span>
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MAC address</strong></span> </span></dt><dd><div class="para">
+ Like an Ethernet Network Interface Card (NIC), a wireless adapter has a unique MAC address (Media Access Control; also known as a <em class="firstterm">hardware address</em>) that identifies it to the system. Running the <code class="command">ip addr</code> command will show the MAC address associated with each interface. For example, in the following <code class="command">ip addr</code> output, the MAC address for the <code class="computeroutput">wlan0</code> interface (which is <code class="computeroutput">00:1c:bf:02:f8:70</code>) immediately follows the <code class="computeroutput">link/ether</code> keyword:
+ </div><pre class="screen">~]# <code class="command">ip addr</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+ link/ether 52:54:00:26:9e:f1 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.251/24 brd 192.168.122.255 scope global eth0
+ inet6 fe80::5054:ff:fe26:9ef1/64 scope link
+ valid_lft forever preferred_lft forever
+3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
+ link/ether <span class="emphasis"><em>00:1c:bf:02:f8:70</em></span> brd ff:ff:ff:ff:ff:ff
+ inet 10.200.130.67/24 brd 10.200.130.255 scope global wlan0
+ inet6 fe80::21c:bfff:fe02:f870/64 scope link
+ valid_lft forever preferred_lft forever</pre><div class="para">
+ A single system could have one or more wireless network adapters connected to it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific wireless adapter with a specific connection (or connections). As mentioned, you can determine the MAC address using the <code class="command">ip addr</code> command, and then copy and paste that value into the <span class="guilabel"><strong>MAC address</strong></span> text-entry field.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ The MTU (Maximum Transmission Unit) value represents the size in bytes of the largest packet that the connection will use to transmit. If set to a non-zero number, only packets of the specified size or smaller will be transmitted. Larger packets are broken up into multiple Ethernet frames. It is recommended to leave this setting on <span class="guimenuitem"><strong>automatic</strong></span>.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-wireless">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing the wireless connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can successfully connect to your the modified connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="#sec-Connecting_to_a_Network">「Connecting to a Network」</a> for details on selecting and connecting to a network.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ security authentication for the wireless connection, click the <span class="guilabel"><strong>Wireless Security</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_Wireless_Security">「Configuring Wireless Security」</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">「Configuring IPv4 Settings」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">「Configuring IPv6 Settings」</a>.
+ </div></li></ul></div></div><div class="section" id="sec-Establishing_a_Mobile_Broadband_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.3. Establishing a Mobile Broadband Connection</h3></div></div></div><div class="para">
+ You can use <span class="application"><strong>NetworkManager</strong></span>'s mobile broadband connection abilities to connect to the following <em class="firstterm">2G</em> and <em class="firstterm">3G</em> services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 2G — <em class="firstterm">GPRS</em> (<em class="firstterm">General Packet Radio Service</em>) or <em class="firstterm">EDGE</em> (<em class="firstterm">Enhanced Data Rates for GSM Evolution</em>)
+ </div></li><li class="listitem"><div class="para">
+ 3G — <em class="firstterm">UMTS</em> (<em class="firstterm">Universal Mobile Telecommunications System</em>) or <em class="firstterm">HSPA</em> (<em class="firstterm">High Speed Packet Access</em>)
+ </div></li></ul></div><div class="para">
+ Your computer must have a mobile broadband device (modem), which the system has discovered and recognized, in order to create the connection. Such a device may be built into your computer (as is the case on many notebooks and netbooks), or may be provided separately as internal or external hardware. Examples include PC card, USB Modem or Dongle, mobile or cellular telephone capable of acting as a modem.
+ </div><div class="procedure" id="procedure-Adding_a_New_Mobile_Broadband_Connection"><h6>手順6.3 Adding a New Mobile Broadband Connection</h6><div class="para">
+ You can configure a mobile broadband connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div><ol class="1"><li class="step"><div class="para">
+ Open the Network Connections window by running, as a normal user:
+ </div><pre class="screen">~]$ <code class="command">nm-connection-editor &</code>
+</pre><div class="para">
+ The <span class="guilabel"><strong>Network Connections</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button to open the <span class="guilabel"><strong>Set up a Mobile Broadband Connection</strong></span> assistant.
+ </div></li><li class="step"><div class="para">
+ Under <span class="guilabel"><strong>Create a connection for this mobile broadband device</strong></span>, choose the 2G- or 3G-capable device you want to use with the connection. If the dropdown menu is inactive, this indicates that the system was unable to detect a device capable of mobile broadband. In this case, click <span class="guilabel"><strong>Cancel</strong></span>, ensure that you do have a mobile broadband-capable device attached and recognized by the computer and then retry this procedure. Click the <span class="guilabel"><strong>Forward</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the country where your service provider is located from the list and click the <span class="guilabel"><strong>Forward</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select your provider from the list or enter it manually. Click the <span class="guilabel"><strong>Forward</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select your payment plan from the dropdown menu and confirm the <em class="firstterm">Access Point Name</em> (<acronym class="acronym">APN</acronym>) is correct. Click the <span class="guilabel"><strong>Forward</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Apply</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Edit the mobile broadband-specific settings by referring to the <span class="emphasis"><em>Configuring the Mobile Broadband Tab</em></span> description below .
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Mobile_Broadband_Connection"><h6>手順6.4 Editing an Existing Mobile Broadband Connection</h6><div class="para">
+ Follow these steps to edit an existing mobile broadband connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Open the Network Connections window by running, as a normal user:
+ </div><pre class="screen">~]$ <code class="command">nm-connection-editor &</code>
+</pre><div class="para">
+ The <span class="guilabel"><strong>Network Connections</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Select the connection you wish to edit and click the <span class="guilabel"><strong>Edit</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">「Connecting to a Network Automatically」</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-User_and_System_Connections">「User and System Connections」</a> for details.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Edit the mobile broadband-specific settings by referring to the <span class="emphasis"><em>Configuring the Mobile Broadband Tab</em></span> description below .
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-mobile_broadband">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your mobile broadband connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="#sec-Connecting_to_a_Network">「Connecting to a Network」</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Point-to-point settings for the connection, click the <span class="guilabel"><strong>PPP Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_PPP_Point-to-Point_Settings">「Configuring PPP (Point-to-Point) Settings」</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">「Configuring IPv4 Settings」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">「Configuring IPv6 Settings」</a>.
+ </div></li></ul></div><h4 id="bh-Configuring_the_Mobile_Broadband_Tab">Configuring the Mobile Broadband Tab</h4><div class="para">
+ If you have already added a new mobile broadband connection using the assistant (refer to <a class="xref" href="#procedure-Adding_a_New_Mobile_Broadband_Connection">手順6.3「Adding a New Mobile Broadband Connection」</a> for instructions), you can edit the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab to disable roaming if home network is not available, assign a network ID, or instruct <span class="application"><strong>NetworkManager</strong></span> to prefer a certain technology (such as 3G or 2G) when using the connection.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Number</strong></span> </span></dt><dd><div class="para">
+ The number that is dialed to establish a PPP connection with the GSM-based mobile broadband network. This field may be automatically populated during the initial installation of the broadband device. You can usually leave this field blank and enter the <span class="guilabel"><strong>APN</strong></span> instead.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username used to authenticate with the network. Some providers do not provide a username, or accept any username when connecting to the network.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password used to authenticate with the network. Some providers do not provide a password, or accept any password.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>APN</strong></span> </span></dt><dd><div class="para">
+ Enter the <em class="firstterm">Access Point Name</em> (<acronym class="acronym">APN</acronym>) used to establish a connection with the GSM-based network. Entering the correct APN for a connection is important because it often determines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ how the user is billed for their network usage; and/or
+ </div></li><li class="listitem"><div class="para">
+ whether the user has access to the Internet, an intranet, or a subnetwork.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Network ID</strong></span> </span></dt><dd><div class="para">
+ Entering a <span class="guilabel"><strong>Network ID</strong></span> causes <span class="application"><strong>NetworkManager</strong></span> to force the device to register only to a specific network. This can be used to ensure the connection does not roam when it is not possible to control roaming directly.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Type</strong></span> </span></dt><dd><div class="para">
+ <span class="guilabel"><strong>Any</strong></span> — The default value of <span class="guilabel"><strong>Any</strong></span> leaves the modem to select the fastest network.
+ </div><div class="para">
+ <span class="guilabel"><strong>3G (UMTS/HSPA)</strong></span> — Force the connection to use only 3G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>2G (GPRS/EDGE)</strong></span> — Force the connection to use only 2G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 3G (UMTS/HSPA)</strong></span> — First attempt to connect using a 3G technology such as HSPA or UMTS, and fall back to GPRS or EDGE only upon failure.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 2G (GPRS/EDGE)</strong></span> — First attempt to connect using a 2G technology such as GPRS or EDGE, and fall back to HSPA or UMTS only upon failure.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow roaming if home network is not available</strong></span> </span></dt><dd><div class="para">
+ Uncheck this box if you want <span class="application"><strong>NetworkManager</strong></span> to terminate the connection rather than transition from the home network to a roaming one, thereby avoiding possible roaming charges. If the box is checked, <span class="application"><strong>NetworkManager</strong></span> will attempt to maintain a good connection by transitioning from the home network to a roaming one, and vice versa.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PIN</strong></span> </span></dt><dd><div class="para">
+ If your device's <em class="firstterm">SIM</em> (<em class="firstterm">Subscriber Identity Module</em>) is locked with a <em class="firstterm">PIN</em> (<em class="firstterm">Personal Identification Number</em>), enter the PIN so that <span class="application"><strong>NetworkManager</strong></span> can unlock the device. <span class="application"><strong>NetworkManager</strong></span> must unlock the SIM if a PIN is required in order to use the device for any purpose.
+ </div></dd></dl></div></div><div class="section" id="sec-Establishing_a_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.4. Establishing a VPN Connection</h3></div></div></div><div class="para">
+ Establishing an encrypted Virtual Private Network (VPN) enables you to communicate securely between your Local Area Network (LAN), and another, remote LAN. After successfully establishing a VPN connection, a VPN router or gateway performs the following actions upon the packets you transmit:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ it adds an <em class="firstterm">Authentication Header</em> for routing and authentication purposes;
+ </div></li><li class="listitem"><div class="para">
+ it encrypts the packet data; and,
+ </div></li><li class="listitem"><div class="para">
+ it encloses the data with an Encapsulating Security Payload (ESP), which constitutes the decryption and handling instructions.
+ </div></li></ol></div><div class="para">
+ The receiving VPN router strips the header information, decrypts the data, and routes it to its intended destination (either a workstation or other node on a network). Using a network-to-network connection, the receiving node on the local network receives the packets already decrypted and ready for processing. The encryption/decryption process in a network-to-network VPN connection is therefore transparent to clients.
+ </div><div class="para">
+ Because they employ several layers of authentication and encryption, VPNs are a secure and effective means of connecting multiple remote nodes to act as a unified intranet.
+ </div><div class="procedure" id="procedure-Adding_a_New_VPN_Connection"><h6>手順6.5 Adding a New VPN Connection</h6><ol class="1"><li class="step"><div class="para">
+ You can configure a new VPN connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the <span class="guilabel"><strong>VPN</strong></span> menu entry.
+ </div></li><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area. Clicking on the <span class="guilabel"><strong>Network Settings</strong></span> menu entry opens the <span class="guilabel"><strong>Network</strong></span> window, from where you can view some basic network configuration information and initiate configuration tasks.
+ </div></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>VPN</strong></span> menu entry followed by <span class="guilabel"><strong>Configure</strong></span> and proceed to <a class="xref" href="#sec-Establishing_a_VPN_Connection">「Establishing a VPN Connection」</a>. If there is no VPN menu entry click on the plus sign at the bottom. A dialog box appears. Ensure the interface is set to VPN.
+ </div><div class="note" id="note-VPN-plug-in-is-required"><div class="admonition_header"><h2>A VPN plug-in is required</h2></div><div class="admonition"><div class="para">
+ The appropriate NetworkManager VPN plug-in for the VPN type you want to configure must be installed. (refer to <a class="xref" href="#sec-Installing">「パッケージのインストール」</a> for more information on how to install new packages in Fedora 17).
+ </div></div></div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Create</strong></span> button to open the <span class="guilabel"><strong>Choose a VPN Connection Type</strong></span> assistant.
+ </div></li><li class="step" id="Network_Configuration-VPN-step2"><div class="para">
+ Select the VPN protocol for the gateway you are connecting to from the dropdown menu. The VPN protocols available for selection in the dropdown menu corresponds to the NetworkManager VPN plug-ins installed. For example, if the <span class="package">NetworkManager VPN plug-in for openswan</span>is installed then the IPsec based VPN will be selectable from the dropdown menu.
+ </div><div class="para">
+ After selecting the correct one, press the <span class="guibutton"><strong>Create...</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Editing VPN Connection <em class="replaceable"><code>1</code></em> </strong></span> window then appears. This window presents settings customized for the type of VPN connection you selected in <a class="xref" href="#Network_Configuration-VPN-step2">ステップ 5</a>.
+ </div></li></ol></div><div class="procedure"><div class="para">
+ You can configure an existing VPN connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the <span class="guilabel"><strong>VPN</strong></span> menu entry.
+ </div><ol class="1"><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Network Settings</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>VPN</strong></span> menu entry.
+ </div></li><li class="step"><div class="para">
+ Select the connection you wish to edit and click the <span class="guilabel"><strong>Configure</strong></span> button.
+ </div></li></ol></div><div class="figure" id="exam-Editing-VPN-connection"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_Editing-VPN-connection-1_Gnome3"><img src="images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png" alt="Editing the newly-created VPN connection 1." /><div class="longdesc"><div class="para">
+ A screenshot of the Editing VPN connection 1 window. The VPN tab is on the left and in the foreground
+ </div></div></div></div><h6>図6.9 Editing the newly-created VPN connection 1.</h6></div><br class="figure-break" /><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-vpn">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>VPN</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">「Connecting to a Network Automatically」</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-User_and_System_Connections">「User and System Connections」</a> for details.
+ </div></li></ul></div><h4 id="bh-Configuring_the_VPN_Tab">Configuring the VPN Tab</h4><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Gateway</strong></span> </span></dt><dd><div class="para">
+ The name or IP address of the remote VPN gateway.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Group name</strong></span> </span></dt><dd><div class="para">
+ The name of a VPN group configured on the remote gateway.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User password</strong></span> </span></dt><dd><div class="para">
+ If required, enter the password used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Group password</strong></span> </span></dt><dd><div class="para">
+ If required, enter the password used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User name</strong></span> </span></dt><dd><div class="para">
+ If required, enter the username used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Phase1 Algorithms</strong></span> </span></dt><dd><div class="para">
+ If required, enter the algorithms to be used to authenticate and set up an encrypted channel.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Phase2 Algorithms</strong></span> </span></dt><dd><div class="para">
+ If required, enter the algorithms to be used for the IPsec negotiations.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Domain</strong></span> </span></dt><dd><div class="para">
+ If required, enter the Domain Name.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>NAT traversal</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Cisco UDP (default)</strong></span> — IPsec over UDP.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>NAT-T</strong></span> — ESP encapsulation and IKE extensions are used to handle NAT Traversal.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Disabled</strong></span> — No special NAT measures required.
+ </div><div class="para">
+ <span class="guilabel"><strong>Disable Dead Peer Detection</strong></span> — Disable the sending of probes to the remote gateway or endpoint.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-vpn">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your new VPN connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="#sec-Connecting_to_a_Network">「Connecting to a Network」</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">「Configuring IPv4 Settings」</a>.
+ </div></li></ul></div></div><div class="section" id="sec-Establishing_a_DSL_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.5. Establishing a DSL Connection</h3></div></div></div><div class="para">
+ Open the Network Connections window by running, as a normal user:
+ </div><pre class="screen">~]$ <code class="command">nm-connection-editor &</code>
+</pre><div class="para">
+ Select the DSL tab and click <span class="guibutton"><strong>Add</strong></span>.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username used to authenticate with the service provider.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Service</strong></span> </span></dt><dd><div class="para">
+ Leave blank unless otherwise directed.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password supplied by the service provider.
+ </div></dd></dl></div></div><div class="section" id="sec-Establishing_Routes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.6. Establishing Routes</h3></div></div></div><div class="figure" id="exam-User_and_System_Connections_Static-Routes"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-System_eth0-Routes"><img src="images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png" alt="Configuring static network routes" /><div class="longdesc"><div class="para">
+ A screen shot of the static routes window
+ </div></div></div></div><h6>図6.10 Configuring static network routes</h6></div><br class="figure-break" /><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Address</strong></span> — The IP address of a network, sub-net or host.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Netmask</strong></span> — The netmask or prefix length of the IP address just entered.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Gateway</strong></span> — The IP address of the gateway leading to the network, sub-net or host.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Metric</strong></span> — A network cost, that is to say a preference value to give to this route. Lower values will be preferred over higher values.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Ignore automatically obtained routes</strong></span> </span></dt><dd><div class="para">
+ Select this check box to only use manually entered routes for the VPN tunnel.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use this connection only for resources on its network</strong></span> </span></dt><dd><div class="para">
+ Select this checkbox to prevent the VPN from becoming the default route. Then only the specific routes sent by the VPN server (or routes entered here manually) will be routed over the VPN tunnel.
+ </div></dd></dl></div></div></div><div class="section" id="sec-Configuring_Connection_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Configuring Connection Settings</h2></div></div></div><div class="section" id="sec-Configuring_802.1x_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.1. Configuring 802.1x Security</h3></div></div></div><div class="para">
+ 802.1x security is the name of the IEEE standard for port-based Network Access Control (PNAC). Simply put, 802.1x security is a way of defining a <em class="firstterm">logical network</em> out of a physical one. All clients who want to join the logical network must authenticate with the server (a router, for example) using the correct 802.1x authentication method.
+ </div><div class="para">
+ 802.1x security is most often associated with securing wireless networks (WLANs), but can also be used to prevent intruders with physical access to the network (LAN) from gaining entry. In the past, DHCP servers were configured not to lease IP addresses to unauthorized users, but for various reasons this practice is both impractical and insecure, and thus is no longer recommended. Instead, 802.1x security is used to ensure a logically-secure network through port-based authentication.
+ </div><div class="para">
+ 802.1x provides a framework for WLAN and LAN access control and serves as an envelope for carrying one of the Extensible Authentication Protocol (EAP) types. An EAP type is a protocol that defines how WLAN security is achieved on the network.
+ </div><div class="para">
+ You can configure 802.1x security for a wired or wireless connection type by opening the <span class="guilabel"><strong>Network Connections</strong></span> window (refer to <a class="xref" href="#sec-Configuring_New_and_Editing_Existing_Connections">「Configuring New and Editing Existing Connections」</a>) and following the applicable procedure:
+ </div><div class="procedure" id="procedure-For_a_wired_connection..."><h6>手順6.6 For a wired connection...</h6><ol class="1"><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Wired</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Either click on <span class="guibutton"><strong>Add</strong></span> to add a new network connection for which you want to configure 802.1x security, or select an existing connection and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Then select the <span class="guilabel"><strong>802.1x Security</strong></span> tab and check the <span class="guilabel"><strong>Use 802.1x security for this connection</strong></span> checkbox to enable settings configuration.
+ </div></li><li class="step"><div class="para">
+ Proceed to <a class="xref" href="#sec-Configuring_TLS_Transport_Layer_Security_Settings">「Configuring TLS (Transport Layer Security) Settings」</a>
+ </div></li></ol></div><div class="procedure" id="procedure-For_a_wireless_connection..."><h6>手順6.7 For a wireless connection...</h6><ol class="1"><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Wireless</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Either click on <span class="guibutton"><strong>Add</strong></span> to add a new network connection for which you want to configure 802.1x security, or select an existing connection and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Then click the <span class="guilabel"><strong>Security</strong></span> dropdown and choose one of the following security methods: <span class="guimenuitem"><strong>LEAP</strong></span>, <span class="guimenuitem"><strong>Dynamic WEP (802.1x)</strong></span>, or <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Refer to <a class="xref" href="#sec-Configuring_TLS_Transport_Layer_Security_Settings">「Configuring TLS (Transport Layer Security) Settings」</a> for descriptions of which EAP types correspond to your selection in the <span class="guilabel"><strong>Security</strong></span> dropdown.
+ </div></li></ol></div><div class="section" id="sec-Configuring_TLS_Transport_Layer_Security_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">6.4.1.1. Configuring TLS (Transport Layer Security) Settings</h4></div></div></div><div class="para">
+ With Transport Layer Security, the client and server mutually authenticate using the TLS protocol. The server demonstrates that it holds a digital certificate, the client proves its own identity using its client-side certificate, and key information is exchanged. Once authentication is complete, the TLS tunnel is no longer used. Instead, the client and server use the exchanged keys to encrypt data using AES, TKIP or WEP.
+ </div><div class="para">
+ The fact that certificates must be distributed to all clients who want to authenticate means that the EAP-TLS authentication method is very strong, but also more complicated to set up. Using TLS security requires the overhead of a public key infrastructure (PKI) to manage certificates. The benefit of using TLS security is that a compromised password does not allow access to the (W)LAN: an intruder must also have access to the authenticating client's private key.
+ </div><div class="para">
+ Network Manger does not determine the version of TLS supported. Network Manager gathers the parameters entered by the user and passes them to the daemon, wpa_supplicant, that handles the procedure. It, in turn, uses OpenSSL to establish the TLS tunnel. OpenSSL itself negotiates the SSL/TLS protocol version. It uses the highest version both ends support.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Identity</strong></span> </span></dt><dd><div class="para">
+ Identity string for EAP authentication methods, such as a username or login name.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a user's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Private key</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a user's private key file.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Private key password</strong></span> </span></dt><dd><div class="para">
+ Enter the user password corresponding to the user's private key.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_Tunneled_TLS_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">6.4.1.2. Configuring Tunneled TLS Settings</h4></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous identity</strong></span> </span></dt><dd><div class="para">
+ This value is used as the unencrypted identity.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>PAP</strong></span> — Password Authentication Protocol.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAP</strong></span> — Challenge Handshake Authentication Protocol.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>CHAP</strong></span> — Challenge Handshake Authentication Protocol.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_Protected_EAP_PEAP_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">6.4.1.3. Configuring Protected EAP (PEAP) Settings</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous Identity</strong></span> </span></dt><dd><div class="para">
+ This value is used as the unencrypted identity.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PEAP version</strong></span> </span></dt><dd><div class="para">
+ The version of Protected EAP to use. Automatic, 0 or 1.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MD5</strong></span> — Message Digest 5, a cryptographic hash function.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>GTC</strong></span> — Generic Token Card.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div></div><div class="section" id="sec-Configuring_Wireless_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.2. Configuring Wireless Security</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Security</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>None</strong></span> — Do not encrypt the Wi-Fi connection.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 40/128-bit Key</strong></span> — Wired Equivalent Privacy (WEP), from the IEEE 802.11 standard. Uses a single pre-shared key (PSK).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 128-bit Passphrase</strong></span> — An MD5 hash of the passphrase will be used to derive a WEP key.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>LEAP</strong></span> — Lightweight Extensible Authentication Protocol, from Cisco Systems.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Dynamic WEP (802.1x)</strong></span> — WEP keys are changed dynamically.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Personal</strong></span> — Wi-Fi Protected Access (WPA), from the draft IEEE 802.11i standard. A replacement for WEP. Wi-Fi Protected Access II (WPA2), from the 802.11i-2004 standard. Personal mode uses a pre-shared key (WPA-PSK).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span> — WPA for use with a RADUIS authentication server to provide IEEE 802.1x network access control.
+ </div></dd><dt class="varlistentry"><span class="term">Password</span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_PPP_Point-to-Point_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.3. Configuring PPP (Point-to-Point) Settings</h3></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Configure Methods</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use point-to-point encryption (MPPE)</strong></span> </span></dt><dd><div class="para">
+ Microsoft Point-To-Point Encryption protocol (RFC 3078).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow BSD data compression</strong></span> </span></dt><dd><div class="para">
+ PPP BSD Compression Protocol (RFC 1977).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow Deflate data compression</strong></span> </span></dt><dd><div class="para">
+ PPP Deflate Protocol (RFC 1979).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use TCP header compression</strong></span> </span></dt><dd><div class="para">
+ Compressing TCP/IP Headers for Low-Speed Serial Links (RFC 1144).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Send PPP echo packets</strong></span> </span></dt><dd><div class="para">
+ LCP Echo-Request and Echo-Reply Codes for loopback tests (RFC 1661).
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_IPv4_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.4. Configuring IPv4 Settings</h3></div></div></div><div class="figure" id="exam-Configuring_IPv4_Settings"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-IPv4_Settings"><img src="images/Network_Configuration-NM-IPv4_Settings_Gnome3.png" alt="Editing the IPv4 Settings Tab" /><div class="longdesc"><div class="para">
+ A screen shot of NetworkManager's IPv4 Settings Tab
+ </div></div></div></div><h6>図6.11 Editing the IPv4 Settings Tab</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab allows you to configure the method by which you connect to the Internet and enter IP address, route, and DNS information as required. The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab is available when you create and modify one of the following connection types: wired, wireless, mobile broadband, VPN or DSL.
+ </div><div class="para">
+ If you are using DHCP to obtain a dynamic IP address from a DHCP server, you can simply set <span class="guilabel"><strong>Method</strong></span> to <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span>.
+ </div><h4 id="bh-Setting_the_Method">Setting the Method</h4><div class="variablelist" id="varlist-Available_IPv4_Methods_by_Connection_Type"><h6>Available IPv4 Methods by Connection Type</h6><div class="para">
+ When you click the <span class="guilabel"><strong>Method</strong></span> dropdown menu, depending on the type of connection you are configuring, you are able to select one of the following IPv4 connection methods. All of the methods are listed here according to which connection type or types they are associated with.
+ </div><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses. You do not need to fill in the <span class="guilabel"><strong>DHCP client ID</strong></span> field.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP) addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> — Choose this option if the network you are connecting to does not have a DHCP server and you do not want to assign IP addresses manually. Random addresses will be selected as per RFC 3927.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> — Choose this option if the interface you are configuring is for sharing an Internet or WAN connection.
+ </div></dd><dt class="varlistentry"><span class="term">Wired, Wireless and DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> — Choose this option if the network you are connecting to does not have a DHCP server and you want to assign IP addresses manually.
+ </div></dd><dt class="varlistentry"><span class="term">Mobile Broadband Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP) addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div></dd><dt class="varlistentry"><span class="term">VPN Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN) addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div></dd><dt class="varlistentry"><span class="term">DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE) addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_IPv6_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.5. Configuring IPv6 Settings</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Ignore</strong></span> — Choose this option if you want to disable IPv6 settings.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic, addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> — Choose this option if the network you are connecting to does not have a DHCP server and you want to assign IP addresses manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> — Choose this option if the network you are connecting to does not have a DHCP server and you do not want to assign IP addresses manually. Random addresses will be selected as per RFC 4862.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> — Choose this option if the interface you are configuring is for sharing an Internet or WAN connection.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>DNS servers</strong></span> — Enter a comma separated list of DNS servers.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Search domains</strong></span> — Enter a comma separated list of domain controllers.
+ </div></dd></dl></div></div></div><div class="section" id="sec-NetworkManager_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.5. NetworkManager Architecture</h2></div></div></div><div class="para">
+ See <a href="http://live.gnome.org/NetworkManagerConfiguration">http://live.gnome.org/NetworkManagerConfiguration</a>
+ </div></div></div><div xml:lang="ja-JP" class="chapter" id="ch-Network_Interfaces" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第7章 ネットワーク・インターフェース</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-networkscripts-files">7.1. ネットワーク設定ファイル</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-interfaces">7.2. インターフェース設定ファイル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-networkscripts-interfaces-eth0">7.2.1. イーサネット インターフェース</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-chan">7.2.2. チャンネル・ボンディング・インターフェース</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces_network-bridge">7.2.3. ネットワークブリッジ</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interf
aces_802.1q-vlan-tagging">7.2.4. Setting up 802.1q VLAN tagging</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-alias">7.2.5. エイリアス ファイルとクローン ファイル</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-ppp0">7.2.6. ダイヤルアップ インターフェース</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-other">7.2.7. 他のインターフェース</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-networkscripts-control">7.3. インターフェース制御スクリプト</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-static-routes">7.4. スタティック ルートの設定</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-functions">7.5. ネットワーク機能ファイル</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-resources">7.6. その他のリソース</a></span><
/dt><dd><dl><dt><span class="section"><a href="#s2-networkscripts-docs-inst">7.6.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a id="idm119046288" class="indexterm"></a><a id="idm109768240" class="indexterm"></a><div class="para">
+ Fedora においては、すべてのネットワーク通信はシステムに接続された設定済みソフトウェア<em class="firstterm">インターフェース</em>と<em class="firstterm">物理ネットワークデバイス</em>の間で発生します。
+ </div><div class="para">
+ The configuration files for network interfaces are located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. The scripts used to activate and deactivate these network interfaces are also located here. Although the number and type of interface files can differ from system to system, there are three categories of files that exist in this directory:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <em class="firstterm">インターフェースの設定ファイル</em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">インターフェースの制御スクリプト</em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">ネットワークの関数ファイル</em>
+ </div></li></ol></div><div class="para">
+ これらの各カテゴリーのファイルは、合同で機能し各種ネットワークデバイスを動作させます。
+ </div><div class="para">
+ この章では、これらファイル間の関係とファイルの使用方法について説明していきます。
+ </div><div class="section" id="s1-networkscripts-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. ネットワーク設定ファイル</h2></div></div></div><a id="idm125474368" class="indexterm"></a><div class="para">
+ インターフェース設定ファイルを調べる前に、まずネットワーク設定において使用される主要な設定ファイルを項目別にあげましょう。Fedora システムをカスタマイズするときに役に立つネットワークスタックをセットアップすることに役立ちます。
+ </div><div class="para">
+ 主要なネットワーク設定ファイルは、次のようになります：
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/etc/hosts</code></span></dt><dd><div class="para">
+ The main purpose of this file is to resolve hostnames that cannot be resolved any other way. It can also be used to resolve hostnames on small networks with no DNS server. Regardless of the type of network the computer is on, this file should contain a line specifying the IP address of the loopback device (<code class="systemitem">127.0.0.1</code>) as <code class="systemitem">localhost.localdomain</code>. For more information, refer to the <span class="bold bold"><strong>hosts</strong></span>(5) manual page.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/etc/resolv.conf</code></span></dt><dd><div class="para">
+ This file specifies the IP addresses of DNS servers and the search domain. Unless configured to do otherwise, the network initialization scripts populate this file. For more information about this file, refer to the <span class="bold bold"><strong>resolv.conf</strong></span>(5) manual page.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/etc/sysconfig/network</code></span></dt><dd><div class="para">
+ このファイルはすべてのネットワークインターフェースに対するルーティングとホスト情報を指定します。このファイルと利用可能なディレクティブの詳細は、<a class="xref" href="#s2-sysconfig-network">「/etc/sysconfig/network」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>interface-name</code></em> </code></span></dt><dd><div class="para">
+ 各ネットワークインターフェースに対して、対応するインターフェース設定ファイルがあります。これらのファイルはそれぞれ、特定のネットワークインターフェースに固有の情報を提供します。この種のファイルと利用可能なディレクティブに関する詳細は<a class="xref" href="#s1-networkscripts-interfaces">「インターフェース設定ファイル」</a>を参照してください。
+ </div></dd></dl></div><div class="important"><div class="admonition_header"><h2>ネットワークインターフェース名</h2></div><div class="admonition"><div class="para">
+ ネットワークインターフェース名は異なるハードウェア種別において異なるかもしれません。詳細は<a class="xref" href="#appe-Consistent_Network_Device_Naming">付録A <em>Consistent Network Device Naming</em></a>を参照してください。
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>/etc/sysconfig/networking/ ディレクトリ</h2></div><div class="admonition"><div class="para">
+ The <code class="filename">/etc/sysconfig/networking/</code> directory is used by the now deprecated <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>). Its contents should <span class="strong strong"><strong>not</strong></span> be edited manually. Using only one method for network configuration is strongly encouraged, due to the risk of configuration deletion. For more information about configuring network interfaces using graphical configuration tools, refer to <a class="xref" href="#ch-NetworkManager">6章<em>NetworkManager</em></a>.
+ </div></div></div></div><div class="section" id="s1-networkscripts-interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.2. インターフェース設定ファイル</h2></div></div></div><a id="idm111557760" class="indexterm"></a><a id="idm130676000" class="indexterm"></a><div class="para">
+ インターフェース設定ファイルは、それぞれのネットワークデバイスに対するソフトウェアインターフェースを制御します。システムが起動するとき、どのインターフェースを起動して、それらをどのように設定するのかを決めるために、これらのファイルを使用します。これらのファイルは通常 <code class="filename">ifcfg-<em class="replaceable"><code>name</code></em></code> という名前です、ここで <em class="replaceable"><code>name</code></em> は設定ファイルが制御するデバイスの名前を参照します。
+ </div><div class="section" id="s2-networkscripts-interfaces-eth0"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. イーサネット インターフェース</h3></div></div></div><a id="idm137592272" class="indexterm"></a><a id="idm135181712" class="indexterm"></a><div class="para">
+ One of the most common interface files is <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code>, which controls the first Ethernet <em class="firstterm">network interface card</em> or <acronym class="acronym">NIC</acronym> in the system. In a system with multiple NICs, there are multiple <code class="filename">ifcfg-eth<em class="replaceable"><code>X</code></em></code> files (where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface). Because each device has its own configuration file, an administrator can control how each interface functions individually.
+ </div><div class="para">
+ 下記は固定 IP アドレスを用いたシステム向けの <code class="filename">ifcfg-eth0</code> のサンプルです。
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=none
+ONBOOT=yes
+NETMASK=255.255.255.0
+IPADDR=10.0.1.27
+USERCTL=no</pre><div class="para">
+ インターフェース設定ファイルにおいて必要とされる値は他の値に基づいて変更できます。たとえば、DHCP を使用しているインターフェースの <code class="filename">ifcfg-eth0</code> ファイルは、IP 情報が DHCP サーバーにより提供されるので、異なって見えます:
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> is graphical configuration tool which provides an easy way to make changes to the various network interface configuration files (refer to <a class="xref" href="#ch-NetworkManager">6章<em>NetworkManager</em></a> for detailed instructions on using this tool).
+ </div><div class="para">
+ 但し、任意のネットワーク インターフェースの設定ファイルは、手動で編集することもできます。
+ </div><div class="para">
+ 以下にイーサネット インターフェースの設定ファイル内の設定パラメーターを一覧で示します。
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">BONDING_OPTS</code>=<em class="replaceable"><code>parameters</code></em></span></dt><dd><div class="para">
+ sets the configuration parameters for the bonding device, and is used in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code>N</code></em></code> (see <a class="xref" href="#s2-networkscripts-interfaces-chan">「チャンネル・ボンディング・インターフェース」</a>). These parameters are identical to those used for bonding devices in <code class="filename">/sys/class/net/<em class="replaceable"><code>bonding_device</code></em>/bonding</code>, and the module parameters for the bonding driver as described in <span class="emphasis"><em><code class="filename">bonding</code> Module Directives</em></span>.
+ </div><div class="para">
+ This configuration method is used so that multiple bonding devices can have different configurations. It is highly recommended to place all of your bonding options after the <code class="option">BONDING_OPTS</code> directive in <code class="filename">ifcfg-<em class="replaceable"><code>name</code></em></code>. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">BOOTPROTO</code>=<em class="replaceable"><code>protocol</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>protocol</code></em> は次のどれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">none</code> — ブートプロトコルを使用しません。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">bootp</code> — BOOTP プロトコルが使用されます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">dhcp</code> — DHCP プロトコルが使用されます。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">BROADCAST</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> はブロードキャストアドレスです。この値は <code class="command">ipcalc</code> を用いて自動的に計算されるので、このディレクティブは推奨されません。
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">DEVICE</code>=<em class="replaceable"><code>name</code></em> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code>name</code></em> is the name of the physical device (except for dynamically-allocated PPP devices where it is the <span class="emphasis"><em>logical name</em></span>).
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">DHCP_HOSTNAME</code>=<em class="replaceable"><code>name</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>name</code></em> は DHCP サーバーに送信される短縮ホスト名です。DHCP サーバーがクライアントに IP アドレスを受信する前にホスト名を指定するよう要求するときのみ、このオプションを使用してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">DNS<em class="replaceable"><code>{1,2}</code></em></code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>address</code></em> is a name server address to be placed in <code class="filename">/etc/resolv.conf</code> if the <code class="option">PEERDNS</code> directive is set to <code class="literal">yes</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">ETHTOOL_OPTS</code>=<em class="replaceable"><code>options</code></em> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code>options</code></em> are any device-specific options supported by <code class="command">ethtool</code>. For example, if you wanted to force 100Mb, full duplex:
+ </div><pre class="programlisting">ETHTOOL_OPTS="autoneg off speed 100 duplex full"</pre><div class="para">
+ Instead of a custom initscript, use <code class="option">ETHTOOL_OPTS</code> to set the interface speed and duplex settings. Custom initscripts run outside of the network init script lead to unpredictable results during a post-boot network service restart.
+ </div><div class="important"><div class="admonition_header"><h2>Set <span class="quote">「<span class="quote">autoneg off</span>」</span> before changing speed or duplex settings</h2></div><div class="admonition"><div class="para">
+ Changing speed or duplex settings almost always requires disabling autonegotiation with the <code class="option">autoneg off</code> option. This option needs to be stated first, as the option entries are order-dependent.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"><code class="option">GATEWAY</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> はネットワークのルーターまたはゲートウェイデバイスの IP アドレスです（あれば）。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">HOTPLUG</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このデバイスはホットプラグされたときに有効化されます (これが初期状態です)。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — このデバイスがホットプラグされたときに有効化<span class="emphasis"><em>されません</em></span>。
+ </div></li></ul></div><div class="para">
+ <code class="option">HOTPLUG=no</code> オプションは、bonding カーネルモジュールが読み込まれているときに、チャネルボンディングインターフェースが有効化するのを防げます。
+ </div><div class="para">
+ ボンディング・インターフェースの詳細は<a class="xref" href="#s2-networkscripts-interfaces-chan">「チャンネル・ボンディング・インターフェース」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">HWADDR</code>=<em class="replaceable"><code>MAC-address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>MAC-address</code></em> は <em class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em> の形式であるイーサネットデバイスのハードウェアアドレスです。このディレクティブは、インターフェースが各 NIC モジュールに対して設定された読み込み順序にかかわりなく正しいデバイス名を確実に割り当てるために、複数の NIC を持つマシンにおいて使用する必要があります。このディレクティブは <code class="option">MACADDR</code> と同時に使用<span class="strong strong"><strong>できません</strong></span>。
+ </div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ 永続的なデバイス名は <code class="filename">/etc/udev/rules.d/70-persistent-net.rules</code> により処理されています。
+ </div></div></div></dd><dt class="varlistentry"><span class="term"><code class="option">IPADDR</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> は IP アドレスです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">LINKDELAY</code>=<em class="replaceable"><code>time</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>time</code></em> は、デバイスを設定する前にリンクネゴシエーションを待つ秒数です。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">MACADDR</code>=<em class="replaceable"><code>MAC-address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>MAC-address</code></em> は <em class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em> の形式であるイーサネットデバイスのハードウェアアドレスです。
+ </div><div class="para">
+ このディレクティブは、物理 NIC に割り当てられた MAC アドレスを上書きして、インターフェースに MAC アドレスを割り当てるために使用されます。このディレクティブは <code class="option">HWADDR</code> ディレクティブと一緒に使用<span class="strong strong"><strong>できません</strong></span>。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">MASTER</code>=<em class="replaceable"><code>bond-interface</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>bond-interface</code></em> は、イーサネットインターフェースが連結されたチャネルボンディングインターフェースです。
+ </div><div class="para">
+ このディレクティブは <code class="option">SLAVE</code> ディレクティブと一緒に使用されます。
+ </div><div class="para">
+ ボンディング・インターフェースの詳細は<a class="xref" href="#s2-networkscripts-interfaces-chan">「チャンネル・ボンディング・インターフェース」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">NETMASK</code>=<em class="replaceable"><code>mask</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>mask</code></em> はネットマスクの値です。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">NETWORK</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> はネットワークアドレスです。この値は <code class="command">ipcalc</code> を用いて自動的に計算されるので、このディレクティブは推奨されません。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">NM_CONTROLLED</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — NetworkManager がこのデバイスを設定することを許可します。これは初期状態の動作のため、省略できます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — NetworkManager がこのデバイスを設定することを許可しません。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">ONBOOT</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このデバイスが起動時に有効化されます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — このデバイスが起動時に有効化されません。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">PEERDNS</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — DNS ディレクティブが設定されていると、<code class="filename">/etc/resolv.conf</code> を変更します。DHCP を使用していると、<code class="literal">yes</code> が初期値です。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — <code class="filename">/etc/resolv.conf</code> を変更しません。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">SLAVE</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このデバイスは <code class="option">MASTER</code> ディレクティブにおいて指定されたチャネルボンディングインターフェースにより制御されます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — このデバイスは <code class="option">MASTER</code> ディレクティブにおいて指定されたチャネルボンディングインターフェースにより制御<span class="emphasis"><em>されません</em></span>。
+ </div></li></ul></div><div class="para">
+ このディレクティブは <code class="option">MASTER</code> ディレクティブと同時に使用されません。
+ </div><div class="para">
+ チャネル・ボンディング・インターフェースの詳細は<a class="xref" href="#s2-networkscripts-interfaces-chan">「チャンネル・ボンディング・インターフェース」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">SRCADDR</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> は出力パケットに対して指定されるソース IP アドレスです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">USERCTL</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — 非 <code class="systemitem">root</code> ユーザーがこのデバイスを制御できます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — 非 <code class="systemitem">root</code> ユーザーがこのデバイスを制御できません。
+ </div></li></ul></div></dd></dl></div></div><div class="section" id="s2-networkscripts-interfaces-chan"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. チャンネル・ボンディング・インターフェース</h3></div></div></div><a id="idm121406528" class="indexterm"></a><a id="idm69194496" class="indexterm"></a><div class="para">
+ Fedora は管理者が <code class="filename">bonding</code> カーネルモジュールおよび<em class="firstterm">チャネルボンディングインターフェース</em>と呼ばれる特別なネットワークインターフェースを使用して単一チャネルの中に複数のネットワークインターフェースを一緒にバインドできます。チャネルボンディングは、同時に帯域を増加させて冗長性を提供する、2つ以上のネットワークインターフェースを1つとして動作させることができます。
+ </div><div class="para">
+ To create a channel bonding interface, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file can be identical to whatever type of interface is getting bonded, such as an Ethernet interface. The only difference is that the <code class="option">DEVICE</code> directive is <code class="option">bond<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface.
+ </div><div class="para">
+ 以下は、チャンネル ボンディング設定ファイルの例です。
+ </div><div class="example" id="ex-Sample_ifcfg-bond0_interface_configuration_file"><h6>例7.1 ifcfg-bond0 インターフェース設定ファイルの例</h6><div class="example-contents"><pre class="programlisting">DEVICE=bond0
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+ONBOOT=yes
+BOOTPROTO=none
+USERCTL=no
+BONDING_OPTS="<em class="replaceable"><code>スペースで区切ってボンディングのパラメーター</code></em>"</pre></div></div><br class="example-break" /><div class="para">
+ After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the <code class="option">MASTER</code> and <code class="option">SLAVE</code> directives to their configuration files. The configuration files for each of the channel-bonded interfaces can be nearly identical.
+ </div><div class="para">
+ For example, if two Ethernet interfaces are being channel bonded, both <code class="systemitem">eth0</code> and <code class="systemitem">eth1</code> may look like the following example:
+ </div><pre class="programlisting">DEVICE=eth<em class="replaceable"><code>N</code></em>
+BOOTPROTO=none
+ONBOOT=yes
+MASTER=bond0
+SLAVE=yes
+USERCTL=no</pre><div class="para">
+ この例では、<em class="replaceable"><code>N</code></em> をインターフェースの数値に置き換えます。
+ </div><div class="para">
+ For a channel bonding interface to be valid, the kernel module must be loaded. To ensure that the module is loaded when the channel bonding interface is brought up, create a new file as root named <code class="filename"><em class="replaceable"><code>bonding</code></em>.conf</code> in the <code class="filename">/etc/modprobe.d/</code> directory. Note that you can name this file anything you like as long as it ends with a <code class="filename">.conf</code> extension. Insert the following line in this new file:
+ </div><pre class="programlisting">alias bond<em class="replaceable"><code>N</code></em> bonding</pre><div class="para">
+ Replace <em class="replaceable"><code>N</code></em> with the interface number, such as <code class="literal">0</code>. For each configured channel bonding interface, there must be a corresponding entry in your new <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code> file.
+ </div><div class="important"><div class="admonition_header"><h2>ifcfg-bondN ファイルにすべてのボンディングモジュールパラメーターを書きます</h2></div><div class="admonition"><div class="para">
+ Parameters for the bonding kernel module must be specified as a space-separated list in the <code class="option">BONDING_OPTS="<em class="replaceable"><code>bonding parameters</code></em>"</code> directive in the <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code> interface file. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file. For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to <a class="xref" href="#sec-Using_Channel_Bonding">「Using Channel Bonding」</a>.
+ </div></div></div></div><div class="section" id="s2-networkscripts-interfaces_network-bridge"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. ネットワークブリッジ</h3></div></div></div><a id="idm106280400" class="indexterm"></a><div class="para">
+ A network bridge is a Link Layer device which forwards traffic between networks based on MAC addresses and is therefore also referred to as a Layer 2 device. It makes forwarding decisions based on tables of MAC addresses which it builds by learning what hosts are connected to each network. A software bridge can be used within a Linux host in order to emulate a hardware bridge, for example in virtualization applications for sharing a NIC with one or more virtual NICs. This case will be illustrated here as an example.
+ </div><div class="para">
+ To create a network bridge, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-br<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file is similar to whatever type of interface is getting bridged to, such as an Ethernet interface. The differences in this example are as follows:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="option">DEVICE</code> directive is given an interface name as its argument in the format <code class="option">br<em class="replaceable"><code>N</code></em></code>, where <em class="replaceable"><code>N</code></em> is replaced with the number of the interface.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">TYPE</code> directive is given an argument <code class="option">Bridge</code> or <code class="option">Ethernet</code>. This directive determines the device type and the argument is case sensitive.
+ </div></li><li class="listitem"><div class="para">
+ The bridge interface configuration file now has the IP address and the physical interface has only a MAC address.
+ </div></li><li class="listitem"><div class="para">
+ An extra directive, <code class="option">DELAY=0</code>, is added to prevent the bridge from waiting while it monitors traffic, learns where hosts are located, and builds a table of MAC addresses on which to base its filtering decisions. The default delay of 30 seconds is not needed if no routing loops are possible.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">NM_CONTROLLED=no</code> should be added to the Ethernet interface to prevent <span class="application"><strong>NetworkManager</strong></span> from altering the file. It can also be added to the bridge configuration file in case future versions of <span class="application"><strong>NetworkManager</strong></span> support bridge configuration.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The following is a sample bridge interface configuration file using a static IP address:
+ </div><div class="example" id="ex-Sample_ifcfg-br0_interface_configuration_file"><h6>例7.2 ifcfg-br0 インターフェース設定ファイルの例</h6><div class="example-contents"><pre class="programlisting">DEVICE=br0
+TYPE=Bridge
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+ONBOOT=yes
+BOOTPROTO=static
+NM_CONTROLLED=no
+DELAY=0</pre></div></div><br class="example-break" /><div class="para">
+ To complete the bridge another interface is created, or an existing interface is modified, and pointed to the bridge interface. The following is a sample Ethernet interface configuration file pointing to a bridge interface. Configure your physical interface in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth<em class="replaceable"><code>X</code></em></code>, where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface, as follows:
+ </div><div class="example" id="ex-Sample_ifcfg-eth0_interface_configuration_file"><h6>例7.3 ifcfg-ethX インターフェース設定ファイルの例</h6><div class="example-contents"><pre class="programlisting">DEVICE=ethX
+TYPE=Ethernet
+HWADDR=AA:BB:CC:DD:EE:FF
+BOOTPROTO=none
+ONBOOT=yes
+NM_CONTROLLED=no
+BRIDGE=br0</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ For the <code class="option">DEVICE</code> directive, almost any interface name could be used as it does not determine the device type. Other commonly used names include <code class="option">tap</code>, <code class="option">dummy</code> and <code class="option">bond</code> for example. <code class="option">TYPE=Ethernet</code> is not strictly required. If the <code class="option">TYPE</code> directive is not set, the device is treated as an Ethernet device (unless it's name explicitly matches a different interface configuration file.)
+ </div></div></div><div class="para">
+ You can refer to <a class="xref" href="#s1-networkscripts-interfaces">「インターフェース設定ファイル」</a> for a review of the directives and options used in network interface config files.
+ </div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
+ If you are configuring bridging on a remote host, and you are connected to that host over the physical NIC you are configuring, please consider the implications of losing connectivity before proceeding. You will lose connectivity when restarting the service and may not be able to regain connectivity if any errors have been made. Console, or out-of-band access is advised.
+ </div></div></div><div class="para">
+ Restart the networking service, in order for the changes to take effect by running as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command"> systemctl restart network.service </code></pre><div class="para">
+ An example of a network bridge formed from two or more bonded Ethernet interfaces will now be given as this is another common application in a virtualization environment. If you are not very familiar with the configuration files for bonded interfaces then please refer to <a class="xref" href="#s2-networkscripts-interfaces-chan">「チャンネル・ボンディング・インターフェース」</a>
+ </div><div class="para">
+ Create or edit two or more Ethernet interface configuration files, which are to be bonded, as follows:
+<pre class="programlisting">DEVICE=ethX
+TYPE=Ethernet
+USERCTL=no
+SLAVE=yes
+MASTER=bond0
+BOOTPROTO=none
+HWADDR=AA:BB:CC:DD:EE:FF
+NM_CONTROLLED=no</pre>
+
+ </div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ Using <code class="systemitem">eth<em class="replaceable"><code>X</code></em></code> as the interface name is common practice but almost any name could be used. Names such as <code class="option">tap</code>, <code class="option">dummy</code> and <code class="option">bond</code> are commonly used.
+ </div></div></div><div class="para">
+ Create or edit one interface configuration file, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond0</code>, as follows:
+<pre class="programlisting">DEVICE=bond0
+ONBOOT=yes
+BONDING_OPTS='mode=1 miimon=100'
+BRIDGE=brbond0
+NM_CONTROLLED=no</pre>
+ For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to <a class="xref" href="#sec-Using_Channel_Bonding">「Using Channel Bonding」</a>.
+ </div><div class="para">
+ Create or edit one interface configuration file, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-brbond0</code>, as follows:
+<pre class="programlisting">DEVICE=brbond0
+ONBOOT=yes
+TYPE=Bridge
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+NM_CONTROLLED=no</pre>
+
+ </div><div class="figure" id="exam-Network_Interfaces-bridge-with-bond"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Interfaces-bridge-with-bond.png"><img src="images/Network_Interfaces-bridge-with-bond.png" alt="A network bridge consisting of two bonded Ethernet interfaces." /><div class="longdesc"><div class="para">
+ A diagram of two Ethernet interfaces on the left feeding into a virtual interface labeled <code class="literal">bond 0</code>. This in turn leads to a virtual interface called <code class="literal">BR Bond 0</code> on the right. From there a path leads to a virtual network below.
+ </div></div></div></div><h6>図7.1 A network bridge consisting of two bonded Ethernet interfaces.</h6></div><br class="figure-break" /><div class="para">
+ We now have two or more interface configuration files with the <code class="option">MASTER=bond0</code> directive. These point to the configuration file named <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond0</code>, which contains the <code class="option">DEVICE=bond0</code> directive. This <code class="filename">ifcfg-bond0</code> in turn points to the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-brbond0</code> configuration file, which contains the IP address, and acts as an interface to the virtual networks inside the host.
+ </div><div class="para">
+ Restart the networking service, in order for the changes to take effect by running as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command"> systemctl restart network.service </code></pre></div><div class="section" id="s2-networkscripts-interfaces_802.1q-vlan-tagging"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.4. Setting up 802.1q VLAN tagging</h3></div></div></div><a id="idm104966432" class="indexterm"></a><a id="idm103759936" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Ensure that the module is loaded by entering the following command:
+ </div><pre class="screen"><code class="command"> lsmod | grep 8021q</code></pre></li><li class="step"><div class="para">
+ If the module is not loaded, load it with the following command:
+ </div><pre class="screen"><code class="command">modprobe 8021q</code></pre></li><li class="step"><div class="para">
+ Configure your physical interface in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth<em class="replaceable"><code>X</code></em></code>, where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface, as follows:
+ </div><pre class="screen">DEVICE=ethX
+TYPE=Ethernet
+BOOTPROTO=none
+ONBOOT=yes</pre></li><li class="step"><div class="para">
+ Configure the VLAN interface configuration in <code class="filename">/etc/sysconfig/network-scripts</code>. The configuration filename should be the physical interface plus a <code class="literal">.</code> character plus the VLAN ID number. For example, if the VLAN ID is 192, and the physical interface is <code class="systemitem">eth0</code>, then the configuration filename should be <code class="filename">ifcfg-eth0.192</code>:
+ </div><pre class="screen">DEVICE=ethX.192
+BOOTPROTO=static
+ONBOOT=yes
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+USERCTL=no
+NETWORK=192.168.1.0
+VLAN=yes</pre><div class="para">
+ If there is a need to configure a second VLAN, with for example, VLAN ID 193, on the same interface, <code class="systemitem">eth0</code> , add a new file with the name <code class="filename">eth0.193</code> with the VLAN configuration details.
+ </div></li><li class="step"><div class="para">
+ Restart the networking service, in order for the changes to take effect by running as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command"> systemctl restart network.service </code></pre></li></ol></div></div><div class="section" id="s2-networkscripts-interfaces-alias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.5. エイリアス ファイルとクローン ファイル</h3></div></div></div><a id="idm85248144" class="indexterm"></a><a id="idm126418208" class="indexterm"></a><div class="para">
+ Two lesser-used types of interface configuration files are <em class="firstterm">alias</em> and <em class="firstterm">clone</em> files. As the <code class="command">ip</code> command of the <span class="package">iproute</span> package now supports assigning multiple address to the same interface it is no longer necessary to use this method of binding multiple addresses to the same interface.
+ </div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ At the time of writing, <span class="application"><strong>NetworkManager</strong></span> does not detect IP aliases in <code class="filename">ifcfg</code> files. For example, if <code class="filename">ifcfg-eth0</code> and <code class="filename">ifcfg-eth0:1</code> files are present, <span class="application"><strong>NetworkManager</strong></span> creates two connections, which will cause confusion.
+ </div></div></div><div class="para">
+ For new installations, users should select the <span class="guilabel"><strong>Manual</strong></span> method on the IPv4 or IPv6 tab in <span class="application"><strong>NetworkManager</strong></span> to assign multiple IP address to the same interface. For more information on using this tool, refer to <a class="xref" href="#ch-NetworkManager">6章<em>NetworkManager</em></a>.
+ </div><div class="para">
+ Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the <code class="filename">ifcfg-<em class="replaceable"><code>if-name</code></em>:<em class="replaceable"><code>alias-value</code></em></code> naming scheme.
+ </div><div class="para">
+ For example, an <code class="filename">ifcfg-eth0:0</code> file could be configured to specify <code class="literal">DEVICE=eth0:0</code> and a static IP address of <code class="systemitem">10.0.0.2</code>, serving as an alias of an Ethernet interface already configured to receive its IP information via DHCP in <code class="filename">ifcfg-eth0</code>. Under this configuration, <code class="systemitem">eth0</code> is bound to a dynamic IP address, but the same physical network card can receive requests via the fixed, <code class="systemitem">10.0.0.2</code> IP address.
+ </div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
+ エイリアス インターフェースは DHCP をサポートしません。
+ </div></div></div><div class="para">
+ A clone interface configuration file should use the following naming convention: <code class="filename">ifcfg-<em class="replaceable"><code>if-name</code></em>-<em class="replaceable"><code>clone-name</code></em></code>. While an alias file allows multiple addresses for an existing interface, a clone file is used to specify additional options for an interface. For example, a standard DHCP Ethernet interface called <code class="systemitem">eth0</code>, may look similar to this:
+ </div><pre class="programlisting">DEVICE=eth0
+ONBOOT=yes
+BOOTPROTO=dhcp</pre><div class="para">
+ Since the default value for the <code class="option">USERCTL</code> directive is <code class="literal">no</code> if it is not specified, users cannot bring this interface up and down. To give users the ability to control the interface, create a clone by copying <code class="filename">ifcfg-eth0</code> to <code class="filename">ifcfg-eth0-user</code> and add the following line to <code class="filename">ifcfg-eth0-user</code>:
+ </div><pre class="programlisting">USERCTL=yes</pre><div class="para">
+ This way a user can bring up the <code class="systemitem">eth0</code> interface using the <code class="command">/sbin/ifup eth0-user</code> command because the configuration options from <code class="filename">ifcfg-eth0</code> and <code class="filename">ifcfg-eth0-user</code> are combined. While this is a very basic example, this method can be used with a variety of options and interfaces.
+ </div><div class="para">
+ It is no longer possible to create alias and clone interface configuration files using a graphical tool. However, as explained at the beginning of this section, it is no longer necessary to use this method as it is now possible to directly assign multiple IP address to the same interface. For new installations, users should select the <span class="guilabel"><strong>Manual</strong></span> method on the IPv4 or IPv6 tab in <span class="application"><strong>NetworkManager</strong></span> to assign multiple IP address to the same interface. For more information on using this tool, refer to <a class="xref" href="#ch-NetworkManager">6章<em>NetworkManager</em></a>.
+ </div></div><div class="section" id="s2-networkscripts-interfaces-ppp0"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.6. ダイヤルアップ インターフェース</h3></div></div></div><a id="idm85668480" class="indexterm"></a><div class="para">
+ ダイヤルアップ接続を通してインターネットに接続する場合、インターフェース用に設定ファイルが必要です。
+ </div><div class="para">
+ PPP インターフェイス ファイルは、以下の形式を使用して名付けられます:
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-ppp<em class="replaceable"><code>X</code></em> </code></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>X</code></em> は特定のインターフェースに対応する一意な番号です。
+ </div></dd></dl></div>
+
+ </div><div class="para">
+ ダイヤルアップアカウントを作成するために、<code class="command">wvdial</code>、<span class="application"><strong>ネットワーク管理ツール</strong></span> または <span class="application"><strong>Kppp</strong></span> を使用するとき、PPP インターフェース設定ファイルが自動的に作成されます。手動でこのファイルを作成および編集することもできます。
+ </div><div class="para">
+ 以下は一般的な <code class="filename">ifcfg-ppp0</code> ファイルです:
+ </div><pre class="programlisting">DEVICE=ppp0
+NAME=test
+WVDIALSECT=test
+MODEMPORT=/dev/modem
+LINESPEED=115200
+PAPNAME=test
+USERCTL=true
+ONBOOT=no
+PERSIST=no
+DEFROUTE=yes
+PEERDNS=yes
+DEMAND=no
+IDLETIMEOUT=600
+</pre><div class="para">
+ <em class="firstterm">Serial Line Internet Protocol </em> (<acronym class="acronym">SLIP</acronym>) is another dialup interface, although it is used less frequently. SLIP files have interface configuration file names such as <code class="filename">ifcfg-sl0</code>.
+ </div><div class="para">
+ これらのファイルで使用できる他のオプションを以下に示します：
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">DEFROUTE</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このインターフェースをデフォルトルートとして設定します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — このインターフェースをデフォルトルートとして設定しません。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">DEMAND</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このインターフェースは <code class="command">pppd</code> が使用しようとするときに接続を初期化できます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — 接続はこのインターフェースに対して手動で確立する必要があります。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">IDLETIMEOUT</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>value</code></em> is the number of seconds of idle activity before the interface disconnects itself.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">INITSTRING</code>=<em class="replaceable"><code>string</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>string</code></em> is the initialization string passed to the modem device. This option is primarily used in conjunction with SLIP interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">LINESPEED</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>value</code></em> is the baud rate of the device. Possible standard values include <code class="literal">57600</code>, <code class="literal">38400</code>, <code class="literal">19200</code>, and <code class="literal">9600</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">MODEMPORT</code>=<em class="replaceable"><code>device</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>device</code></em> is the name of the serial device that is used to establish the connection for the interface.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">MTU</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>value</code></em> is the <em class="firstterm">Maximum Transfer Unit</em> (<acronym class="acronym">MTU</acronym>) setting for the interface. The MTU refers to the largest number of bytes of data a frame can carry, not counting its header information. In some dialup situations, setting this to a value of <code class="literal">576</code> results in fewer packets dropped and a slight improvement to the throughput for a connection.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">NAME</code>=<em class="replaceable"><code>name</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>name</code></em> is the reference to the title given to a collection of dialup connection configurations.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">PAPNAME</code>=<em class="replaceable"><code>name</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>name</code></em> is the username given during the <em class="firstterm">Password Authentication Protocol</em> (<acronym class="acronym">PAP</acronym>) exchange that occurs to allow connections to a remote system.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">PERSIST</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — This interface should be kept active at all times, even if deactivated after a modem hang up.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — This interface should not be kept active at all times.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">REMIP</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>address</code></em> is the IP address of the remote system. This is usually left unspecified.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">WVDIALSECT</code>=<em class="replaceable"><code>name</code></em> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code>name</code></em> associates this interface with a dialer configuration in <code class="filename">/etc/wvdial.conf</code>. This file contains the phone number to be dialed and other important information for the interface.
+ </div></dd></dl></div></div><div class="section" id="s2-networkscripts-interfaces-other"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.7. 他のインターフェース</h3></div></div></div><div class="para">
+ 他の一般的なインターフェイス設定ファイルは次の項目を含みます：
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-lo</code></span></dt><dd><div class="para">
+ ローカルの <em class="firstterm">ループバック インターフェイス</em> はよくテストで 使用されるだけでなく、同じシステムを指定し直す IP アドレスを必要とするさまざまなアプリケーションでも使用されます。ループバックデバイスに送信されたデータはすぐにホストのネットワーク層に戻されます。
+ </div><div class="warning"><div class="admonition_header"><h2>ifrcfg-lo スクリプトは手動で編集しません</h2></div><div class="admonition"><div class="para">
+ ループバックインターフェースのスクリプト <code class="filename">/etc/sysconfig/network-scripts/ifcfg-lo</code> は、手動で編集すべきではありません。そうすると、システムが正しく動作しなくなる可能性がありません。
+ </div></div></div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-irlan0</code></span></dt><dd><div class="para">
+ <em class="firstterm">赤外線インターフェース</em> によって、ラップトップとプリンタなどデバイス間の情報を赤外線リンク上で流すことができます。これは、通常ピアツーピア接続で可能という事以外はイーサネットと同じような方法で動作します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-plip0</code></span></dt><dd><div class="para">
+ A <em class="firstterm">Parallel Line Interface Protocol</em> (<acronym class="acronym">PLIP</acronym>) connection works much the same way as an Ethernet device, except that it utilizes a parallel port.
+ </div></dd></dl></div></div></div><div class="section" id="s1-networkscripts-control"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. インターフェース制御スクリプト</h2></div></div></div><a id="idm134190608" class="indexterm"></a><a id="idm123299920" class="indexterm"></a><a id="idm83092896" class="indexterm"></a><a id="idm111126544" class="indexterm"></a><div class="para">
+ インターフェース制御スクリプトはシステムインターフェースを活性化および非活性化します。<code class="filename">/etc/sysconfig/network-scripts/</code> ディレクトリーに置かれている制御スクリプトにおいて呼び出す 2 つの主なインターフェース制御スクリプトがあります: <code class="command">/sbin/ifdown</code> および <code class="command">/sbin/ifup</code>。
+ </div><div class="para">
+ <code class="filename">ifup</code> および <code class="filename">ifdown</code> インターフェーススクリプトは、<code class="filename">/sbin/</code> ディレクトリにあるスクリプトへのシンボリックリンクです。これらのスクリプトのいずれかが呼び出されるとき、次のように、インターフェースの値が指定される必要があります:
+ </div><pre class="screen"><code class="command">ifup eth0</code></pre><div class="warning"><div class="admonition_header"><h2>インターフェースのスクリプト ifup と ifdown を使う</h2></div><div class="admonition"><div class="para">
+ <code class="filename">ifup</code> および <code class="filename">ifdown</code> インターフェーススクリプトは、ユーザーがネットワークインターフェースを起動または停止するために使用する唯一のスクリプトです。
+ </div><div class="para">
+ 参考のために以下にスクリプトの例をあげておきます。
+ </div></div></div><div class="para">
+ ネットワークインターフェースが起動するプロセス中にさまざまなネットワーク初期化作業を実行するために使用される2つのファイルが、<code class="filename">/etc/rc.d/init.d/functions</code> および <code class="filename">/etc/sysconfig/network-scripts/network-functions</code> です。詳細は<a class="xref" href="#s1-networkscripts-functions">「ネットワーク機能ファイル」</a>を参照してください。
+ </div><div class="para">
+ インターフェースが指定され、要求を実行しているユーザーがインターフェースを制御することが許可された後、適切なスクリプトがインターフェースを起動または停止します。以下は、<code class="filename">/etc/sysconfig/network-scripts/</code> ディレクトリーの中にある一般的なインターフェース制御スクリプトです:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">ifup-aliases</code></span></dt><dd><div class="para">
+ 複数の IP アドレスが 1 つのインターフェイスに関連付けられている場合、インターフェース設定ファイルから IP エイリアスを設定します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-ippp</code> と <code class="filename">ifdown-ippp</code></span></dt><dd><div class="para">
+ ISDN インターフェースをアップとダウンする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-ipv6</code> と <code class="filename">ifdown-ipv6</code></span></dt><dd><div class="para">
+ IPv6 インターフェースをアップとダウンする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-plip</code></span></dt><dd><div class="para">
+ PLIP インターフェースをアップする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-plusb</code></span></dt><dd><div class="para">
+ ネットワーク接続用の USB インターフェースをアップする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-post</code> と <code class="filename">ifdown-post</code></span></dt><dd><div class="para">
+ これらには、インターフェイスを立ち上げた後、及び停止した後に実行されるコマンドが含まれています。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-ppp</code> と <code class="filename">ifdown-ppp</code></span></dt><dd><div class="para">
+ PPP インターフェースをアップとダウンする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-routes</code></span></dt><dd><div class="para">
+ デバイスの静的ルートを、そのインターフェイスがアップするときに追加します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifdown-sit</code> と <code class="filename">ifup-sit</code></span></dt><dd><div class="para">
+ IPv4 接続内にある IPv6 トンネルのアップ/ダウンに関連した機能呼び出しを含みます。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-wireless</code></span></dt><dd><div class="para">
+ ワイヤレスインターフェースをアップする為に使用します。
+ </div></dd></dl></div><div class="warning"><div class="admonition_header"><h2>ネットワーク スクリプトの修正と削除をする際は注意をしてください!</h2></div><div class="admonition"><div class="para">
+ Removing or modifying any scripts in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory can cause interface connections to act irregularly or fail. Only advanced users should modify scripts related to a network interface.
+ </div></div></div><div class="para">
+ The easiest way to manipulate all network scripts simultaneously is to use the <code class="command">systemctl</code> command on the network service (<code class="filename">/etc/rc.d/init.d/network</code>), as illustrated by the following command:
+ </div><pre class="screen"><code class="command">systemctl <em class="replaceable"><code>action</code></em> network.service</code></pre><div class="para">
+ ここで、<em class="replaceable"><code>action</code></em> は <code class="command">start</code>, <code class="command">stop</code>, または <code class="command">restart</code> のどれかです。
+ </div><div class="para">
+ 設定したデバイスと現在アクティブになっているネットワーク インターフェースの一覧を表示するには、次のコマンドを使用します：
+ </div><pre class="screen"><code class="command"> systemctl status network.service</code></pre><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ The older SysV service commands, such as <span class="quote">「<span class="quote">service network status</span>」</span> are considered deprecated but will still work. The SysV services can define their status in an arbitrary fashion so the output of the status command is not considered predictable over time. The SysV commands are retained for compatibility purposes. The <span class="application"><strong>/sbin/service</strong></span> utility will call <span class="application"><strong>systemctl</strong></span> when necessary.
+ </div></div></div></div><div class="section" id="s1-networkscripts-static-routes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.4. スタティック ルートの設定</h2></div></div></div><div class="para">
+ Static routes are for traffic that must not, or should not, go through the default route. Use the <code class="command">route</code> command to display the IP routing table. If static routes are required, they can be specified by means of the GATEWAY directive, either globally or in interface-specific configuration files. There is also the GATEWAYDEV directive, which is a global option. If multiple devices specify GATEWAY, and one interface is specified using the GATEWAYDEV directive, that directive will take precedence. This option is not recommend. Specifying an exit interface is optional. It can be useful if you want to force traffic out of a specific interface. For example, in the case of a VPN, you can force traffic to a remote network to pass through a tun0 interface even when the interface is in a different sub-net to the destination network.
+ </div><div class="para">
+ Global static route configuration is stored in the <code class="filename">/etc/sysconfig/network</code> file. This file specifies routing and host information for all network interfaces. For more information about this file and the directives it accepts, refer to <a class="xref" href="#s2-sysconfig-network">「/etc/sysconfig/network」</a>.
+ </div><div class="para">
+ Per-interface static route configuration is stored in a <code class="filename">/etc/sysconfig/network-scripts/route-<em class="replaceable"><code>interface</code></em></code> file. For example, static routes for the <code class="systemitem">eth0</code> interface would be stored in the <code class="filename">/etc/sysconfig/network-scripts/route-eth0</code> file. The <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> file has two formats: IP command arguments and network/netmask directives.
+ </div><h3 id="bh-networkscripts-static-routes-ip-command">IP コマンドの引数形式</h3><div class="para">
+ 最初の行にデフォルトゲートウェイを定義します。デフォルトゲートウェイが DHCP 経由で設定されていないときのみ、これが必要になります:
+ </div><pre class="synopsis">default via <em class="replaceable"><code>X.X.X.X</code></em><code class="option"> dev </code><em class="replaceable"><code>interface</code></em></pre><div class="para">
+ <em class="replaceable"><code>X.X.X.X</code></em> is the IP address of the default gateway. The <em class="replaceable"><code>interface</code></em> is the interface that is connected to, or can reach, the default gateway. The <code class="option"> dev </code> option can be omitted.
+ </div><div class="para">
+ 静的ルーティングを定義します。各行はそれぞれルーティングとして構文解析されます:
+ </div><pre class="synopsis"><em class="replaceable"><code>X.X.X.X/X</code></em> via <em class="replaceable"><code>X.X.X.X</code></em> dev <em class="replaceable"><code>interface</code></em></pre><div class="para">
+ <em class="replaceable"><code>X.X.X.X/X</code></em> は静的ルートに対するネットワークの番号とネットマスクです。<em class="replaceable"><code>X.X.X.X</code></em> および <em class="replaceable"><code>interface</code></em> はそれぞれデフォルトゲートウェイに対する IP アドレスとインターフェースです。<em class="replaceable"><code>X.X.X.X</code></em> のアドレスはデフォルトゲートウェイの IP アドレスである必要がありません。多くの場合、<em class="replaceable"><code>X.X.X.X</code></em> は異なるサブネットにおける IP アドレスです。また、<em class="replaceable"><code>interface</code></em> は、そのサブネットに接続されている、または到達できるインターフェースです。
+ </div><div class="para">
+ 以下は IP コマンド引数形式を使用するサンプル <code class="filename">route-eth0</code> ファイルです。デフォルトゲートウェイは 192.168.0.1、インターフェース eth0 です。2 つの静的ルートは 10.10.10.0/24 および 172.16.1.0/24 のネットワークに対するものです:
+ </div><pre class="screen">default via 192.168.0.1 dev eth0
+10.10.10.0/24 via 192.168.0.1 dev eth0
+172.16.1.0/24 via 192.168.0.1 dev eth0</pre><div class="para">
+ Static routes should only be configured for other subnets. The above example is not necessary, since packets going to the 10.10.10.0/24 and 172.16.1.0/24 networks will use the default gateway anyway. Below is an example of setting static routes to a different subnet, on a machine in a 192.168.0.0/24 subnet. The example machine has an <code class="systemitem">eth0</code> interface in the 192.168.0.0/24 subnet, and an <code class="systemitem">eth1</code> interface (10.10.10.1) in the 10.10.10.0/24 subnet:
+ </div><pre class="screen">10.10.10.0/24 via 10.10.10.1 dev eth1</pre><div class="important"><div class="admonition_header"><h2>デフォルト ゲートウェイの複製</h2></div><div class="admonition"><div class="para">
+ デフォルトゲートウェイがすでに DHCP から割り当てられていると、IP コマンド引数のフォーマットは、起動中、または <code class="command">ifup</code> コマンドを使用してインターフェースを停止状態から起動するとき、次のエラーのうちどちらかが発生します: "RTNETLINK answers: File exists" または 'Error: either "to" is a duplicate, or "<em class="replaceable"><code>X.X.X.X</code></em>" is a garbage.'、ここで <em class="replaceable"><code>X.X.X.X</code></em> はゲートウェイまたは他の IP アドレスです。デフォルトゲートウェイを使用して他のネットワークへの他のルートがあると、これらのエラーが発生する可能性があります。これらのエラーはどちらも無視しても安全です。
+ </div></div></div><h3 id="bh-networkscripts-static-routes-network-netmask-directives">ネットワーク/ネットマスク ディレクティブの形式</h3><div class="para">
+ You can also use the network/netmask directives format for <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> files. The following is a template for the network/netmask format, with instructions following afterwards:
+ </div><pre class="synopsis"> ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em> NETMASK0=<em class="replaceable"><code>X.X.X.X</code></em> GATEWAY0=<em class="replaceable"><code>X.X.X.X</code></em> </pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em></code> is the network number for the static route.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NETMASK0=<em class="replaceable"><code>X.X.X.X</code></em></code> is the netmask for the network number defined with <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">GATEWAY0=<em class="replaceable"><code>X.X.X.X</code></em></code> is the default gateway, or an IP address that can be used to reach <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em></code>
+ </div></li></ul></div><div class="para">
+ The following is a sample <code class="filename">route-eth0</code> file using the network/netmask directives format. The default gateway is 192.168.0.1, interface <code class="systemitem">eth0</code>. The two static routes are for the 10.10.10.0/24 and 172.16.1.0/24 networks. However, as mentioned before, this example is not necessary as the 10.10.10.0/24 and 172.16.1.0/24 networks would use the default gateway anyway:
+ </div><pre class="programlisting">ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=192.168.0.1
+ADDRESS1=172.16.1.0
+NETMASK1=255.255.255.0
+GATEWAY1=192.168.0.1</pre><div class="para">
+ 後続の静的ルートが順番に番号がつけられる必要があります。また、すべての値を飛ばすことはできません。たとえば、<code class="computeroutput">ADDRESS0</code>, <code class="computeroutput">ADDRESS1</code>, <code class="computeroutput">ADDRESS2</code>, などです。
+ </div><div class="para">
+ Below is an example of setting static routes to a different subnet, on a machine in the 192.168.0.0/24 subnet. The example machine has an <code class="systemitem">eth0</code> interface in the 192.168.0.0/24 subnet, and an <code class="systemitem">eth1</code> interface (10.10.10.1) in the 10.10.10.0/24 subnet:
+ </div><pre class="programlisting">ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=10.10.10.1</pre><div class="para">
+ DHCP が使用されていると、これらの設定が自動的に割り当てられることに注意してください。
+ </div></div><div class="section" id="s1-networkscripts-functions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.5. ネットワーク機能ファイル</h2></div></div></div><a id="idm94188368" class="indexterm"></a><div class="para">
+ Fedora は、インターフェースを起動および停止するために使用される、重要な一般的な機能を含むいくつかのファイルを使用します。それぞれのインターフェース制御ファイルにこれらの機能を強制的に含めるよりは、必要なときに呼び出されるいくつかのファイルに一緒にグループ化します。
+ </div><div class="para">
+ <code class="filename">/etc/sysconfig/network-scripts/network-functions</code> ファイルは最も一般的に使用される IPv4 機能が含まれます。これは多くのインターフェース制御スクリプトにとって有用です。これらの機能には、インターフェースの状態の変更、ホスト名の設定、ゲートウェイデバイスの検索、特定のデバイスがダウンしているかどうかの検証、およびデフォルトルートの追加に関して、必要とされる情報を持つ実行中のプログラムにアクセスすることを含みます。
+ </div><div class="para">
+ IPv6 インターフェースに対して要求される関数は IPv4 インターフェースとは異なるので、<code class="filename">/etc/sysconfig/network-scripts/network-functions-ipv6</code> ファイルはこの情報を保持するために特別に存在します。このファイルにある関数は、静的 IPv6 ルートを設定および削除、トンネルを作成および削除、インターフェースに IPv6 アドレスを追加および削除、およびインターフェースに IPv6 アドレスの存在を確認します。
+ </div></div><div class="section" id="s1-networkscripts-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.6. その他のリソース</h2></div></div></div><a id="idm110905872" class="indexterm"></a><div class="para">
+ ネットワークインターフェースに関して詳細に説明しているリソースを以下に示します。
+ </div><div class="section" id="s2-networkscripts-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.6.1. インストールされているドキュメント</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code>version</code></em>/sysconfig.txt</code></span></dt><dd><div class="para">
+ この章では触れていない IPv6 オプションなど、ネットワーク設定ファイル用に利用可能なオプションへの手引きです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/iproute-<em class="replaceable"><code>version</code></em>/ip-cref.ps</code></span></dt><dd><div class="para">
+ このファイルは <code class="command">ip</code> コマンドに関する豊富な情報を含みます。ここで、他のことがらの間で、ルーティングテーブルを操作するために使用できます。このファイルを表示するには <span class="application"><strong>ggv</strong></span> または <span class="application"><strong>kghostview</strong></span> アプリケーションを使用します。
+ </div></dd></dl></div></div></div></div></div><div class="part" id="part-Infrastructure_Services"><div class="titlepage"><div><div text-align="center"><h1 class="title">パート IV. インフラストラクチャーサービス</h1></div></div></div><div class="partintro" id="idm90052288"><div></div><div class="para">
+ このパートはサービスとデーモンの設定、認証の設定、およびリモートログインを有効にする方法に関する情報を提供します。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="#ch-Services_and_Daemons">8. サービスおよびデーモン</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-configuring">8.1. サービスの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">8.1.1. サービスの有効化</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">8.1.2. サービスの無効化</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">8.2. サービスの実行</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">8.2.1. サービスの状態の確認</a></span></dt><dt><span class="section"><a href="#s3-services-running-running">8.2.2. サービスの実行</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">8.2.3. サービスの停止</a></span></dt><dt
><span class="section"><a href="#s3-services-running-restarting">8.2.4. サービスの再起動</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">8.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">8.3.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">8.3.2. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_Authentication">9. 認証の設定</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">9.1. 認証の設定ツール</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">9.1.1. 識別と認証</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configurati
on_Tool-Advanced_Options">9.1.2. 高度なオプション</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">9.1.3. コマンドライン版</a></span></dt></dl></dd><dt><span class="section"><a href="#chap-SSSD_User_Guide-Introduction">9.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-What_is_SSSD">9.2.1. SSIDとは?</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">9.2.2. SSIDの特徴</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Setting_Up_SSSD">9.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Services">9.2.4. サービスの設定</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Domains">9.2.5. Configuring Domains</a></span></dt><dt><span class="secti
on"><a href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">9.2.6. Setting Up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">9.2.7. Configuring a Proxy Domain</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Troubleshooting">9.2.8. トラブルシューティング</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">9.2.9. SSSD Configuration File Format</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">10. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">10.1. SSH プロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">10.1.1. なぜ SSH を使うのか？</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">10.1.2. 主な
機能</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">10.1.3. プロトコル・バージョン</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">10.1.4. SSH コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">10.2. OpenSSH の設定</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">10.2.1. 設定ファイル</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-sshd">10.2.2. OpenSSH サーバーの起動</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">10.2.3. リモート接続に対する SSH の要求</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">10.2.4. キー認証の使用</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">10.3. OpenSSH クライアント</a></span></dt><dd><dl><dt><span class="section
"><a href="#s2-ssh-clients-ssh">10.3.1. ssh ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">10.3.2. <code class="command">scp</code> ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">10.3.3. <code class="command">sftp</code> ユーティリティの使用方法</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">10.4. 安全なシェル以上のもの</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">10.4.1. X11 転送</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">10.4.2. ポート転送</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">10.5. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-openssh-installed-docs">10.5.1. インストールされているドキュメント</a></span></dt><
dt><span class="section"><a href="#s2-openssh-useful-websites">10.5.2. 役に立つ Web サイト</a></span></dt></dl></dd></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">第8章 サービスおよびデーモン</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-services-configuring">8.1. サービスの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">8.1.1. サービスの有効化</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">8.1.2. サービスの無効化</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">8.2. サービスの実行</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">8.2.1. サービスの状態の確認</a></span></dt><dt><span class="section"><a href="#s
3-services-running-running">8.2.2. サービスの実行</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">8.2.3. サービスの停止</a></span></dt><dt><span class="section"><a href="#s3-services-running-restarting">8.2.4. サービスの再起動</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">8.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">8.3.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">8.3.2. 関連書籍</a></span></dt></dl></dd></dl></div><a id="idm139415488" 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 17 <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">8.1. サービスの設定</h2></div></div></div><a id="idm118606992" class="indexterm"></a><a id="idm132772016" 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 17 のインストール中にインストールされ設定されています。<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">8.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>例8.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">8.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>例8.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">8.2. サービスの実行</h2></div></div></div><a id="idm135821680" class="indexterm"></a><a id="idm137419856" 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">8.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>例8.3 httpd サービスの状態の確認</h6><div class="example-contents"><div class="para">
+ <a class="xref" href="#exam-services-configuration-enabling">例8.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>例8.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">8.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>例8.5 httpd サービスの実行</h6><div class="example-contents"><div class="para">
+ <a class="xref" href="#exam-services-configuration-enabling">例8.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">8.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>例8.6 telnet サービスの停止</h6><div class="example-contents"><div class="para">
+ <a class="xref" href="#exam-services-configuration-disabling">例8.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">8.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>例8.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 httpd.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">8.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">8.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">8.3.2. 関連書籍</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="citetitle">Fedora 17 セキュリティガイド</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-Configuring_Authentication" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第9章 認証の設定</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">9.1. 認証の設定ツール</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">9.1.1. 識別と認証</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">9.1.2. 高度なオプション</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">9.1.3. コマンドライン版</a></span></dt></dl></dd><dt><span class="section"><a href="#chap-SSSD_User_Guide-Introduction">9.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class=
"section"><a href="#sect-SSSD_User_Guide-Introduction-What_is_SSSD">9.2.1. SSIDとは?</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">9.2.2. SSIDの特徴</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Setting_Up_SSSD">9.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Services">9.2.4. サービスの設定</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Domains">9.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">9.2.6. Setting Up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">9.2.7. Configuring a Proxy Domain</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Troubleshooting">9.2.
8. トラブルシューティング</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">9.2.9. SSSD Configuration File Format</a></span></dt></dl></dd></dl></div><div class="section" id="sect-The_Authentication_Configuration_Tool"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.1. 認証の設定ツール</h2></div></div></div><a id="idm123524272" class="indexterm"></a><a id="idm123525872" class="indexterm"></a><div class="para">
+ ユーザーが Fedora システムにログインするとき、ユーザー名とパスワードの組み合わせが有効かつアクティブなユーザーとして検証または<em class="firstterm">認証</em>されなければいけません。ときどき、ユーザーを検証するための情報はローカルシステムに置かれます。それ以外の場合、システムは認証をリモートシステムにあるユーザーデータベースに従います。
+ </div><div class="para">
+ <span class="application"><strong>認証の設定ツール</strong></span>は、<em class="firstterm">Lightweight Directory Access Protocol</em> (LDAP), <em class="firstterm"> Network Information Service</em> (NIS), および <em class="firstterm">Winbind</em> ユーザーアカウントデータベースから取り出したユーザー情報を設定するためのグラフィカルインターフェースを提供します。このツールは LDAP または NIS を使用しているとき、認証プロトコルとして Kerberos を使用するようにも設定できます。
+ </div><div class="note"><div class="admonition_header"><h2>中高セキュリティレベルの使用</h2></div><div class="admonition"><div class="para">
+ インストール中に中間または高セキュリティレベルを設定すると (または<span class="application"><strong>セキュリティレベル設定ツール</strong></span>)、ファイアウォールが NIS 認証を妨害します。ファイアウォールに関する詳細は、Fedora 17 <em class="citetitle">セキュリティガイド</em> の <em class="citetitle">"ファイアウォール"</em> セクションを参照してください。
+ </div></div></div><a id="idm110234640" class="indexterm"></a><a id="idm110236400" class="indexterm"></a><div class="para">
+ デスクトップから<span class="application"><strong>認証の設定</strong></span>のグラフィカル版を起動するには、<span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>その他</strong></span> → <span class="guimenuitem"><strong>認証</strong></span>を選択します、または（たとえば <span class="application"><strong>XTerm</strong></span> や <span class="application"><strong>GNOME</strong></span> 端末において）シェルプロンプトにコマンド <code class="command">system-config-authentication</code> を入力します。
+ </div><div class="important"><div class="admonition_header"><h2>変更は即座に適用されます</h2></div><div class="admonition"><div class="para">
+ 認証プログラムを終了した後、あらゆる変更は即座に反映されます。
+ </div></div></div><div class="section" id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.1. 識別と認証</h3></div></div></div><div class="para">
+ <span class="guilabel"><strong>識別と認証</strong></span>タブにより、どのようにユーザーが認証されるかを設定できます。また、それぞれの認証方式に対するいくつかのオプションがあります。どのユーザーアカウントデータベースが使用されるべきかを選択するには、ドロップダウンリストからオプションを選択します。
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject" align="center" id="mediaobj-authconfig_LDAP_kerb"><img src="images/authconfig_LDAP_kerb.png" align="middle" alt="識別と認証：ユーザーアカウントデータベースのドロップダウンにおいてオプションを変更すると、タブの内容が変更されます" /></div></div><h6>図9.1 識別と認証：ユーザーアカウントデータベースのドロップダウンにおいてオプションを変更すると、タブの内容が変更されます</h6></div><br class="figure-break" /><div class="para">
+ 以下の一覧は各オプションの説明です。
+ </div><h4 id="idm86597936">LDAP</h4><a id="idm86596960" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>LDAP</strong></span> オプションはシステムが LDAP 経由でユーザー情報を取得するよう指示します。以下の指定を含みます:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP 検索のベース DN</strong></span> — ユーザー情報が一覧化された識別名 (DN: Distinguished Name) を使用して取得されるよう指定します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP Server</strong></span> — <code class="systemitem">LDAP</code> サーバーのアドレスを指定します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>暗号化通信のために TLS を使用する</strong></span> — 有効になっているとき、<code class="systemitem">LDAP</code> サーバーに送信されるパスワードを暗号化するために <code class="systemitem">Transport Layer Security</code> (TLS) が使用されます。<span class="guibutton"><strong>CA 証明書のダウンロード</strong></span> オプションにより、有効な <em class="firstterm">認証局の証明書</em> (CA: Certificate Authority) をダウンロードする URL を指定できます。有効な CA 証明書は <em class="firstterm">Privacy Enhanced Mail</em> (PEM) 形式である必要があります。
+ </div><div class="important"><div class="admonition_header"><h2>LDAP サーバー項目における ldaps:// の使用法</h2></div><div class="admonition"><div class="para">
+ <code class="systemitem">ldaps://</code> サーバーアドレスが <span class="guilabel"><strong>LDAP サーバー</strong></span> の項目に指定されていると、<span class="guilabel"><strong>暗号化通信のために TLS を使用する</strong></span>オプションをチェックする必要がありません。
+ </div></div></div><div class="para">
+ CA 証明書の詳細は<a class="xref" href="#s3-apache-mod_ssl-certificates">「証明書とセキュリティの概要」</a>を参照してください。
+ </div></li></ul></div><div class="para">
+ <code class="filename">openldap-clients</code> パッケージはこのオプションが機能するためにインストールする必要があります。
+ </div><div class="para">
+ LDAP の詳細は<a class="xref" href="#s1-OpenLDAP">「OpenLDAP」</a>を参照してください。
+ </div><div class="para">
+ LDAP は次の認証方法を提供します。
+ </div><div class="itemizedlist"><ul><li class="listitem"><a id="idm134512016" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Kerberos パスワード</strong></span> — このオプションは Kerberos 認証を有効にします。以下の指定を含みます:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>レルム</strong></span> — Kerberos サーバーのレルムを設定します。レルムは Kerberos を使用するネットワークです。一つかそれ以上の KDC および潜在的に大規模なクライアントから構成されます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>KDC</strong></span> — 鍵配布センター (KDC: Key Distribution Centers) を定義します、これは Kerberos チケットを発行するサーバーです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>管理サーバー</strong></span> — <code class="command">kadmind</code> を実行して管理サーバーを指定します。
+ </div></li></ul></div>
+
+ </div><div class="para">
+ <span class="guimenu"><strong>Kerberos 設定</strong></span> ダイアログにより、ホストをレルムに名前解決するため、およびレルムに対する KDC の位置を決めるために、DNS を使用できます。
+ </div><div class="para">
+ このオプションが動作するためには <code class="filename">krb5-libs</code> および <code class="filename">krb5-workstation</code> パッケージがインストールされている必要があります。Kerberos の詳細は、Fedora 17 <em class="citetitle">Managing Single Sign-On and Smart Cards</em> ガイドのセクション <em class="citetitle">Using Kerberos</em> を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP パスワード</strong></span> — このオプションにより、標準的な PAM 対応アプリケーションが LDAP のユーザーアカウント設定において指定されたオプションを用いて LDAP 認証を使用するよう指示します。このオプションを使用するとき、 <code class="systemitem">ldaps://</code> サーバーアドレスを提供する、または LDAP 認証の TLS をしようする必要があります。
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>SSSD サービスの設定</h2></div><div class="admonition"><div class="para">
+ SSSD サービスが LDAP および Kerberos サーバーに対するクライアントとして使用されます。このように、オフラインログインが有効化され、標準でサポートされます。ユーザーの対話が <span class="application"><strong>認証設定ツール</strong></span> で SSSD サービスをセットアップする必要がありません。SSSD サービスに関する詳細は<a class="xref" href="#chap-SSSD_User_Guide-Introduction">「The System Security Services Daemon (SSSD)」</a>を参照してください。
+ </div></div></div><h4 id="idm106847488">NIS</h4><a id="idm88665040" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>NIS</strong></span> オプションは、ユーザーとパスワードの認証のために NIS サーバーに (NIS クライアント) として接続するよう、システムを設定します。このオプションを設定するには、NIS ドメインと NIS サーバーを指定します。NIS サーバーが指定されていないと、デーモンがブロードキャストにより発見しようとします。
+ </div><div class="para">
+ <span class="package">ypbind</span> パッケージがこのオプションの正常動作のためにインストールされている必要があります。NIS ユーザーアカウントデータベースが使用されていると、<code class="systemitem">portmap</code> および <code class="systemitem">ypbind</code> サービスが起動され、ブート時の起動を有効化する必要があります。
+ </div><div class="para">
+ NIS の詳細は、Fedora <em class="citetitle">セキュリティガイド</em> のセクション <em class="citetitle">"NIS のセキュア化"</em> を参照してください。
+ </div><div class="para">
+ NIS は次の認証方法を提供します。
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Kerberos パスワード</strong></span> — このオプションにより Kerberos 認証が有効化されます。Kerberos 認証方法の設定に関する詳細は、LDAP に関する前のセクションを参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <a id="idm117739408" class="indexterm"></a>
+ <span class="guilabel"><strong>NIS パスワード</strong></span> — このオプションは NIS 認証を有効にします。NIS はユーザーを認証するために認証情報を外部のプロセスに提供できます。
+ </div></li></ul></div><h4 id="idm106845504">Winbind</h4><a id="idm106846192" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Winbind</strong></span> オプションはシステムが Windows Active Directory または Windows ドメインコントローラーに接続するよう設定します。指定されたディレクトリーまたはドメインコントローラーからのユーザー情報がアクセスされます。また、サーバー認証オプションが設定できます。以下の仕様が含まれます:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind ドメイン</strong></span> — 接続する Windows Active Directory またはドメインコントローラーを指定します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>セキュリティモデル</strong></span> — Samba クライアントの動作モードを設定する、セキュリティモデルを選択できます。ドロップダウンリストは、以下のどれかを選択できます:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ads</strong></span> — このモードは Active Directory Server (ADS) レルムにおいてドメインメンバーとして動作するよう Samba に指示します。このモードにおいて動作するには、<code class="filename">krb5-server</code> パッケージがインストールされている必要があります。また、Kerberos が正しく設定されている必要があります。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>domain</strong></span> — このモードでは、Windows NT サーバーと同じように、Samba は Windows NT プライマリまたはバックアップドメインコントローラーを通して認証することにより、ユーザー名とパスワードを検証しようとします。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>server</strong></span> — このモードでは、Samba は他の SMB サーバー (たとえば、Windows NT Server) を通して認証することにより、ユーザー名・パスワードを検証しようとします。これに失敗すると、代わりに <span class="guilabel"><strong>user</strong></span> モードが効果を持ちます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>user</strong></span> — これが標準のモードです。このレベルのセキュリティを用いると、クライアントはまず有効なユーザー名とパスワードでログインします。暗号化されたパスワードはこのセキュリティモードにおいても使用できます。
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind ADS Realm</strong></span> — <span class="guilabel"><strong>ads</strong></span> セキュリティモデルが選択されたとき、Samba サーバーがドメインのメンバーとして動作する ADS レルムを指定できます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind Domain Controllers</strong></span> — <code class="command">winbind</code> が使用するドメインコントローラーを指定するために、このオプションを使用します。ドメインコントローラーに関する詳細は、<a class="xref" href="#s3-samba-domain-controller">「Domain Controller」</a>を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>テンプレートシェル</strong></span> — Windows NT ユーザーの情報を記入するとき、<code class="command">winbindd</code> デーモンがユーザーのログインシェルを指定するために、ここで選択された値を使用します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>オフラインログインを許可する</strong></span> — このオプションをチェックすることにより、認証情報を (SSSD により提供される) ローカルキャッシュに保存できるようになります。オフラインの間にユーザーが認証を試行したときに、この情報が使用されます。
+ </div></li></ul></div><div class="para">
+ <code class="command">winbindd</code> サービスに関する詳細は <a class="xref" href="#s2-samba-daemons">「Samba デーモンと関連サービス」</a> を参照してください。
+ </div><a id="idm70561808" class="indexterm"></a><div class="para">
+ Winbind は一つの認証方式 <span class="guilabel"><strong>Winbind パスワード</strong></span>のみを提供します。この方式の認証は、Windows Active Directory または Windows ドメインコントローラーに接続するために、Winbind のユーザーアカウント設定において指定されたオプションを使用します。
+ </div></div><div class="section" id="sect-The_Authentication_Configuration_Tool-Advanced_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.2. 高度なオプション</h3></div></div></div><div class="para">
+ このタブにより、以下にあるような高度なオプションを設定できます。
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject" align="center" id="mediaobj-authconfig_advanced"><img src="images/authconfig_advanced.png" align="middle" width="444" alt="高度なオプション" /></div></div><h6>図9.2 高度なオプション</h6></div><br class="figure-break" /><h4 id="idm84717600">ローカルの認証オプション</h4><div class="itemizedlist"><ul><li class="listitem"><a id="idm107468048" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>指紋読み取り装置のサポートの有効化</strong></span> — このオプションをチェックすることにより、指紋読み取り装置を用いて指紋を読み取ることによりログインするために、指紋認証を有効化します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ローカルアクセス制御を有効化する</strong></span> — 有効にされたとき、ユーザーの認証のために <code class="filename">/etc/security/access.conf</code> が参照されます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>パスワードハッシュ化アルゴリズム</strong></span> — このオプションにより、ローカルに保存されるパスワードを暗号化するために使用されるハッシュ化または暗号化アルゴリズムを指定できます。
+ </div></li></ul></div><h4 id="idm119660800">その他の認証オプション</h4><div class="para">
+ <span class="guilabel"><strong>初回ログイン時にホームディレクトリーを作成する</strong></span> — 有効にされているとき、ユーザーがログインしたときにホームディレクトリーが存在しないと、自動的に作成されます。
+ </div><h4 id="idm119662480">スマート カードの認証オプション</h4><a id="idm83400192" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>スマートカードのサポートの有効化</strong></span> — このオプションによりスマートカード認証が有効化されます。スマートカード認証により、スマートカードと関連した証明書およびキーを使用してログインできます。
+ </div><div class="para">
+ <span class="guilabel"><strong>スマートカードのサポートの有効化</strong></span> オプションがチェックされているとき、以下のオプションが指定できます:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>カード抜き取り動作</strong></span> — このオプションは、カードが有効な間にカードリーダーから抜き取られたときに、システムが実行する動作を定義します。2 つの代替が利用可能です:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Ignore</strong></span> — カードの取り出しが無視され、システムは通常どおり動作し続けます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Lock</strong></span> — 現在のセッションがただちにロックされます。
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>スマートカードログインの要求</strong></span> — ユーザーにスマートカードを用いたログインと認証をするよう要求します。本質的に他の種類のパスワード認証を無効化します。このオプションは、スマートカードを使用して正常にログインした後、選択されません。
+ </div></li></ul></div>
+
+ </div><div class="para">
+ <span class="package">pam_pkcs11</span> および <span class="package">coolkey</span> パッケージはこのオプションが機能するためにインストールされている必要があります。スマートカードに関する詳細は Red Hat Enterprise Linux 6 <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Managing_Smart_Cards/enabling-smart-card-login.html">Managing Single Sign-On and Smart Cards Guide</a> を参照してください。
+ <div class="note"><div class="admonition_header"><h2>前の設定を復元するには Revert をクリックする</h2></div><div class="admonition"><div class="para">
+ <span class="guibutton"><strong>復元</strong></span>をクリックすることにより、<span class="application"><strong>認証設定ツール</strong></span>において指定されたオプションを前に設定した内容にすべて復元できます。
+ </div></div></div>
+
+ </div></div><div class="section" id="sect-The_Authentication_Configuration_Tool-Command_Line_Version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.3. コマンドライン版</h3></div></div></div><a id="idm74788928" class="indexterm"></a><div class="para">
+ <span class="application"><strong>認証設定</strong></span>ツールはコマンドラインインターフェースもサポートします。コマンドラインのバージョンは、設定スクリプトまたは kickstart スクリプトにおいて使用できます。認証オプションは<a class="xref" href="#tb-authconfig-cmd-line">表9.1「コマンドラインのオプション」</a>にまとめられています。
+ </div><div class="note"><div class="admonition_header"><h2>サポートされる認証オプションの一覧取得方法</h2></div><div class="admonition"><div class="para">
+ これらのオプションは、<code class="command">authconfig</code> マニュアルページ、またはシェルプロンプトにおいて <code class="command">authconfig --help</code> と入力することにより、参照できます。
+ </div></div></div><div class="table" id="tb-authconfig-cmd-line"><h6>表9.1 コマンドラインのオプション</h6><div class="table-contents"><table summary="コマンドラインのオプション" border="1"><colgroup><col width="60%" class="option" /><col width="40%" class="description" /></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">--enableshadow, --useshadow</code>
+ </td><td class="">
+ シャドウパスワードを有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disableshadow</code>
+ </td><td class="">
+ シャドウパスワードを解除する
+ </td></tr><tr><td class="">
+ <code class="command">--passalgo=<em class="replaceable"><code>descrypt|bigcrypt|md5|sha256|sha512</code></em></code>
+ </td><td class="">
+ 使用されるハッシュ/暗号アルゴリズム
+ </td></tr><tr><td class="">
+ <code class="command">--enablenis</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの NIS を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablenis</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの NIS を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--nisdomain=<em class="replaceable"><code>domain</code></em> </code>
+ </td><td class="">
+ NIS ドメインを指定する
+ </td></tr><tr><td class="">
+ <code class="command">--nisserver=<em class="replaceable"><code>server</code></em> </code>
+ </td><td class="">
+ NIS サーバーを指定する
+ </td></tr><tr><td class="">
+ <code class="command">--enableldap</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの LDAP を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disableldap</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの LDAP を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enableldaptls</code>
+ </td><td class="">
+ LDAP で TLS の使用を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disableldaptls</code>
+ </td><td class="">
+ LDAP で TLS の使用を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablerfc2307bis</code>
+ </td><td class="">
+ LDAP ユーザー情報の検索のために RFC-2307bis スキーマの使用を有効にします
+ </td></tr><tr><td class="">
+ <code class="command">--disablerfc2307bis</code>
+ </td><td class="">
+ LDAP ユーザー情報の検索のために RFC-2307bis スキーマの使用を無効にします
+ </td></tr><tr><td class="">
+ <code class="command">--enableldapauth</code>
+ </td><td class="">
+ 認証の LDAP を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disableldapauth</code>
+ </td><td class="">
+ 認証の LDAP を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--ldapserver=<em class="replaceable"><code>server</code></em> </code>
+ </td><td class="">
+ LDAP サーバーを指定する
+ </td></tr><tr><td class="">
+ <code class="command">--ldapbasedn=<em class="replaceable"><code>dn</code></em> </code>
+ </td><td class="">
+ LDAP ベース DN (Distinguished Name) を指定します
+ </td></tr><tr><td class="">
+ <code class="command">--ldaploadcacert=<em class="replaceable"><code>URL</code></em> </code>
+ </td><td class="">
+ 指定された CA 証明書を読み込みます
+ </td></tr><tr><td class="">
+ <code class="command">--enablekrb5</code>
+ </td><td class="">
+ 認証のために Kerberos を有効にします
+ </td></tr><tr><td class="">
+ <code class="command">--disablekrb5</code>
+ </td><td class="">
+ 認証のために Kerberos を無効にします
+ </td></tr><tr><td class="">
+ <code class="command">--krb5kdc=<em class="replaceable"><code>server</code></em> </code>
+ </td><td class="">
+ Kerberos KDC サーバーを指定します
+ </td></tr><tr><td class="">
+ <code class="command">--krb5adminserver=<em class="replaceable"><code>server</code></em> </code>
+ </td><td class="">
+ Kerberos の管理サーバーを指定する
+ </td></tr><tr><td class="">
+ <code class="command">--krb5realm=<em class="replaceable"><code>realm</code></em> </code>
+ </td><td class="">
+ Kerberos の realm を指定する
+ </td></tr><tr><td class="">
+ <code class="command">--enablekrb5kdcdns</code>
+ </td><td class="">
+ Kerberos KDC の検索に DNS の使用を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablekrb5kdcdns</code>
+ </td><td class="">
+ Kerberos KDC の検索に DNS の使用を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablekrb5realmdns</code>
+ </td><td class="">
+ Kerberos realm の検索に DNS の使用を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablekrb5realmdns</code>
+ </td><td class="">
+ Kerberos realm の検索に DNS の使用を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablewinbind</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの winbind を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablewinbind</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの winbind を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablewinbindauth</code>
+ </td><td class="">
+ 認証で winbindauth を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablewinbindauth</code>
+ </td><td class="">
+ 認証で winbindauth を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--winbindseparator=<em class="replaceable"><code>\</code></em> </code>
+ </td><td class="">
+ <code class="command">winbindusedefaultdomain</code> が有効になっていない場合に、winbind ユーザー名のドメイン部分とユーザー部分を分離するために使用する文字です
+ </td></tr><tr><td class="">
+ <code class="command">--winbindtemplatehomedir=<em class="replaceable"><code>/home/%D/%U</code></em> </code>
+ </td><td class="">
+ winbind ユーザーがホームとするディレクトリ
+ </td></tr><tr><td class="">
+ <code class="command">--winbindtemplateprimarygroup=<em class="replaceable"><code>nobody</code></em> </code>
+ </td><td class="">
+ winbind ユーザーが最初のグループとするグループ
+ </td></tr><tr><td class="">
+ <code class="command">--winbindtemplateshell=<em class="replaceable"><code>/bin/false</code></em> </code>
+ </td><td class="">
+ winbind ユーザーがログインシェルの初期値とするシェル
+ </td></tr><tr><td class="">
+ <code class="command">--enablewinbindusedefaultdomain</code>
+ </td><td class="">
+ ユーザー名にドメインのないユーザーはドメイン ユーザーであると winbind に仮定させる
+ </td></tr><tr><td class="">
+ <code class="command">--disablewinbindusedefaultdomain</code>
+ </td><td class="">
+ ユーザー名にドメインのないユーザーはドメイン ユーザーではないと winbind に仮定させる
+ </td></tr><tr><td class="">
+ <code class="command">--winbindjoin=<em class="replaceable"><code>Administrator</code></em> </code>
+ </td><td class="">
+ 指定された管理者として winbind ドメインまたは ADS レルムに参加します。
+ </td></tr><tr><td class="">
+ <code class="command">--enablewinbindoffline</code>
+ </td><td class="">
+ オフライン ログインを許可する winbind の設定
+ </td></tr><tr><td class="">
+ <code class="command">--disablewinbindoffline</code>
+ </td><td class="">
+ オフライン ログインを防ぐ winbind の設定
+ </td></tr><tr><td class="">
+ <code class="command">--smbsecurity=<em class="replaceable"><code>user|server|domain|ads</code></em></code>
+ </td><td class="">
+ Samba および Winbind サービスに対して使用するセキュリティモードです
+ </td></tr><tr><td class="">
+ <code class="command">--smbrealm=<em class="replaceable"><code>realm</code></em></code>
+ </td><td class="">
+ <span class="guilabel"><strong>security</strong></span> が <span class="guimenuitem"><strong>ads</strong></span> に設定されているとき、Samba および Winbind サービスの初期レルムです。
+ </td></tr><tr><td class="">
+ <code class="command">--enablewins</code>
+ </td><td class="">
+ ホスト名解決で Wins を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablewins</code>
+ </td><td class="">
+ ホスト名解決で Wins を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablesssd</code>
+ </td><td class="">
+ ユーザー情報の SSSD を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablesssd</code>
+ </td><td class="">
+ ユーザー情報の SSSD を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablecache</code>
+ </td><td class="">
+ <code class="command">nscd</code> を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablecache</code>
+ </td><td class="">
+ <code class="command">nscd</code> を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablelocauthorize</code>
+ </td><td class="">
+ ローカル認証はローカルユーザーに対して十分です。
+ </td></tr><tr><td class="">
+ <code class="command">--disablelocauthorize</code>
+ </td><td class="">
+ ローカルユーザーはリモートサービスを用いても認証されます。
+ </td></tr><tr><td class="">
+ <code class="command">--enablesysnetauth</code>
+ </td><td class="">
+ ネットワーク サービスでシステム アカウントを認証する
+ </td></tr><tr><td class="">
+ <code class="command">--disablesysnetauth</code>
+ </td><td class="">
+ ローカルのファイルのみでシステム アカウントを認証する
+ </td></tr><tr><td class="">
+ <code class="command">--enablepamaccess</code>
+ </td><td class="">
+ アカウントの認可中に <code class="filename">/etc/security/access.conf</code> をチェックします
+ </td></tr><tr><td class="">
+ <code class="command">--disablepamaccess</code>
+ </td><td class="">
+ アカウント認可中に <code class="filename">/etc/security/access.conf</code> を確認しません
+ </td></tr><tr><td class="">
+ <code class="command">--enablemkhomedir</code>
+ </td><td class="">
+ 初回ログイン時にユーザーのホームディレクトリーを作成します
+ </td></tr><tr><td class="">
+ <code class="command">--disablemkhomedir</code>
+ </td><td class="">
+ 初回ログイン時にユーザーのホームディレクトリーを作成しません
+ </td></tr><tr><td class="">
+ <code class="command">--enablesmartcard</code>
+ </td><td class="">
+ スマートカードでの認証を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablesmartcard</code>
+ </td><td class="">
+ スマートカードでの認証を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablerequiresmartcard</code>
+ </td><td class="">
+ 認証にスマートカードを要求する
+ </td></tr><tr><td class="">
+ <code class="command">--disablerequiresmartcard</code>
+ </td><td class="">
+ 認証にスマートカードを要求しない
+ </td></tr><tr><td class="">
+ <code class="command">--smartcardmodule=<em class="replaceable"><code>module</code></em></code>
+ </td><td class="">
+ 標準でスマートカードを使う
+ </td></tr><tr><td class="">
+ <code class="command">--smartcardaction=<em class="replaceable"><code>0=ロック|1=無視</code></em></code>
+ </td><td class="">
+ スマートカードの抜き取りを検知したときのアクションです
+ </td></tr><tr><td class="">
+ <code class="command">--enablefingerprint</code>
+ </td><td class="">
+ 指紋認証を有効にします
+ </td></tr><tr><td class="">
+ <code class="command">--disablefingerprint</code>
+ </td><td class="">
+ 指紋認証を無効にします
+ </td></tr><tr><td class="">
+ <code class="command">--nostart</code>
+ </td><td class="">
+ <code class="command">portmap</code>, <code class="command">ypbind</code>, または <code class="command">nscd</code> サービスが設定されているときでも、それらを開始または停止しません
+ </td></tr><tr><td class="">
+ <code class="command">--test</code>
+ </td><td class="">
+ 新しい設定の表示のみで設定ファイルの更新をしない
+ </td></tr><tr><td class="">
+ <code class="command">--update, --kickstart</code>
+ </td><td class="">
+ <code class="command">--test</code> と反対に、変更された設定で設定ファイルを更新します
+ </td></tr><tr><td class="">
+ <code class="command">--updateall</code>
+ </td><td class="">
+ 全設定ファイルを更新する
+ </td></tr><tr><td class="">
+ <code class="command">--probe</code>
+ </td><td class="">
+ ネットワークデフォルトを調査して表示する
+ </td></tr><tr><td class="">
+ <code class="command">--savebackup=<em class="replaceable"><code>name</code></em></code>
+ </td><td class="">
+ 全設定ファイルのバックアップを保存する
+ </td></tr><tr><td class="">
+ <code class="command">--restorebackup=<em class="replaceable"><code>name</code></em></code>
+ </td><td class="">
+ 全設定ファイルのバックアップを復元する
+ </td></tr><tr><td class="">
+ <code class="command">--restorelastbackup</code>
+ </td><td class="">
+ これまでの設定変更の前に保存された設定ファイルのバックアップを復元します
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div xml:lang="ja-JP" class="section" id="chap-SSSD_User_Guide-Introduction" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.2. The System Security Services Daemon (SSSD)</h2></div></div></div><div class="para">
+ This section provides an introduction to the <em class="firstterm">System Security Services Daemon (SSSD)</em>, the main features that it provides, and discusses the requirements and any limitations of a typical SSSD deployment.
+ </div><div class="para">
+ This section also describes how to configure SSSD, and how to use the features that it provides. It provides information on the types of services that it supports and how to configure them, and introduces and describes the most important configuration options. Sample configuration files are also provided to help you optimize your deployment.
+ </div><div class="section" id="sect-SSSD_User_Guide-Introduction-What_is_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.1. SSIDとは?</h3></div></div></div><div class="para">
+ The System Security Services Daemon (SSSD) is a service which provides access to different identity and authentication providers. You can configure SSSD to use a native LDAP domain (that is, an LDAP identity provider with LDAP authentication), or an LDAP identity provider with Kerberos authentication. It provides an NSS and PAM interface to the system, and a pluggable back-end system to connect to multiple different account sources.
+ </div><div class="para">
+ SSSD is also extensible; you can configure it to use new identity sources and authentication mechanisms should they arise. In addition, SSSD is fully IPv6-compatible, provided that it is built against <span class="package">c-ares 1.7.1</span> or later and <span class="package">krb5-libs 1.8.1</span> or later.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Introduction-SSSD_Features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.2. SSIDの特徴</h3></div></div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Offline_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.1. オフライン認証</h4></div></div></div><div class="para">
+ One of the primary benefits of SSSD is offline authentication. This solves the case of users having a separate corporate account and a local machine account because of the common requirement to implement a Virtual Private Network (<abbr class="abbrev">VPN</abbr>).
+ </div><div class="para">
+ SSSD can cache remote identities and authentication credentials. This means that you can still authenticate with these remote identities even when a machine is offline. In an SSSD system, you only need to manage one account.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Server_Load_Reduction"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.2. Server Load Reduction</h4></div></div></div><div class="para">
+ The use of SSSD also helps to reduce the load on identification servers. For example, using <span class="package">nss_ldap</span>, every client application that needs to request user information opens its own connection to the LDAP server. Managing these multiple connections can lead to a heavy load on the LDAP server. In an SSSD system, only the SSSD Data Provider process actually communicates with the LDAP server, reducing the load to one connection per client system.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.3. Support for Multiple Domains</h4></div></div></div><a id="idm123391440" class="indexterm"></a><div class="para">
+ You can use SSSD to specify multiple domains of the same type. Compare this to an <code class="filename">nsswitch.conf</code> file configuration, with which you can only request user information from a single server of any particular type (LDAP, NIS, etc.). With SSSD, you can create multiple domains of the same, or of different types of identity provider.
+ </div><div class="para">
+ Beginning with version 0.6.0, SSSD maintains a separate database file for each domain. This means that each domain has its own cache, and in the event that problems occur and maintenance is necessary, it is very easy to purge the cache for a single domain, by stopping <code class="systemitem">sssd</code> and deleting the corresponding cache file. These cache files are stored in the <code class="filename">/var/lib/sss/db/</code> directory.
+ </div><div class="para">
+ All cache files are named according to the domain that they represent, for example <code class="filename">cache_<em class="replaceable"><code>DOMAINNAME</code></em>.ldb</code>.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm130018576">Considerations Associated with Deleting Cache Files</h5><a id="idm130020000" class="indexterm"></a>
+ Deleting a domain's cache file can have some unexpected side effects. You should be aware of the following before you proceed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Deleting the cache file also deletes all user data (both identification and cached credentials). Consequently, you should not proceed unless you are online and can authenticate with your username against the domain's servers, because offline authentication will fail.
+ </div></li><li class="listitem"><div class="para">
+ If you are online and change your configuration to reference a different identity provider, SSSD will recognize users from both providers until the cached entries from the original provider time out.
+ </div><div class="para">
+ To avoid this situation, you can either purge the cache or use a different domain name for the new provider (this is the recommended practice). Changing the domain name means that when you restart SSSD it will create a new cache file (with the new name) and the old file will be ignored.
+ </div></li></ul></div></div><div class="section" id="idm83998832"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm83998832">9.2.2.4. Support for LDAP Referrals</h4></div></div></div><div class="para">
+ SSSD supports two types of LDAP referrals: object-level referrals and subtree referrals. These referral types and the extent of SSSD support is outlined below.
+ </div><div class="section" id="idm120088768"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm120088768">9.2.2.4.1. Object-level Referrals</h5></div></div></div><div class="para">
+ SSSD provides full support for object-level referrals within the same LDAP server, correctly handling any differences in the distinguished name (DN) that might exist as part of the LDAP server referral configuration.
+ </div><div class="para">
+ SSSD provides partial support for object-level referrals between different LDAP servers, and requires that the full DN of an LDAP request be identical on each server. SSSD does not support referrals to different DN paths on other servers.
+ </div></div><div class="section" id="idm120090768"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm120090768">9.2.2.4.2. Subtree Referrals</h5></div></div></div><div class="para">
+ SSSD provides a similar level of support for subtree referrals as it does for object-level referrals. That is, it supports referrals to a changed DN on the local system or to an identical DN on a remote system. The difference with subtree referrals, however, is the ability to set up identical subtrees on each LDAP server and to then configure referrals between these subtrees.
+ </div></div><div class="section" id="idm55438496"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm55438496">9.2.2.4.3. Enabling LDAP Referrals</h5></div></div></div><div class="para">
+ To take advantage of the SSSD LDAP referral functionality, you need to set the <code class="option">ldap_referrals</code> option to <code class="literal">TRUE</code> in the LDAP domain configuration section of the <code class="filename">/etc/sssd/sssd.conf</code> file. This will enable anonymous access to the second LDAP server.
+ </div><div class="note"><div class="admonition_header"><h2>Make sure SSSD is compiled with OpenLDAP version 2.4.13 or later</h2></div><div class="admonition"><div class="para">
+ SSSD only supports LDAP referrals when it is compiled with OpenLDAP version 2.4.13 or later.
+ </div></div></div></div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Differentiating_Like_named_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.5. Differentiating Like-named Users</h4></div></div></div><div class="para">
+ SSSD supports the differentiation of like-named users in different domains. For example, you can differentiate the user <code class="systemitem">kate</code> in the <code class="systemitem">ldap.example.com</code> domain from the user <code class="systemitem">kate</code> in the <code class="systemitem">ldap.myhome.com</code> domain. You can use SSSD to make requests using fully-qualified usernames. If you request information for <code class="systemitem">kate</code>, you will receive the information from whichever domain is listed first in the look-up order. If you request information for <code class="systemitem">kate at ldap.myhome.com</code>, however, you will receive the correct user information.
+ </div><div class="para">
+ SSSD also provides a <code class="option">filter_users</code> option, which you can use to exclude certain users from being fetched from the database. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for full details about this option.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Integration_with_IPA"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.6. IPAとの統合</h4></div></div></div><div class="para">
+ Beyond the offline authentication, multiple domain management and other features already described, SSSD is also designed to integrate with and enhance the functionality of IPA clients. In an environment with the latest version of IPA installed, SSSD provides additional functionality, including support for dynamic DNS updates, host-based access control, and password migration from an LDAP-only environment into the LDAP/Kerberos 5 environment employed by IPA.
+ </div><div class="section" id="idm97496160"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm97496160">9.2.2.6.1. ダイナミックDNSアップデートのサポート</h5></div></div></div><div class="para">
+ Because the IP address of IPA clients can change, SSSD provides the ability to dynamically update the client's DNS entry on the IPA server. Using a combination of Kerberos and GSS-TSIG (Generic Security Service Algorithm for Secret Key Transaction), IPA can determine the identity of the host machine, authenticate it, and allow that machine to edit its own DNS record. These changes are then stored in the LDAP back end.
+ </div><div class="note"><div class="admonition_header"><h2>Each IPA client can only edit its own DNS record</h2></div><div class="admonition"><div class="para">
+ Using this authentication system means that each IPA client can only edit its own DNS record; it cannot edit the DNS record of any other client.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm97498816">ダイナミックDNSアップデート設定</h5>
+ The SSSD configuration file provides two options used for setting up dynamic DNS updates: <code class="option">ipa_dyndns_update</code>, used to enable dynamic DNS updates; and <code class="option">ipa_dyndns_iface</code>, which specifies the interface whose IP address should be used for dynamic DNS updates.
+ </div><div class="para">
+ Refer to the <em class="citetitle">sssd-ipa</em> manual page for more information about these options, and how to configure dynamic DNS updates.
+ </div><div class="note"><div class="admonition_header"><h2>Support for dynamic DNS updates</h2></div><div class="admonition"><div class="para">
+ Support for dynamic DNS updates is only available on IPA version 2 or later, and with DNS correctly configured.
+ </div></div></div></div></div></div><div class="section" id="chap-SSSD_User_Guide-Setting_Up_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.3. Setting Up SSSD</h3></div></div></div><div class="para">
+ This section describes how to install SSSD, how to run the service, and how to configure it for each type of supported information provider.
+ </div><div class="section" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Installing_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.3.1. SSSDのインストール</h4></div></div></div><div class="para">
+ Run the following command to install SSSD and any dependencies, including the SSSD client:
+ </div><div class="para">
+ <code class="command"># yum install sssd</code>
+ </div><div class="para">
+ SSSD requires very few dependencies and should install very quickly, depending on the speed of your network connection.
+ </div><div class="section" id="sect-SSSD_User_Guide-Installing_SSSD-Upgrading_from_a_Previous_Version"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.1.1. Upgrading from a Previous Version</h5></div></div></div><div class="formalpara" id="form-SSSD_User_Guide-Upgrading_from_a_Previous_Version-Upgrading_Using_RPM_Packages"><h5 class="formalpara">Upgrading Using RPM Packages</h5>
+ If you are upgrading using RPM packages, the script will run automatically when you upgrade to the new version. This will upgrade the <code class="filename">/etc/sssd/sssd.conf</code> file to the new format, and copy the existing version to <code class="filename">/etc/sssd/sssd.conf.bak</code>.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Upgrading_from_a_Previous_Version-Upgrading_Manually"><h5 class="formalpara">Upgrading Manually</h5>
+ It may be necessary to run the upgrade script manually, either because you built SSSD from source files, or because you are using a platform that does not support the use of RPM packages. The synopsis for the script is as follows:
+ </div><div class="cmdsynopsis"><p id="idm120131024"><code class="command">upgrade_config.py</code> [
+ -f INFILE
+ ] [
+ -o OUTFILE
+ ] [
+ -verbose
+ ] [
+ --no-backup
+ ]</p></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>-f INFILE</code></em> — the configuration file to upgrade. If not specified, this defaults to <code class="filename">/etc/sssd/sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>-o OUTFILE</code></em> — the name of the upgraded configuration file. If not specified, this defaults to <code class="filename">/etc/sssd/sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>-verbose</code></em> — produce more verbose output during the upgrade process
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>--no-backup</code></em> — do not produce a back-up file. If not specified, this defaults to <code class="filename"><em class="parameter"><code>INFILE</code></em>.bak</code>
+ </div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Installing_SSSD-Starting_and_Stopping_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.1.2. Starting and Stopping SSSD</h5></div></div></div><div class="note"><div class="admonition_header"><h2>Starting SSSD for the first time</h2></div><div class="admonition"><div class="para">
+ Before you start SSSD for the first time, you need to configure at least one domain. Refer to <a class="xref" href="#chap-SSSD_User_Guide-Configuring_Domains">「Configuring Domains」</a> for information on how to configure an SSSD domain.
+ </div></div></div><div class="para">
+ You can use either the <code class="command">service</code> command or the <code class="filename">/etc/init.d/sssd</code> script to control SSSD. For example, run the following command to start <code class="systemitem">sssd</code>:
+ </div><div class="para">
+ <code class="command"># systemctl start sssd.service</code>
+ </div><div class="para">
+ By default, SSSD is configured not to start automatically. There are two ways to change this behavior; if you use the Authentication Configuration tool to configure SSSD, it will reconfigure the default behavior so that SSSD starts when the machine boots. Alternatively, you can use the <code class="command">systemctl</code> command, as follows:
+ </div><div class="para">
+ <code class="command"># systemctl enable sssd.service</code>
+ </div></div></div><div class="section" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Configuring_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.3.2. Configuring SSSD</h4></div></div></div><div class="para">
+ The global configuration of SSSD is stored in the <code class="filename">/etc/sssd/sssd.conf</code> file. This file consists of various sections, each of which contains a number of key/value pairs. Some keys accept multiple values; use commas to separate multiple values for such keys. This configuration file uses data types of <span class="type">string</span> (no quotes required), <span class="type">integer</span> and <span class="type">Boolean</span> (with values of <code class="literal">TRUE</code> or <code class="literal">FALSE</code>). Comments are indicated by either a hash sign (#) or a semicolon (;) in the first column. The following example illustrates some of this syntax:
+ </div><pre class="programlisting">[section]
+# Keys with single values
+key1 = value
+key2 = val2
+
+# Keys with multiple values
+key10 = val10,val11
+</pre><div class="note"><div class="admonition_header"><h2>Specifying a different configuration file</h2></div><div class="admonition"><div class="para">
+ You can use the <em class="parameter"><code>-c</code></em> (or <em class="parameter"><code>--config</code></em>) parameter on the command line to specify a different configuration file for SSSD.
+ </div></div></div><div class="para">
+ The format of the configuration file is described in <a class="xref" href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">「SSSD Configuration File Format」</a>
+ </div><div class="para">
+ Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more information on global SSSD configuration options.
+ </div><div class="section" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.2.1. Configuring NSS</h5></div></div></div><div class="para">
+ SSSD provides a new NSS module, <code class="systemitem">sssd_nss</code>, so that you can configure your system to use SSSD to retrieve user information. Edit the <code class="filename">/etc/nsswitch.conf</code> file for your system to use the <code class="systemitem">sss</code> name database. For example:
+ </div><pre class="programlisting">passwd: files sss
+group: files sss
+</pre></div><div class="section" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.2.2. Configuring PAM</h5></div></div></div><div class="warning"><div class="admonition_header"><h2>Be careful when changing your PAM configuration</h2></div><div class="admonition"><div class="para">
+ Use extreme care when changing your PAM configuration. A mistake in the PAM configuration file can lock you out of the system completely. Always back up your configuration files before performing any changes, and keep a session open so that you can revert any changes you make should the need arise.
+ </div></div></div><div class="para">
+ To enable your system to use SSSD for PAM, you need to edit the default PAM configuration file. On Fedora—based systems, this is the <code class="filename">/etc/pam.d/system-auth</code> file. Edit this file to reflect the following example, and then restart <code class="systemitem">sssd</code>:
+ </div><pre class="programlisting">#%PAM-1.0
+# This file is auto-generated.
+# User changes will be destroyed the next time authconfig is run.
+auth required pam_env.so
+auth sufficient pam_unix.so nullok try_first_pass
+auth requisite pam_succeed_if.so uid >= 500 quiet
+auth sufficient pam_sss.so use_first_pass
+auth required pam_deny.so
+
+account required pam_unix.so broken_shadow
+account sufficient pam_localuser.so
+account sufficient pam_succeed_if.so uid < 500 quiet
+account [default=bad success=ok user_unknown=ignore] pam_sss.so
+account required pam_permit.so
+
+password requisite pam_cracklib.so try_first_pass retry=3
+password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok
+password sufficient pam_sss.so use_authtok
+password required pam_deny.so
+
+session required pam_mkhomedir.so umask=0022 skel=/etc/skel/
+session optional pam_keyinit.so revoke
+session required pam_limits.so
+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
+session sufficient pam_sss.so
+session required pam_unix.so
+</pre><div class="section" id="idm131072000"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="idm131072000">9.2.3.2.2.1. Using Custom Home Directories with SSSD</h6></div></div></div><div class="para">
+ If your LDAP users have home directories that are not in <code class="filename">/home</code>, and if your system is configured to create home directories the first time your users log in, then these directories will be created with the wrong permissions. For example, instead of a typical home directory such as <code class="filename">/home/<username></code>, your users might have home directories that include their locale, such as <code class="filename">/home/<locale>/<username></code>. If this is true for your system, the following steps need to be taken (preemptively):
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Apply the correct SELinux context and permissions from the <code class="filename">/home</code> directory to the home directory that you use on your system. In the example above, the following command would achieve this result (replace the directory names with those that apply to your system):
+<pre class="screen"># semanage fcontext -a -e /home /home/locale</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ Ensure the <span class="package">oddjob-mkhomedir</span> package is installed on your system and then re-run the Authentication Configuration tool.
+ </div><div class="para">
+ This package provides the <code class="systemitem">pam_oddjob_mkhomedir.so</code> library, which the Authentication Configuration tool will then use to create your custom home directories. You need to use this library to create your home directories, and not the default <code class="systemitem">pam_mkhomedir.so</code> library, because the latter cannot create SELinux labels.
+ </div><div class="note"><div class="admonition_header"><h2>The pam_oddjob_mkhomedir and pam_mkhomedir libraries</h2></div><div class="admonition"><div class="para">
+ The Authentication Configuration tool will automatically use the <code class="systemitem">pam_oddjob_mkhomedir.so</code> library if it is available. Otherwise, it will default to using <code class="systemitem">pam_mkhomedir.so</code>.
+ </div></div></div></li></ol></div><div class="para">
+ If the preceding steps were not performed before the custom home directories were created, you can use the following commands to correct the permissions and SELinux contexts (again, replace the directory names with those that apply to your system):
+<pre class="screen"># semanage fcontext -a -e /home /home/locale
+# restorecon -R -v /home/locale</pre>
+
+ </div></div><div class="section" id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title">9.2.3.2.2.2. Using "include" Statements in PAM Configurations</h6></div></div></div><div class="para">
+ Recent PAM implementations allow you to use <code class="literal">include</code> statements in PAM configurations. For example:
+ </div><pre class="programlisting">...
+session include system-auth
+session optional pam_console.so
+...
+</pre><div class="para">
+ In the preceding example, if a <em class="parameter"><code>sufficient</code></em> condition from <code class="filename">system-auth</code> returns <span class="returnvalue">PAM_SUCCESS</span>, <code class="filename">pam_console.so</code> will not be executed.
+ </div></div></div><div class="section" id="idm115611856"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm115611856">9.2.3.2.3. Configuring Access Control</h5></div></div></div><a id="idm108695792" class="indexterm"></a><div class="para">
+ SSSD provides a rudimentary access control mechanism, offering two solutions based on the value of the <code class="option">access_provider</code> option in the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> section in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="section" id="idm121783856"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="idm121783856">9.2.3.2.3.1. The Simple Access Provider</h6></div></div></div><div class="para">
+ The first of these solutions is known as the <em class="firstterm">Simple Access Provider</em>, and is based on the implementation of access or deny lists of usernames. To enable the Simple Access Provider, you need to set the <code class="option">access_provider</code> option to <code class="literal">simple</code>, and then add usernames as a comma-separated list to either the <code class="option">simple_allow_users</code> or <code class="option">simple_deny_users</code> options.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm59259984">Using the Simple Access Provider</h5>
+ By using the Simple Access Provider, you can continue to support a number of network logins to maintain common network accounts on company or department laptops, but you might want to restrict the use of a particular laptop to one or two users. This means that even if a different user authenticated successfully against the same authentication provider, the Simple Access Provider would prevent that user from gaining access.
+ </div><div class="para">
+ The following example demonstrates the use of the Simple Access Provider to grant access to two users. This example assumes that SSSD is correctly configured and <code class="systemitem">example.com</code> is one of the domains specified in the <code class="literal">[sssd]</code> section, and only shows the Simple Access Provider-specific options.
+ </div><pre class="screen">[domain/example.com]
+access_provider = simple
+simple_allow_users = user1, user2</pre><div class="note"><div class="admonition_header"><h2>Using the Local ID provider</h2></div><div class="admonition"><div class="para">
+ The Local ID provider does not support <code class="option">simple</code> as an access provider.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm134093232">Access Control Rules</h5><a id="idm123822320" class="indexterm"></a>
+ The Simple Access Provider adheres to the following three rules to determine which users should or should not be granted access:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If both lists are empty, access is granted.
+ </div></li><li class="listitem"><div class="para">
+ If <code class="option">simple_allow_users</code> is set, only users from this list are allowed access. This setting supersedes the <code class="option">simple_deny_users</code> list (which would be redundant).
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="option">simple_allow_users</code> list is empty, users are allowed access unless they appear in the <code class="option">simple_deny_users</code> list.
+ </div></li></ul></div>
+ <div class="important"><div class="admonition_header"><h2>Do not define both simple_allow_users and simple_deny_users</h2></div><div class="admonition"><div class="para">
+ Defining both <code class="option">simple_allow_users</code> and <code class="option">simple_deny_users</code> is a configuration error. If this occurs, SSSD will output an error to the <code class="filename">/var/log/sssd/sssd_default.log</code> log file when loading the back end, but continue to start normally. Future versions of SSSD will output an error and fail to start.
+ </div></div></div>
+
+ </div></div><div class="section" id="idm112203168"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="idm112203168">9.2.3.2.3.2. The LDAP Access Provider</h6></div></div></div><div class="para">
+ The second access control solution uses the LDAP server itself as the access provider (<code class="option">access_provider=ldap</code>) and the associated filter option (<code class="option">ldap_access_filter</code>) to specify which users are granted access to the specified host. Note that these two options are codependent; if you use LDAP as your access provider then you must specify a value for the <code class="option">ldap_access_filter</code> option, otherwise all users will be denied access. If you are not using LDAP as your access provider, then the <code class="option">ldap_access_filter</code> option has no effect.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm89200208">Using the LDAP Access Provider</h5>
+ The following example demonstrates the use of the LDAP Access Provider to grant access to members of the "allowedusers" group in LDAP. This example assumes that SSSD is correctly configured and <code class="systemitem">example.com</code> is one of the domains specified in the <code class="literal">[sssd]</code> section, and only shows the LDAP Access Provider-specific options.
+ </div><pre class="screen">[domain/example.com]
+access_provider = ldap
+ldap_access_filter = memberOf=cn=allowedusers,ou=Groups,dc=example,dc=com</pre><div class="note"><div class="admonition_header"><h2>Using offline caching</h2></div><div class="admonition"><div class="para">
+ Offline caching for this feature is limited to determining whether or not the user's last online login attempt was successful. If they were granted access during their last login, they will continue to be granted access while offline, and vice-versa.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">sssd-ldap</em> manual page for more information about using the LDAP Access Provider.
+ </div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.2.4. Configuring Failover</h5></div></div></div><div class="para">
+ The failover feature allows back ends to automatically switch to a different server if the primary server fails. These servers are entered as a case-insensitive, comma-separated list in the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> sections of the <code class="filename">/etc/sssd/sssd.conf</code> file, and listed in order of preference. This list can contain any number of servers.
+ </div><div class="para">
+ For example, if you have configured a native LDAP domain, you could specify the following as your <em class="parameter"><code>ldap_uri</code></em> values:
+ </div><pre class="screen">ldap_uri = ldap://ldap0.mydomain.org, ldap://ldap1.mydomain.org, ldap://ldap2.mydomain.org</pre><div class="para">
+ In this configuration, <code class="uri">ldap://ldap0.mydomain.org</code> functions as the primary server. If this server fails, the SSSD failover mechanism first attempts to connect to <code class="uri">ldap1.mydomain.org</code>, and if that server is unavailable, it then attempts to connect to <code class="uri">ldap2.mydomain.org</code>.
+ </div><div class="para">
+ If the parameter that specifies which server to connect to for the specific domain (for example, <em class="parameter"><code>ldap_uri</code></em>, <em class="parameter"><code>krb5_server</code></em>, …) is not specified, the back end defaults to using <em class="replaceable"><code>Use service discovery</code></em>. Refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">「Using SRV Records with Failover」</a> for more information on service discovery.
+ </div><div class="important"><div class="admonition_header"><h2>Do not use multiple ldap_uri parameters</h2></div><div class="admonition"><div class="para">
+ Do not use multiple <em class="parameter"><code>ldap_uri</code></em> parameters to specify your failover servers. The failover servers must be entered as a comma-separated list of values for a single <em class="parameter"><code>ldap_uri</code></em> parameter. If you enter multiple <em class="parameter"><code>ldap_uri</code></em> parameters, SSSD only recognizes the last entry.
+ </div><div class="para">
+ Future versions of SSSD will throw an error upon receiving additional <em class="parameter"><code>ldap_uri</code></em> entries.
+ </div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title">9.2.3.2.4.1. Using SRV Records with Failover</h6></div></div></div><div class="para">
+ SSSD also supports the use of SRV records in its failover configuration. This means that you can specify a server that is later resolved into a list of specific servers using SRV requests. The <em class="parameter"><code>priority</code></em> and <em class="parameter"><code>weight</code></em> attributes of SRV records provide further opportunity for specifying which servers should be contacted first in the event that the primary server fails.
+ </div><div class="para">
+ For every service with which you want to use service discovery, you need to add a special DNS record to your DNS server using the following form:
+ </div><pre class="screen">_<em class="replaceable"><code>service</code></em>._<em class="replaceable"><code>protocol</code></em>._<em class="replaceable"><code>domain TTL priority weight port hostname</code></em>
+</pre><div class="para">
+ A typical configuration would contain multiple such records, each with a different priority (for failover) and different weights (for load balancing).
+ </div><div class="para">
+ The client then makes an SRV DNS query to retrieve a list of host names, their priorities, and weights. These queries are of the form _<em class="replaceable"><code>service</code></em>._<em class="replaceable"><code>protocol</code></em>._<em class="replaceable"><code>domain</code></em>, for example, <code class="literal">_ldap._tcp._redhat.com</code>. The client then sorts this list according to the priorities and weights, and connects to the first server in this sorted list.
+ </div><div class="para">
+ For more information on SRV records, refer to <a href="http://tools.ietf.org/html/rfc2782">RFC 2782</a>.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-How_the_Failover_Mechanism_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title">9.2.3.2.4.2. How the Failover Mechanism Works</h6></div></div></div><div class="para">
+ The failover mechanism distinguishes between machines and services. The back end first tries to resolve the hostname of a given machine; if this resolution attempt fails, the machine is considered offline. No further attempts are made to connect to this machine for any other service. If the resolution attempt succeeds, the back end tries to connect to a service on this machine. If the service connection attempt fails, then only this particular service is considered offline and the back end automatically switches over to the next service. The machine is still considered online and might still be tried for another service.
+ </div><div class="para">
+ The failover mechanism does not handle DNS A records with multiple IP addresses; instead it only uses the first address. DNS round-robin cannot be used for failover. Further, providing multiple A records does not provide failover. Only the first A record is used, and if a lookup attempt on the first record fails then the system attempts no further lookups. To find multiple servers with a single request, and thus implementing failover, SSSD relies on SRV resource records, as explained in <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">「Using SRV Records with Failover」</a>.
+ </div><div class="para">
+ Further connection attempts are made to machines or services marked as offline after a specified period of time; this is currently hard coded to 30 seconds. If there are no more machines to try, the back end as a whole switches to offline mode, and then attempts to reconnect every 30 seconds.
+ </div></div></div></div></div><div class="section" id="chap-SSSD_User_Guide-Configuring_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.4. サービスの設定</h3></div></div></div><div class="para">
+ Individual pieces of SSSD functionality are provided by special SSSD services that are started and stopped together with SSSD. The services provided by SSSD have their own configuration sections. The <code class="literal">[sssd]</code> section also lists the services that are active and should be started when <code class="systemitem">sssd</code> starts within the <code class="command">services</code> directive.
+ </div><div class="para">
+ SSSD currently provides several services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">NSS</code> — An NSS provider service that answers NSS requests from the <code class="systemitem">sssd_nss</code> module.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">PAM</code> — A PAM provider service that manages a PAM conversation through the <code class="systemitem">sssd_pam</code> PAM module.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">monitor</code> — A special service that monitors all other SSSD services, and starts or restarts them as needed. Its options are specified in the <code class="literal">[sssd]</code> section of the <code class="filename">/etc/sssd/sssd.conf</code> configuration file.
+ </div></li></ul></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Services-Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.4.1. Configuration Options</h4></div></div></div><div class="para">
+ The following sections cover the most important SSSD configuration options. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page that ships with SSSD for information on all the available configuration options.
+ </div><div class="section" id="sect-SSSD_User_Guide-Configuration_Options-General_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.4.1.1. General Configuration Options</h5></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">debug_level <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Sets the debug level for a particular service. This is a per-service setting (that is, it can appear in any of the <code class="literal">[service/<NAME>]</code> sections in the SSSD configuration file).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">reconnection_retries <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ In the event of a data provider crash or restart, this specifies the number of times that a service should attempt to reconnect.
+ </div><div class="note"><div class="admonition_header"><h2>DNS lookup of IPv6 addresses</h2></div><div class="admonition"><div class="para">
+ If a <code class="systemitem">DNS</code> lookup fails to return an <code class="systemitem">IPv4</code> address for a hostname, SSSD attempts to look up an <code class="systemitem">IPv6</code> address before returning a failure. Note that this only ensures that the async resolver identifies the correct address; there is currently a bug in the LDAP code that prevents SSSD from connecting to an LDAP server over IPv6. This is being investigated separately.
+ </div></div></div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Configuration_Options-NSS_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.4.1.2. NSS Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the <code class="systemitem">Name Service Switch (NSS)</code> service. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for full details about each option.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">enum_cache_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long (in seconds) <span class="package">sssd_nss</span> should cache enumerations (requests for information about all users).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_cache_nowait_percentage <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long <span class="package">sssd_nss</span> should return cached entries before initiating an out-of-band cache refresh (<code class="literal">0</code> disables this feature).
+ </div><div class="para">
+ You can configure the entry cache to automatically update entries in the background if they are requested beyond a percentage of the <code class="option">entry_cache_timeout</code> value for the domain.
+ </div><div class="para">
+ Valid values for this option are <code class="literal">0-99</code>, and represent a percentage of the <code class="option">entry_cache_timeout</code> value for each domain.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_negative_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long (in seconds) <span class="package">sssd_nss</span> should cache negative cache hits (that is, queries for invalid database entries, such as nonexistent ones) before asking the back end again.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">filter_users, filter_groups <span class="type">(string)</span> </code>
+ </div><div class="para">
+ Exclude certain users from being fetched from the sss NSS database. This is particularly useful for system accounts such as <code class="systemitem">root</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">filter_users_in_groups <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ If set to <code class="literal">TRUE</code>, specifies that users listed in the <code class="option">filter_users</code> list do not appear in group memberships when performing group lookups. If set to <code class="literal">FALSE</code>, group lookups return all users that are members of that group. If not specified, defaults to <code class="literal">TRUE</code>.
+ </div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Configuration_Options-PAM_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.4.1.3. PAM Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the <code class="systemitem">Pluggable Authentication Module (<acronym class="acronym">PAM</acronym>)</code> service.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">offline_credentials_expiration <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ If the authentication provider is offline, specifies for how long to allow cached log-ins (in days). This value is measured from the last successful online log-in. If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">offline_failed_login_attempts <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ If the authentication provider is offline, specifies how many failed log in attempts are allowed. If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">offline_failed_login_delay <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the time in minutes after the value of <code class="option">offline_failed_login_attempts</code> has been reached before a new log in attempt is possible.
+ </div><div class="para">
+ If set to <code class="literal">0</code>, the user cannot authenticate offline if the value of <code class="option">offline_failed_login_attempts</code> has been reached. Only a successful online authentication can re-enable offline authentication. If not specified, defaults to <code class="literal">5</code>.
+ </div></li></ul></div></div></div></div><div class="section" id="chap-SSSD_User_Guide-Configuring_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.5. Configuring Domains</h3></div></div></div><div class="para">
+ A domain is a database of user information. SSSD can use more than one domain at the same time, but at least one must be configured for SSSD to start. Using SSSD domains, it is possible to use several LDAP servers providing several unique namespaces. You can specify not only where users' identity information is stored, but how users authenticate against each of the specified domains.
+ </div><div class="para">
+ SSSD supports the following identity and authentication combinations:
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">LDAP/LDAP</span></dt><dd><div class="para">
+ This combination uses an LDAP back end as both the identity and authentication provider. For more information, refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">「Configuring an LDAP Domain」</a>.
+ </div></dd><dt class="varlistentry"><span class="term">LDAP/KRB5</span></dt><dd><div class="para">
+ This combination uses an LDAP back end as the identity provider, and uses Kerberos to provide authentication. For more information, refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">「Setting Up Kerberos Authentication」</a>.
+ </div></dd><dt class="varlistentry"><span class="term">proxy</span></dt><dd><div class="para">
+ Specifying a proxy identity or an authentication provider uses an existing NSS library or a customized PAM stack, but takes advantage of the SSSD caching mechanism. For more information, refer to <a class="xref" href="#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">「Configuring a Proxy Domain」</a>.
+ </div></dd></dl></div>
+
+ </div><div class="para">
+ The following example assumes that SSSD is correctly configured and FOO is one of the domains in the <code class="literal">[sssd]</code> section. This example shows only the configuration of Kerberos authentication; it does not include any identity provider.
+ </div><pre class="screen">[domain/FOO]
+auth_provider = krb5
+krb5_server = 192.168.1.1
+krb5_realm = EXAMPLE.COM</pre><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Domain_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.5.1. Domain Configuration Options</h4></div></div></div><div class="para">
+ You can add new domain configurations to the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> sections of the <code class="filename">/etc/sssd/sssd.conf</code> file, and then add the list of domains to the <em class="parameter"><code>domains</code></em> attribute of the <code class="literal">[sssd]</code> section, in the order you want them to be queried.
+ </div><div class="section" id="sect-SSSD_User_Guide-Domain_Configuration_Options-General_Domain_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.5.1.1. General Domain Configuration Options</h5></div></div></div><div class="para">
+ You can use the following configuration options in a domain configuration section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">min_id,max_id <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the UID and GID limits for the domain. If a domain contains entries that are outside these limits, they are ignored.
+ </div><div class="para">
+ The default value for <code class="option">min_id</code> is <code class="literal">1</code>; the default value for <code class="option">max_id</code> is <code class="literal">0</code> (unbounded).
+ </div><div class="important"><div class="admonition_header"><h2>Avoid conflicts with users in /etc/passwd</h2></div><div class="admonition"><div class="para">
+ If <code class="option">min_id</code> is unspecified, it defaults to <code class="literal">1</code> for any back end. This default was chosen to provide compatibility with existing systems and to ease any migration attempts. LDAP administrators should be aware that granting identities in this range may conflict with users in the local <code class="filename">/etc/passwd</code> file. To avoid these conflicts, <code class="option">min_id</code> should be set to <code class="literal">1000</code> or higher wherever possible.
+ </div><div class="para">
+ The <code class="option">min_id</code> option determines the minimum acceptable value for both UID and GID numbers. Accounts with either UID or GID values below the <code class="option">min_id</code> value are filtered out and not made available on the client.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">enumerate <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not to enumerate (list) the users and groups of a domain.
+ </div><div class="para">
+ Enumeration means that the entire set of available users and groups on the remote source is cached on the local machine. When enumeration is disabled, users and groups are only cached as they are requested.
+ </div><div class="warning"><div class="admonition_header"><h2>Disable enumeration for domains with many users and groups</h2></div><div class="admonition"><div class="para">
+ If a client has enumeration enabled, reinitialization of the client results in a complete refresh of the entire set of available users and groups from the remote source. Similarly, when SSSD is connected to a new server, the entire set of available users and groups from the remote source is pulled and cached on the local machine. In a domain with a large amount of clients connected to a remote source, both aforementioned cases can affect the network performance due to frequent queries from the clients. If the set of available users and groups is large enough, it will affect the performance of clients as well. For performance reasons, it is recommended that you disable enumeration for domains with many users and groups.
+ </div></div></div><div class="para">
+ The default value for this parameter is <code class="literal">FALSE</code>. Set this value to <code class="literal">TRUE</code> to enable enumeration of users and groups of a domain.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the timeout in seconds for this particular domain.
+ </div><div class="para">
+ This is used to ensure that the back end process is alive and capable of answering requests. The default value for this parameter is <code class="literal">10</code> seconds. Raising this timeout might prove useful for slower back ends, such as distant LDAP servers.
+ </div><div class="note"><div class="admonition_header"><h2>Changing the timeout value to 0</h2></div><div class="admonition"><div class="para">
+ If you set <code class="option">timeout = 0</code>, SSSD reverts to the default value; you cannot force a timeout value of zero, because this would force the <code class="systemitem">sssd</code> daemon into a loop.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">cache_credentials <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not to store user credentials in the local SSSD domain database cache.
+ </div><div class="para">
+ The default value for this parameter is <code class="literal">FALSE</code>. You should set this value to <code class="literal">TRUE</code> for domains other than local if you want to enable offline authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">id_provider <span class="type">(string)</span> </code>
+ </div><div class="para">
+ Specifies the data provider identity back end to use for this domain. Currently supported identity back ends are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ proxy — Support a legacy <code class="systemitem">NSS</code> provider (for example, <span class="package">nss_nis</span>).
+ </div><div class="note"><div class="admonition_header"><h2>Changing the id_provider value to proxy</h2></div><div class="admonition"><div class="para">
+ SSSD needs to know which legacy NSS library to load in order to start successfully. If you set <code class="option">id_provider</code> to <code class="literal">proxy</code>, ensure that you also specify a value for <code class="option">proxy_lib_name</code>. Refer to <a class="xref" href="#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">「Configuring a Proxy Domain」</a> for information on this attribute.
+ </div></div></div></li><li class="listitem"><div class="para">
+ local — <code class="systemitem">SSSD</code> internal local provider.
+ </div></li><li class="listitem"><div class="para">
+ ldap — <code class="systemitem">LDAP</code> provider.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_cache_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long the domain's data provider should cache positive cache hits (that is, queries for valid database entries) before asking the database again.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">use_fully_qualified_names <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not requests to this domain require fully-qualified domain names.
+ </div><div class="para">
+ If set to <code class="literal">TRUE</code>, all requests to this domain must use fully-qualified domain names. It also means that the output from the request displays the fully-qualified name.
+ </div><div class="para">
+ The ability to restrict requests in this way means that if you know you have multiple domains with conflicting usernames, then there is no doubt about which username the query will resolve.
+ </div><div class="para">
+ Consider the following examples, in which the IPA domain database contains a user named <code class="systemitem">ipauser01</code>, and the <em class="parameter"><code>use_fully_qualified_names</code></em> attribute is set to <code class="literal">TRUE</code>:
+ </div><pre class="screen">
+<code class="command"># getent passwd ipauser01</code>
+[no output]
+<code class="command"># getent passwd ipauser01 at IPA</code>
+ipauser01 at IPA:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+</pre><div class="para">
+ In the following examples, using the same IPA domain and user, the <em class="parameter"><code>use_fully_qualified_names</code></em> attribute is set to <code class="literal">FALSE</code>:
+ </div><pre class="screen">
+<code class="command"># getent passwd ipauser01</code>
+ipauser01:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+<code class="command"># getent passwd ipauser01 at IPA</code>
+ipauser01:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+</pre><div class="note"><div class="admonition_header"><h2>Changing the use_fully_qualified_names value to FALSE</h2></div><div class="admonition"><div class="para">
+ If <em class="parameter"><code>use_fully_qualified_names</code></em> is set to <code class="literal">FALSE</code>, you can continue to use the fully-qualified name in your requests, but only the simplified version is displayed in the output.
+ </div><div class="para">
+ SSSD can only parse <code class="systemitem">name at domain</code>, not <code class="systemitem">name at realm</code>. You can, however, use the same name for both your domain and your realm.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">auth_provider <span class="type">(string)</span> </code>
+ </div><div class="para">
+ The authentication provider used for the domain. The default value for this option is the value of <code class="option">id_provider</code> if it is set and can handle authentication requests.
+ </div><div class="para">
+ Currently supported authentication providers are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ldap — for native LDAP authentication. Refer to the sssd-ldap(5) manual page for more information on configuring LDAP.
+ </div></li><li class="listitem"><div class="para">
+ krb5 — for Kerberos authentication. Refer to the sssd-krb5(5) manual page for more information on configuring Kerberos.
+ </div></li><li class="listitem"><div class="para">
+ proxy — for relaying authentication to some other PAM target.
+ </div></li><li class="listitem"><div class="para">
+ none — explicitly disables authentication.
+ </div></li></ul></div>
+
+ </div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Proxy_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.5.1.2. Proxy Configuration Options</h5></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">proxy_pam_target</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">auth_provider</code> option is set to <code class="literal">proxy</code>, and specifies the target to which <acronym class="acronym">PAM</acronym> must proxy.
+ </div><div class="para">
+ This option has no default value. If proxy authentication is required, you need to specify your own <acronym class="acronym">PAM</acronym> target. This corresponds to a file containing <acronym class="acronym">PAM</acronym> stack information in the system's default <acronym class="acronym">PAM</acronym> configuration directory. On Fedora-based systems, this is the <code class="filename">/etc/pam.d/</code> directory.
+ </div><div class="important"><div class="admonition_header"><h2>Avoid recursive inclusion of pam_sss</h2></div><div class="admonition"><div class="para">
+ Ensure that your proxy PAM stack does <span class="emphasis"><em>not</em></span> recursively include <code class="filename">pam_sss.so</code>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">proxy_lib_name</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">id_provider</code> option is set to <code class="literal">proxy</code>, and specifies which existing NSS library to proxy identity requests through.
+ </div><div class="para">
+ This option has no default value. You need to manually specify an existing library to take advantage of this option. For example, set this value to <code class="literal">nis</code> to use the existing <code class="filename">libnss_nis.so</code> file.
+ </div></li></ul></div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.5.2. Configuring an LDAP Domain</h4></div></div></div><a id="idm130528096" class="indexterm"></a><div class="para">
+ An LDAP domain is one where the <code class="option">id_provider</code> option is set to <code class="literal">ldap</code> (<code class="option">id_provider = ldap</code>). Such a domain requires a running LDAP server against which to authenticate. This can be an open source LDAP server such as OpenLDAP or Microsoft Active Directory. SSSD currently supports Microsoft Active Directory 2003 (+Services for UNIX) and Active Directory 2008 (+Subsystem for UNIX-based Applications). In all cases, the client configuration is stored in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-How_to_Authenticate_Against_an_LDAP_Server"><h5 class="formalpara">How to Authenticate Against an LDAP Server</h5>
+ SSSD does not support authentication over an unencrypted channel. Consequently, if you want to authenticate against an LDAP server, either <code class="systemitem">TLS/SSL</code> or <code class="systemitem">LDAPS</code> is required. If the LDAP server is used only as an identity provider, an encrypted channel is not needed.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file to include the following settings:
+ </div><pre class="screen"># A native LDAP domain
+[domain/LDAP]
+enumerate = false
+cache_credentials = TRUE
+
+id_provider = ldap
+auth_provider = ldap
+ldap_schema = rfc2307
+chpass_provider = ldap
+
+ldap_uri = ldap://ldap.mydomain.org
+ldap_search_base = dc=mydomain,dc=org
+ldap_tls_reqcert = demand
+ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+</pre><div class="note"><div class="admonition_header"><h2>Creating a certificate with an IP address instead of the server name</h2></div><div class="admonition"><div class="para">
+ If you wish to use an IP address in the <code class="option">ldap_uri</code> option instead of the server name, for example, if <code class="systemitem">GSSAPI</code> is used to avoid time consuming <code class="systemitem">DNS</code> lookups, the <code class="systemitem">TSL</code>/<code class="systemitem">SSL</code> setup might fail. This is due to the fact that <code class="systemitem">TSL</code>/<code class="systemitem">SSL</code> certificates contain the server name only. However, a special field in the certificate, called <span class="emphasis"><em>Subject Alternative Name</em></span> (<code class="option">subjectAltName</code>), can be used to additionally set the IP address of the server.
+ </div><div class="para">
+ The following steps show how to create a certificate with a Subject Alternative Name being the IP address of your server:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Using your command line, execute the following command to convert an existing certificate (previously signed by the <em class="parameter"><code>key.pem</code></em> key) into a certificate request:
+ </div><pre class="screen">openssl x509 -x509toreq -in old_cert.pem -out req.pem -signkey key.pem</pre><div class="para">
+ Alternatively, if you are using a self-signed certificate(for example, one created by the Fedora OpenLDAP package in <code class="filename">/etc/pki/tls/certs/slapd.pem</code>), execute the following command:
+ </div><pre class="screen">openssl x509 -x509toreq -in old_cert.pem -out req.pem -signkey old_cert.pem</pre></li><li class="step"><div class="para">
+ Edit your <code class="filename">/etc/pki/tls/openssl.cnf</code> configuration file to include the following line under the <em class="parameter"><code>[ v3_ca ]</code></em> section:
+ </div><pre class="screen">subjectAltName = IP:10.0.0.10</pre><div class="para">
+ Replace the IP address with one of your choice.
+ </div></li><li class="step"><div class="para">
+ By executing the following command, use the previously generated certificate request to generate a new self-signed certificate that will contain your desired IP address:
+ </div><pre class="screen">openssl x509 -req -in req.pem -out new_cert.pem -extfile ./openssl.cnf -extensions v3_ca -signkey old_cert.pem</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="command">openssl x509</code> command creates the new certificate.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-req</code> option tells the command to expect a certificate request as an input.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-in</code> and <code class="option">-out</code> options specify the input and output files.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-extfile</code> option expects a file containing certificate extensions to use (in our case the <code class="option">subjectAltName</code> extension).
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-extensions</code> option specifies the section of the <code class="filename">openssl.cnf</code> file to add certificate extensions from (in this case, the <em class="parameter"><code>[ v3_ca ]</code></em> section).
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-signkey</code> option tells the command to self-sign the input file using the supplied private key.
+ </div></li></ul></div><div class="para">
+ For more information on the <span class="application"><strong>x509</strong></span> utility and its parameters, refer to <code class="command">man x509</code>.
+ </div></li><li class="step"><div class="para">
+ Lastly, copy the private key block from the <code class="filename">old_cert.pem</code> file into the <code class="filename">new_cert.pem</code> file to keep all relevant information in one file.
+ </div></li></ol></div><div class="para">
+ When creating a certificate through the <span class="application"><strong>certutil</strong></span> utility provided by the <span class="package">nss-utils</span> package, note that <span class="application"><strong>certutil</strong></span> supports <code class="systemitem">DNS</code> subject alternative names for certificate creation only.
+ </div><div class="para">
+ It is advisable to use a Certificate Authority to issue your certificate. Consider using the Red Hat Certificate System; for more information on managing subject names and subject alternative names in your certificate, refer to the <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Certificate_System/8.0/html/Admin_Guide/Managing_Subject_Names_and_Subject_Alternative_Names.html">Red Hat Certificate System Admin Guide</a>.
+ </div></div></div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-Selecting_an_LDAP_Schema"><h5 class="formalpara">Selecting an LDAP Schema</h5><a id="idm119846352" class="indexterm"></a>
+ You can set the <em class="parameter"><code>ldap_schema</code></em> attribute to either <code class="literal">rfc2307</code> or <code class="literal">rfc2307bis</code>. These schema define how groups in <acronym class="acronym">LDAP</acronym> are specified. In <em class="citetitle">RFC 2307</em>, group objects use a multi-valued attribute, <em class="parameter"><code>memberuid</code></em>, which lists the names of the users that belong to that group. In <em class="citetitle">RFC 2307bis</em>, instead of the <em class="parameter"><code>memberuid</code></em>, group objects use the <em class="parameter"><code>member</code></em> attribute. Rather than just the name of the user, this attribute contains the full Distinguished Name (DN) of another object in the LDAP database. This means that groups can have other groups as members. That is, it adds support for nested groups.
+ </div><div class="para">
+ SSSD assumes that your LDAP server is using <em class="citetitle">RFC 2307</em>. If your LDAP server is using <em class="citetitle">RFC 2307bis</em>, and you do not update the <code class="filename">/etc/sssd/sssd.conf</code> file accordingly, this can impact how your users and groups are displayed. It also means that some groups will not be available and network resources may be inaccessible even though you have permissions to use them.
+ </div><div class="para">
+ For example, when using <em class="citetitle">RFC 2307bis</em> and you have configured both primary and secondary groups, or are using nested groups, you can use the <code class="command">id</code> command to display these groups:
+ </div><pre class="screen">[f12server at ipaserver ~]$ id
+uid=500(f12server) gid=500(f12server) groups=500(f12server),510(f12tester)
+</pre><div class="para">
+ If instead you have configured your client to use <em class="citetitle">RFC 2307</em> then only the primary group is displayed.
+ </div><div class="para">
+ Changes to this setting only affect how SSSD determines the groups to which a user belongs; there is no negative effect on the actual user data. If you do not know the correct value for this attribute, consult your System Administrator.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-Specifying_Timeout_Values"><h5 class="formalpara">Specifying Timeout Values</h5><a id="idp1472160" class="indexterm"></a>
+ SSSD supports a number of timeout values that apply when configuring an <acronym class="acronym">LDAP</acronym> domain. These are described below.
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">ldap_search_timeout (integer)</code> — Specifies the timeout (in seconds) that <acronym class="acronym">LDAP</acronym> searches are allowed to run before they are canceled and cached results are returned (and offline mode is entered). If not specified:
+ </div><div class="para">
+ Defaults to five when <code class="option">enumerate</code> = <code class="literal">False</code>
+ </div><div class="para">
+ Defaults to 30 when <code class="option">enumerate</code> = <code class="literal">True</code>. This option is forced to a minimum of 30 in this case.
+ </div><div class="note"><div class="admonition_header"><h2>The ldap_network_timeout option is going to be changed</h2></div><div class="admonition"><div class="para">
+ This option is subject to change in future versions of SSSD, where it may be replaced by a series of timeouts for specific look-up types.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">ldap_network_timeout (integer)</code> — Specifies the timeout (in seconds) after which the <code class="function">poll(2)</code>/<code class="function">select(2)</code> following a <code class="function">connect(2)</code> returns in case of no activity.
+ </div><div class="para">
+ If not specified, defaults to five.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ldap_opt_timeout (integer)</code> — Specifies the timeout (in seconds) after which calls to synchronous <acronym class="acronym">LDAP</acronym> APIs will abort if no response is received. This option also controls the timeout when communicating with the KDC in case of a SASL bind.
+ </div><div class="para">
+ If not specified, defaults to five.
+ </div></li></ul></div>
+
+ </div><div class="note"><div class="admonition_header"><h2>DNS Service Discovery</h2></div><div class="admonition"><div class="para">
+ The <code class="systemitem">DNS</code> service discovery feature allows the LDAP back end to automatically find the appropriate <code class="systemitem">DNS</code> servers to connect to using a special <code class="systemitem">DNS</code> query. For more information on the <code class="systemitem">DNS</code> service discovery feature, refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">「Using SRV Records with Failover」</a>.
+ </div></div></div><h5 id="idm97530656"></h5><div class="para">
+
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.5.3. Configuring a Microsoft Active Directory Domain</h4></div></div></div><a id="idm134294688" class="indexterm"></a><div class="para">
+ You can configure SSSD to use Microsoft Active Directory as an LDAP back end, providing both identity and authentication services. If you are using Active Directory 2003, SSSD requires that you install Windows Services for UNIX (SFU) on the machine where Active Directory is installed. If instead you are using Active Directory 2008, you need to install the Subsystem for UNIX-based Applications (SUA) on the Active Directory machine.
+ </div><div class="note"><div class="admonition_header"><h2>SFU is not supported on 64-bit systems</h2></div><div class="admonition"><div class="para">
+ SFU is not supported on 64-bit operating systems. Refer to <a href="http://support.microsoft.com/kb/920751">http://support.microsoft.com/kb/920751</a> for more information about which Windows systems can provide a suitable platform for an SSSD LDAP back end.
+ </div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2003"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.5.3.1. Configuring Active Directory 2003 as an LDAP Back End</h5></div></div></div><div class="para">
+ The example <code class="filename">/etc/sssd/sssd.conf</code> file that ships with SSSD contains the following sample configuration for Active Directory 2003:
+ </div><pre class="screen"># Example LDAP domain where the LDAP server is an Active Directory 2003 server.
+
+[domain/AD]
+description = LDAP domain with AD server
+enumerate = false
+min_id = 1000
+;
+id_provider = ldap
+auth_provider = ldap
+ldap_uri = ldap://your.ad.server.com
+ldap_schema = rfc2307bis
+ldap_search_base = dc=example,dc=com
+ldap_default_bind_dn = cn=Administrator,cn=Users,dc=example,dc=com
+ldap_default_authtok_type = password
+ldap_default_authtok = YOUR_PASSWORD
+ldap_user_object_class = person
+ldap_user_name = msSFU30Name
+ldap_user_uid_number = msSFU30UidNumber
+ldap_user_gid_number = msSFU30GidNumber
+ldap_user_home_directory = msSFU30HomeDirectory
+ldap_user_shell = msSFU30LoginShell
+ldap_user_principal = userPrincipalName
+ldap_group_object_class = group
+ldap_group_name = msSFU30Name
+ldap_group_gid_number = msSFU30GidNumber</pre><div class="para">
+ This configuration is specific to Windows Active Directory 2003. Refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008">「Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends」</a> for information on how to configure Active Directory 2003 R2 and Active Directory 2008.
+ </div><div class="para">
+ Note that the above configuration assumes that the certificates are stored in the default location (that is, in <code class="filename">/etc/openldap/cacerts</code>) and that the <code class="function">c_rehash</code> function has been used to create the appropriate symlinks.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm126741856">More Information</h5>
+ Refer to the <em class="citetitle">sssd-ldap(5)</em> manual page for a full description of all the options that apply to <acronym class="acronym">LDAP</acronym> domains.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.5.3.2. Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends</h5></div></div></div><div class="para">
+ The configuration of <code class="filename">/etc/sssd/sssd.conf</code> to support Active Directory 2003 R2 or Active Directory 2008 as a back end is similar to that for AD 2003. The following example configuration highlights the necessary changes.
+ </div><pre class="screen"># Example LDAP domain where the LDAP server is an Active Directory 2003 R2 or an Active Directory 2008 server.
+
+[domain/AD]
+description = LDAP domain with AD server
+; debug_level = 9
+enumerate = false
+
+id_provider = ldap
+auth_provider = ldap
+chpass_provider = ldap
+
+ldap_uri = ldap://your.ad.server.com
+ldap_tls_cacertdir = /etc/openldap/cacerts
+ldap_tls_cacert = /etc/openldap/cacerts/test.cer
+ldap_search_base = dc=example,dc=com
+ldap_default_bind_dn = cn=Administrator,cn=Users,dc=example,dc=com
+ldap_default_authtok_type = password
+ldap_default_authtok = YOUR_PASSWORD
+ldap_pwd_policy = none
+ldap_user_object_class = user
+ldap_group_object_class = group</pre><div class="para">
+ Note that the above configuration assumes that the certificates are stored in the default location (that is, in <code class="filename">/etc/openldap/cacerts</code>) and that the <code class="function">c_rehash</code> function has been used to create the appropriate symlinks.
+ </div></div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.6. Setting Up Kerberos Authentication</h3></div></div></div><a id="idm111813440" class="indexterm"></a><div class="para">
+ In order to set up Kerberos authentication, you need to know the address of your <em class="firstterm">key distribution center</em> (KDC) and the Kerberos domain. The client configuration is then stored in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="para">
+ The Kerberos 5 authentication back end does not contain an identity provider and must be paired with one in order to function properly (for example, <code class="option">id_provider = ldap</code>). Some information required by the Kerberos 5 authentication back end must be supplied by the identity provider, such as the user's <em class="firstterm">Kerberos Principal Name</em> (UPN). The identity provider configuration should contain an entry to specify this UPN. Refer to the manual page for the applicable identity provider for details on how to configure the UPN.
+ </div><div class="para">
+ If the UPN is not available in the identity back end, SSSD will construct a UPN using the format <code class="systemitem">username at krb5_realm</code>.
+ </div><div class="para">
+ SSSD assumes that the Kerberos KDC is also a Kerberos kadmin server. However, it is very common for production environments to have multiple, read-only replicas of the KDC, but only a single kadmin server (because password changes and similar procedures are comparatively rare). To manage this type of configuration, you can use the <code class="option">krb5_kpasswd</code> option to specify where your password changing service is running, or if it is running on a non-default port. If the <code class="option">krb5_kpasswd</code> option is not defined, SSSD tries to use the Kerberos KDC in order to change the password. Refer to the <em class="citetitle">sssd-krb5(5)</em> manual page for more information about this and all Kerberos configuration options.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Setting_Up_Kerberos_Authentication-How_to_Set_up_Kerberos_Authentication"><h5 class="formalpara">How to Set Up Kerberos Authentication</h5>
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file to include the following settings:
+ </div><pre class="screen"># A domain with identities provided by LDAP and authentication by Kerberos
+[domain/KRBDOMAIN]
+enumerate = false
+id_provider = ldap
+chpass_provider = krb5
+ldap_uri = ldap://ldap.mydomain.org
+ldap_search_base = dc=mydomain,dc=org
+tls_reqcert = demand
+ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+
+auth_provider = krb5
+krb5_server = 192.168.1.1
+krb5_realm = EXAMPLE.COM
+krb5_changepw_principal = kadmin/changepw
+krb5_ccachedir = /tmp
+krb5_ccname_template = FILE:%d/krb5cc_%U_XXXXXX
+krb5_auth_timeout = 15
+</pre><div class="para">
+ This example describes the minimum options that must be configured when using Kerberos authentication. Refer to the <em class="citetitle">sssd-krb5(5)</em> manual page for a full description of all the options that apply to configuring Kerberos authentication.
+ </div><div class="note"><div class="admonition_header"><h2>DNS Service Discovery</h2></div><div class="admonition"><div class="para">
+ The <code class="systemitem">DNS</code> service discovery feature allows the Kerberos 5 authentication back end to automatically find the appropriate <code class="systemitem">DNS</code> servers to connect to using a special <code class="systemitem">DNS</code> query. For more information on the <code class="systemitem">DNS</code> service discovery feature, refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">「Using SRV Records with Failover」</a>.
+ </div></div></div><div class="section" id="sect-setting-up-sasl-gssapi-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.6.1. Setting up SASL/GSSAPI Authentication</h4></div></div></div><div class="para">
+ <em class="firstterm">GSSAPI</em> (Generic Security Services Application Programming Interface) is a supported <em class="firstterm">SASL</em> (Simple Authentication and Security Layer) authentication method. Kerberos is currently the only commonly used GSSAPI implementation. An LDAP client and an LDAP server use SASL to take advantage of GSSAPI as the authentication method (an alternative to plain text passwords, etc.). The GSSAPI plug-in for SASL is then invoked on the client and server side to use Kerberos to communicate.
+ </div><div class="para">
+ Using GSSAPI protected communication for LDAP is an advanced configuration not supported by the Authentication Configuration tool; the following steps show how to manually configure it.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">On the KDC</span></dt><dd><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Using <span class="application"><strong>kadmin</strong></span>, set up a Kerberos service principal for the directory server. Use the <code class="option">-randkey</code> option for the <span class="application"><strong>kadmin</strong></span>'s <code class="command">addprinc</code> command to create the principal and assign it a random key:
+ </div><pre class="screen">kadmin: addprinc -randkey ldap/server.example.com</pre></li><li class="listitem"><div class="para">
+ Use the <code class="command">ktadd</code> command to write the service principal to a file:
+ </div><pre class="screen">kadmin: ktadd -k /root/ldap.keytab ldap/server.example.com</pre></li><li class="listitem"><div class="para">
+ Using <span class="application"><strong>kadmin</strong></span>, set up a Kerberos host principal for the client running SSSD. Use the <code class="option">-randkey</code> option for the <span class="application"><strong>kadmin</strong></span>'s <code class="command">addprinc</code> command to create the principal and assign it a random key:
+ </div><pre class="screen">kadmin: addprinc -randkey host/client.example.com</pre></li><li class="listitem"><div class="para">
+ Use the <code class="command">ktadd</code> command to write the host principal to a file:
+ </div><pre class="screen">kadmin: ktadd -k /root/client.keytab host/client.example.com</pre></li></ol></div></dd><dt class="varlistentry"><span class="term">On the Directory Server</span></dt><dd><div class="para">
+ Complete the following steps for a directory server of your choice:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">OpenLDAP</span></dt><dd><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Copy the previously created <code class="filename">/root/ldap.keytab</code> file from the KDC to the <code class="filename">/etc/openldap/</code> directory and name it <code class="filename">ldap.keytab</code>.
+ </div></li><li class="listitem"><div class="para">
+ Make the <code class="filename">/etc/openldap/ldap.keytab</code> file read-writable for the <code class="systemitem">ldap</code> user and readable for the <code class="systemitem">ldap</code> group only.
+ </div></li></ol></div></dd><dt class="varlistentry"><span class="term">Red Hat Directory Server</span></dt><dd><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Copy the previously created <code class="filename">/root/ldap.keytab</code> file from the KDC to the <code class="filename">/etc/dirsrv/</code> directory and name it <code class="filename">ldap.keytab</code>.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="varname">KRB5_KTNAME</code> line in the <code class="filename">/etc/sysconfig/dirsrv</code> (or instance-specific) file, and set the keytab location for the <code class="varname">KRB5_KTNAME</code> variable. For example:
+<pre class="screen">
+# In order to use SASL/GSSAPI the directory
+# server needs to know where to find its keytab
+# file - uncomment the following line and set
+# the path and filename appropriately
+KRB5_KTNAME=/etc/dirsrv/ldap.keytab; export KRB5_KTNAME</pre>
+
+ </div></li></ol></div></dd></dl></div></dd><dt class="varlistentry"><span class="term">On the Client</span></dt><dd><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Copy the previously created <code class="filename">/root/client.keytab</code> file from the KDC to the <code class="filename">/etc/</code> directory and name it <code class="filename">krb5.keytab</code>. If the <code class="filename">/etc/krb5.keytab</code> file exists already, use the <span class="application"><strong>ktutil</strong></span> utility to merge both files properly. For more information on the <span class="application"><strong>ktutil</strong></span> utility, refer to <code class="command">man ktutil</code>.
+ </div></li><li class="listitem"><div class="para">
+ Modify your /etc/sssd/sssd.conf file to include the following settings:
+ </div><pre class="screen">
+ldap_sasl_mech = gssapi
+ldap_sasl_authid = host/client.example.com at EXAMPLE.COM
+ldap_krb5_keytab = /etc/krb5.keytab (default)
+ldap_krb5_init_creds = true (default)
+ldap_krb5_ticket_lifetime = 86400 (default)
+krb5_realm = EXAMPLE.COM
+</pre></li></ol></div></dd></dl></div></div></div><div class="section" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.7. Configuring a Proxy Domain</h3></div></div></div><a id="idm118951216" class="indexterm"></a><div class="para">
+ SSSD currently only supports LDAP and Kerberos as authentication providers. If you prefer to use SSSD (for example, to take advantage of its caching functionality), but SSSD does not support your authentication method, you can set up a proxy authentication provider. This could be the case if you use fingerprint scanners or smart cards as part of your authentication process. Similarly, you can set up proxy to serve as an identity provider.
+ </div><div class="para">
+ The following sections cover combinations of identity and authentication providers in which the proxy server takes the role of one.
+ </div><div class="section" id="sect-SSSD-proxy-krb5"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.7.1. proxy/KRB5</h4></div></div></div><div class="para">
+ The following configuration is an example of a combination of a proxy identity provider used with Kerberos authentication:
+ </div><div class="para">
+ Edit the <code class="filename">/etc/sssd/sssd.conf</code> configuration file to include the following settings:
+ </div><pre class="screen">
+[domain/PROXY_KRB5]
+auth_provider = krb5
+krb5_server = 192.168.1.1
+krb5_realm = EXAMPLE.COM
+
+id_provider = proxy
+proxy_lib_name = nis
+enumerate = true
+cache_credentials = true</pre><div class="para">
+ For more information on various Kerberos configuration options, refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">「Setting Up Kerberos Authentication」</a>.
+ </div></div><div class="section" id="sect-SSSD-LDAP-proxy"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.7.2. LDAP/proxy</h4></div></div></div><div class="para">
+ An example of a combination of an LDAP identity provider and a proxy authentication provider is the use of the LDAP with a custom PAM stack. To enable authentication via the PAM stack, complete the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/sssd/sssd.conf</code> configuration file to include the following settings:
+ </div><pre class="screen">
+[domain/LDAP_PROXY]
+id_provider = ldap
+ldap_uri = ldap://example.com
+ldap_search_base = dc=example,dc=com
+
+auth_provider = proxy
+proxy_pam_target = sssdpamproxy
+enumerate = true
+cache_credentials = true
+</pre><div class="para">
+ By specifying the options above, authentication requests will be proxied via the <code class="filename">/etc/pam.d/sssdpamproxy</code> file which provides the needed module interfaces. Note that the <code class="filename">pam_ldap.so</code> file can be substituted with a PAM module of your choice.
+ </div><div class="para">
+ For more information on various LDAP configuration options, refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">「Configuring an LDAP Domain」</a>.
+ </div></li><li class="listitem"><div class="para">
+ Create a <code class="filename">/etc/pam.d/sssdpamproxy</code> file (if not already created) and specify the following settings in it:
+ </div><pre class="screen">
+auth required pam_ldap.so
+account required pam_ldap.so
+password required pam_ldap.so
+session required pam_ldap.so</pre></li></ol></div></div><div class="section" id="sect-SSSD-proxy-proxy"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.7.3. proxy/proxy</h4></div></div></div><div class="para">
+ An example of a combination of an proxy identity provider and a proxy authentication provider is the use of the proxy identity provider with a custom PAM stack. To enable authentication via the PAM stack, complete the following steps:
+ </div><div class="note"><div class="admonition_header"><h2>Make sure the nss-pam-ldapd package is installed</h2></div><div class="admonition"><div class="para">
+ In order to use the proxy identity provider, you must have the <span class="package">nss-pam-ldapd</span> package installed.
+ </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/sssd/sssd.conf</code> configuration file to include the following settings:
+ </div><pre class="screen">
+[domain/PROXY_PROXY]
+auth_provider = proxy
+id_provider = proxy
+proxy_lib_name = ldap
+proxy_pam_target = sssdproxyldap
+enumerate = true
+cache_credentials = true
+</pre><div class="para">
+ By specifying the options above, authentication requests will be proxied via the <code class="filename">/etc/pam.d/sssdproxyldap</code> file which provides the needed module interfaces.
+ </div><div class="para">
+ For more information on the options used in the configuration example above, refer to <code class="command">man sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ Create a <code class="filename">/etc/pam.d/sssdproxyldap</code> file (if not already created) and specify the following settings in it:
+ </div><pre class="screen">
+auth required pam_ldap.so
+account required pam_ldap.so
+password required pam_ldap.so
+session required pam_ldap.so</pre></li><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/nslcd.conf</code> file (the default configuration file for the LDAP name service daemon) to include the following settings:
+ </div><pre class="screen">
+uid nslcd
+gid ldap
+uri ldaps://ldap.mydomain.org:636
+base dc=mydomain,dc=org
+ssl on
+tls_cacertdir /etc/openldap/cacerts</pre><div class="para">
+ For more information on the options used in the configuration example above, refer to <code class="command">man nslcd.conf</code>
+ </div></li></ol></div></div></div><div class="section" id="chap-SSSD_User_Guide-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.8. トラブルシューティング</h3></div></div></div><div class="para">
+ This section lists some of the issues you may encounter when implementing SSSD, the possible causes of these issues, and how to resolve them. If you find further issues that are not covered here, refer to the <em class="citetitle">We Need Feedback</em> section in the <em class="citetitle">Preface</em> for information on how to file a bug report.
+ </div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Using_SSSD_Log_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.1. Using SSSD Log Files</h4></div></div></div><div class="para">
+ SSSD uses a number of log files to report information about its operation, and this information can help to resolve issues in the event of SSSD failure or unexpected behavior. The default location for these log files on Fedora—based systems is the <code class="filename">/var/log/sssd/</code> directory.
+ </div><div class="para">
+ SSSD produces a log file for each back end (that is, one log file for each domain specified in the <code class="filename">/etc/sssd/sssd.conf</code> file), as well as an <code class="filename">sssd_pam.log</code> and an <code class="filename">sssd_nss.log</code> file. This level of granularity can help you to quickly isolate and resolve any errors or issues you might experience with SSSD.
+ </div><div class="para">
+ You should also examine the <code class="filename">/var/log/secure</code> file, which logs authentication failures and the reason for the failure. For example, if you see <span class="errortext">Reason 4: System Error</span> reported against any failure, you should increase the debug level of the log files.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Using_SSSD_Log_Files-Producing_More_Verbose_Log_Files"><h5 class="formalpara">Producing More Verbose Log Files</h5>
+ If you are unable to identify and resolve any problems with SSSD after inspection of the default log files, you can configure SSSD to produce more verbose files. You can set the <code class="option">debug_level</code> option in the <code class="filename">/etc/sssd/sssd.conf</code> for the domain that is causing concern, and then restart SSSD. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more information on how to set the <code class="option">debug_level</code> for a specific domain.
+ </div><div class="para">
+ All log files include timestamps on debug messages by default. This can make it easier to understand any errors that may occur, why they occurred, and how to address them. If necessary, you can disable these timestamps by setting the appropriate parameter to <code class="literal">FALSE</code> in the <code class="filename">/etc/sssd/sssd.conf</code> file:
+ </div><pre class="screen">--debug-timestamps=FALSE
+</pre></div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.2. Problems with SSSD Configuration</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ SSSD fails to start
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ SSSD requires at least one properly configured domain before the service will start. Without such a domain, you might see the following error message when trying to start SSSD with the following command:
+ </div><div class="para">
+ <code class="command"># sssd -d4</code>
+ </div><pre class="screen">[sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
+
+[sssd] [confdb_get_domains] (0): No domains configured, fatal error!
+[sssd] [get_monitor_config] (0): No domains configured.
+</pre><div class="para">
+ You can ignore the <span class="errortext">"Unable to register control with rootdse!"</span> message, as it is erroneous. The other messages, however, indicate that SSSD is unable to locate any properly configured domains.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file and ensure you have at least one properly configured domain, and then try to start SSSD.
+ </div></li><li class="listitem"><div class="para">
+ SSSD requires at least one available service provider before it will start. With no available service providers, you might see the following error message when trying to start SSSD with the following command:
+ </div><div class="para">
+ <code class="command"># sssd -d4</code>
+ </div><pre class="screen">[sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
+
+[sssd] [get_monitor_config] (0): No services configured!
+</pre><div class="para">
+ You can ignore the <span class="errortext">"Unable to register control with rootdse!"</span> message, as it is erroneous. The other message, however, indicates that SSSD is unable to locate any available service providers.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file and ensure you have at least one available service providers, and then try to start SSSD.
+ </div><div class="important"><div class="admonition_header"><h2>Configuring the service providers</h2></div><div class="admonition"><div class="para">
+ SSSD requires that service providers be configured as a comma-separated list in a single <em class="parameter"><code>services</code></em> entry in the <code class="filename">/etc/sssd/sssd.conf</code> file. If services are listed in multiple entries, only the last entry is recognized by SSSD.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more options that might assist in troubleshooting issues with SSSD.
+ </div></li></ul></div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Service_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.3. Problems with SSSD Service Configuration</h4></div></div></div><div class="section" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_NSS"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.8.3.1. Problems with NSS</h5></div></div></div><div class="para">
+ This section describes some common problems with <code class="systemitem">NSS</code>, their symptoms, and how to resolve them.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">NSS</code> fails to return user information
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Ensure that NSS is running
+ </div><div class="para">
+ <code class="command"># systemctl is-active sssd.service</code>
+ </div><div class="para">
+ This command should return results similar to the following:
+ </div><pre class="screen">sssd (pid 21762) is running...
+</pre></li><li class="listitem"><div class="para">
+ Ensure that you have correctly configured the <code class="literal">[nss]</code> section of the <code class="filename">/etc/sssd/sssd.conf</code> file. For example, ensure that you have not misconfigured the <em class="parameter"><code>filter_users</code></em> or <em class="parameter"><code>filter_groups</code></em> attributes. Refer to the <em class="citetitle">NSS configuration options</em> section of the <em class="citetitle">sssd.conf(5)</em> manual page for information on how to configure these attributes.
+ </div></li><li class="listitem"><div class="para">
+ Ensure that you have included <code class="systemitem">nss</code> in the list of services that <code class="systemitem">sssd</code> should start
+ </div></li><li class="listitem"><div class="para">
+ Ensure that you have correctly configured the <code class="filename">/etc/nsswitch.conf</code> file. Refer to the section <a class="xref" href="#sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS">「Configuring NSS」</a> for information on how to correctly configure this file.
+ </div></li></ul></div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.8.3.2. Problems with PAM</h5></div></div></div><div class="para">
+ This section describes some common problems with <code class="systemitem">PAM</code>, their symptoms, and how to resolve them.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Setting the password for the local SSSD user prompts twice for the password
+ </div><div class="para">
+ When attempting to change a local SSSD user's password, you might see output similar to the following:
+ </div><pre class="screen">[root at clientF11 tmp]# passwd user1000
+Changing password for user user1000.
+New password:
+Retype new password:
+New Password:
+Reenter new Password:
+passwd: all authentication tokens updated successfully.
+</pre><div class="para">
+ This is the result of an incorrect PAM configuration. Refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM">「Configuring PAM」</a>, and ensure that the <em class="parameter"><code>use_authtok</code></em> option is correctly configured in your <code class="filename">/etc/pam.d/system-auth</code> file.
+ </div></li></ul></div></div><div class="section" id="idm107257184"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm107257184">9.2.8.3.3. Problems with NFS and NSCD</h5></div></div></div><div class="para">
+ SSSD is not designed to be used with the <code class="systemitem">nscd</code> daemon, and will likely generate warnings in the SSSD log files. Even though SSSD does not directly conflict with <code class="systemitem">nscd</code>, the use of both at the same time can result in unexpected behavior (specifically with how long entries are being cached).
+ </div><div class="para">
+ If you are using Network Manager to manage your network connections, it may take several minutes for the network interface to come up. During this time, various services will attempt to start. If these services start before the network is up (that is, the DNS servers cannot yet be reached) they will fail to identify the forward or reverse DNS entries they might need. These services will be reading an incorrect or possibly empty <code class="filename">resolv.conf</code> file. This file is typically only read once, and so any changes made to this file are not automatically applied.
+ </div><div class="para">
+ This can result in the failure of some system services, and in particular can cause NFS locking to fail on the machine where the <code class="systemitem">nscd</code> service is running, unless that service is manually restarted.
+ </div><div class="para">
+ One method of working around this problem is to enable caching for <em class="parameter"><code>hosts</code></em> and <em class="parameter"><code>services</code></em> in the <code class="filename">/etc/nscd.conf</code> file, and to rely on the SSSD cache for the <em class="parameter"><code>passwd</code></em> and <em class="parameter"><code>group</code></em> entries. With <code class="systemitem">nscd</code> answering <em class="parameter"><code>hosts</code></em> and <em class="parameter"><code>services</code></em> requests, these entries would have been cached and returned by <code class="systemitem">nscd</code> during the boot process.
+ </div><div class="note"><div class="admonition_header"><h2>NSCD and later versions of SSSD</h2></div><div class="admonition"><div class="para">
+ Later versions of SSSD should negate any need for NSCD.
+ </div></div></div></div></div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Domain_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.4. Problems with SSSD Domain Configuration</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ NSS returns incorrect user information
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If your search for user information returns incorrect data, ensure that you do not have conflicting usernames in separate domains. If you use multiple domains, it is recommended that you set the <em class="parameter"><code>use_fully_qualified_domains</code></em> attribute to <code class="literal">TRUE</code> in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div></li></ul></div>
+
+ </div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.5. その他のリソース</h4></div></div></div><div class="section" id="sect-SSSD_User_Guide-Additional_Resources-Manual_Pages"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.8.5.1. Manual Pages</h5></div></div></div><div class="para">
+ SSSD ships with a number of manual pages, all of which provide additional information about specific aspects of SSSD, such as configuration files, commands, and available options. SSSD currently provides the following manual pages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">sssd.conf(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-ipa(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-krb5(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-ldap(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd(8)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd_krb5_locator_plugin(8)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">pam_sss(8)</code>
+ </div></li></ul></div><div class="para">
+ You should refer to these manual pages for detailed information about all aspects of SSSD, its configuration, and associated tools and commands.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Additional_Resources-Mailing_Lists"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.8.5.2. Mailing Lists</h5></div></div></div><div class="para">
+ You can subscribe to the SSSD mailing list to follow and become involved in the development of SSSD, or to ask questions about any issues you may be experiencing with your SSSD deployment.
+ </div><div class="para">
+ Visit <a href="https://fedorahosted.org/mailman/listinfo/sssd-devel">https://fedorahosted.org/mailman/listinfo/sssd-devel</a> to subscribe to this mailing list.
+ </div></div></div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.9. SSSD Configuration File Format</h3></div></div></div><div class="para">
+ The following listing describes the current version (Version 2) of the SSSD configuration file format.
+ </div><pre class="programlisting">[sssd]
+config_file_version = 2
+services = nss, pam
+domains = mybox.example.com, ldap.example.com, ipa.example.com, nis.example.com
+# sbus_timeout = 300
+
+[nss]
+nss_filter_groups = root
+nss_filter_users = root
+nss_entry_cache_timeout = 30
+nss_enum_cache_timeout = 30
+
+[domain/mybox.example.com]
+domain_type = local
+enumerate = true
+min_id = 1000
+# max_id = 2000
+
+local_default_shell = /bin/bash
+local_default_homedir = /home
+
+# Possible overrides
+# id_provider = local
+# auth_provider = local
+# authz_provider = local
+# passwd_provider = local
+
+[domain/ldap.example.com]
+domain_type = ldap
+server = ldap.example.com, ldap3.example.com, 10.0.0.2
+# ldap_uri = ldaps://ldap.example.com:9093
+# ldap_use_tls = ssl
+ldap_search_base = dc=ldap,dc=example,dc=com
+enumerate = false
+
+# Possible overrides
+# id_provider = ldap
+# id_server = ldap2.example.com
+# auth_provider = krb5
+# auth_server = krb5.example.com
+# krb5_realm = KRB5.EXAMPLE.COM
+
+[domain/ipa.example.com]
+domain_type = ipa
+server = ipa.example.com, ipa2.example.com
+enumerate = false
+
+# Possible overrides
+# id_provider = ldap
+# id_server = ldap2.example.com
+# auth_provider = krb5
+# auth_server = krb5.example.com
+# krb5_realm = KRB5.EXAMPLE.COM
+
+[domain/nis.example.com]
+id_provider = proxy
+proxy_lib = nis
+auth_provider = proxy
+proxy_auth_target = nis_pam_proxy
+</pre></div></div></div><div xml:lang="ja-JP" class="chapter" id="ch-OpenSSH" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第10章 OpenSSH</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-ssh-protocol">10.1. SSH プロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">10.1.1. なぜ SSH を使うのか？</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">10.1.2. 主な機能</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">10.1.3. プロトコル・バージョン</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">10.1.4. SSH コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">10.2. OpenSSH の設定</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">10.2.1. 設定ファイル</a></span></dt><dt><span class="section"><a href=
"#s2-ssh-configuration-sshd">10.2.2. OpenSSH サーバーの起動</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">10.2.3. リモート接続に対する SSH の要求</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">10.2.4. キー認証の使用</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">10.3. OpenSSH クライアント</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">10.3.1. ssh ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">10.3.2. <code class="command">scp</code> ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">10.3.3. <code class="command">sftp</code> ユーティリティの使用方法</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">10.4. 安全なシェル以上のもの</a></span></dt>
<dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">10.4.1. X11 転送</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">10.4.2. ポート転送</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">10.5. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-openssh-installed-docs">10.5.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-openssh-useful-websites">10.5.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></div><a id="idm95240112" class="indexterm"></a><div class="para">
+ <code class="systemitem">SSH</code> (Secure Shell) は、クライアント/サーバー型アーキテクチャーを用いて2つのシステム間でセキュアなコミュニケーションを促進して、ユーザーがサーバー・ホスト・システムにリモートでログインできるようにするプロトコルです。<code class="systemitem">FTP</code> や <code class="systemitem">Telnet</code> のような他のリモート・コミュニケーション・プロトコルと違い、SSH はログインセッションを暗号化します。侵入者が暗号化されていないパスワードを収集するのを難しくするコミュニケーションを行います。
+ </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 は一般的な OpenSSH パッケージ (<span class="package">openssh</span>) だけでなく、OpenSSH サーバー (<span class="package">openssh-server</span>) およびクライアント (<span class="package">openssh-clients</span>) パッケージを含みます。OpenSSH パッケージは OpenSSL パッケージ (<span class="package">openssl</span>) を必要なことに注意してください。これは OpenSSH に暗号化されたコミュニケーションを提供できるようにする、いくつかの重要な暗号ライブラリをインストールします。
+ </div><div class="section" id="s1-ssh-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.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">10.1.1. なぜ SSH を使うのか？</h3></div></div></div><a id="idm131824816" 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">10.1.2. 主な機能</h3></div></div></div><a id="idm83850848" class="indexterm"></a><a id="idm117608912" 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">
+ <em class="firstterm">X11 転送</em>という技術を使用することで、クライアントはサーバーから <em class="firstterm">X11</em> (<em class="firstterm">X Window System</em>) アプリケーションを転送できます。
+ </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">10.1.3. プロトコル・バージョン</h3></div></div></div><a id="idm138177984" class="indexterm"></a><a id="idm97477552" class="indexterm"></a><div class="para">
+ 現在 SSH には2種類あります。バージョン1と新しいバージョン2です。Fedora の OpenSSH は SSH バージョン2を使用します。これは、バージョン1において知られていたエクスプロイトに脆弱性がない、改善された鍵交換アルゴリズムを持ちます。しかしながら、互換性のため、OpenSSH はバージョン1の接続も同様にサポートします。
+ </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">10.1.4. SSH コネクションのイベント・シーケンス</h3></div></div></div><a id="idm119030128" 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">
+ リモートクライアントは、暗号化した接続を通じてリモートホストと交信します。
+ </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">10.1.4.1. トランスポート層</h4></div></div></div><a id="idm75206656" 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">
+ éµäº¤æ›ã®é–“ã€ã‚µãƒ¼ãƒãƒ¼ã¯ãれ自身を独自㮠<em class="firstterm">ホストéµ</em> ã§ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«å¯¾ã—ã¦è¨¼æ˜Žã—ã¾ã™ã€‚クライアントãŒã“ã®ç‰¹å®šã®ã‚µãƒ¼ãƒãƒ¼ã¨éŽåŽ»ã«é€šä¿¡ã—ãŸã“ã¨ãŒãªã‘ã‚Œã°ã€ã‚µãƒ¼ãƒãƒ¼ã®ãƒ›ã‚¹ãƒˆéµã¯ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«ã¯æœªçŸ¥ã§ã‚ã‚Šã€æŽ¥ç¶šã¯æˆç«‹ã—ã¾ã›ã‚“。 OpenSSH ã¯ã€ã‚µãƒ¼ãƒãƒ¼ã®ãƒ›ã‚¹ãƒˆéµã‚’承èªã™ã‚‹ã“ã¨ã§ã“ã®å•é¡Œã‚’回é¿ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒé€šçŸ¥ã‚’å—ã‘ã¦æ–°è¦ã®ãƒ›ã‚¹ãƒˆéµã‚’承èªã—確証ã—ãŸå¾Œã«èµ·ã“ã‚Šã¾ã™ã€‚ãれ以é™ã®æŽ¥ç¶šã§ã¯ã€ã‚µãƒ¼ãƒãƒ¼ã®ãƒ›ã‚¹ãƒˆéµã¯ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆä¸Šã«ä¿å˜ã—ã¦ã‚ã‚‹æƒ…å ±ã¨ç…§ã‚‰ã—åˆã‚ã›ã¦ãƒã‚§ãƒƒã‚¯ã•ã‚Œã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆãŒæœ¬å½“ã«ç›®çš„ã®ã‚µãƒ¼ãƒãƒ¼ã¨é€šä¿¡ã—ã¦ã„ã‚‹ã“ã¨ã®ç¢ºè¨¼ã‚’与ãˆã¾ã™ã€‚時間ãŒçµŒéŽã—ã¦ã€ã“ã®ãƒ›ã‚¹ãƒˆéµãŒä¸€è‡´ã—ãªã„状態ãŒèµ·ã“ã‚‹ã¨ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«ä¿å˜ã—ã¦ã‚ã‚‹å¤ã„æƒ…å ±ã‚’å‰Šé™¤ã
™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€æ–°ã—ã„接続ãŒå¯èƒ½ã«ãªã‚Šã¾ã™ã€‚
+ </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 の実装によりことなります)、別の鍵交換が発生してもう１つのハッシュ値セットと新しい共有秘密値が生成されます。攻撃者がハッシュ値と共有秘密値を判別できたとしても、その情報はほんの短い時間しか役に立ちません。
+ </div></div><div class="section" id="s2-ssh-protocol-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.4.2. 認証</h4></div></div></div><a id="idm110210304" 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">10.1.4.3. チャネル</h4></div></div></div><a id="idm132878144" class="indexterm"></a><div class="para">
+ SSH 転送層において認証が成功した後、複数のチャネルが<em class="firstterm">多重化</em><a href="#ftn.idm123686432" class="footnote"><sup class="footnote" id="idm123686432">[2]</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">10.2. 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">10.2.1. 設定ファイル</h3></div></div></div><a id="idm119563984" 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="idm119792352" class="indexterm"></a><div class="para">
+ システム全体の SSH 設定ファイルは <code class="filename">/etc/ssh/</code> ディレクトリに保存されてます。詳細は<a class="xref" href="#table-ssh-configuration-configs-system">表10.1「システム全体の設定ファイル」</a>を参照してください。
+ </div><div class="table" id="table-ssh-configuration-configs-system"><h6>表10.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="">
+ 設定ファイル
+ </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_dsa_key</code>
+ </td><td class="">
+ <code class="command">sshd</code> デーモンにより使用される DSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_dsa_key.pub</code>
+ </td><td class="">
+ <code class="command">sshd</code> デーモンにより使用される DSA 公開鍵です。
+ </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="">
+ SSH プロトコルのバージョン2用の <code class="command">sshd</code> デーモンにより使用される RSA 公開鍵です。
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="idm71939584" class="indexterm"></a><div class="para">
+ ユーザー固有の SSH 設定ファイルは、ユーザーのホームディレクトリにある <code class="filename">~/.ssh/</code> ディレクトリに保存されます。詳細は<a class="xref" href="#table-ssh-configuration-configs-user">表10.2「ユーザー固有の設定ファイル」</a>を参照してください。
+ </div><div class="table" id="table-ssh-configuration-configs-user"><h6>表10.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="">
+ 設定ファイル
+ </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_dsa</code>
+ </td><td class="">
+ ユーザーの DSA 秘密鍵を含みます。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_dsa.pub</code>
+ </td><td class="">
+ ユーザーの DSA 公開鍵です。
+ </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="">
+ SSH プロトコルのバージョン2用の <code class="command">ssh</code> により使用される RSA 鍵です。
+ </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="">
+ ユーザーによりアクセスされた SSH サーバーの DSA ホスト・キーを含みます。このファイルは SSH クライアントが正しい SSH サーバーに接続していることを確実にするために非常に重要です。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ SSH の設定ファイルにおいて利用可能なさまざまなディレクティブに関する詳細は、<code class="command">ssh_config</code> および <code class="command">sshd_config</code> のマニュアルページを参照してください。
+ </div></div><div class="section" id="s2-ssh-configuration-sshd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.2. OpenSSH サーバーの起動</h3></div></div></div><a id="idm90471760" class="indexterm"></a><div class="note"><div class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div class="admonition"><div class="para">
+ OpenSSH サーバーを実行するには、<span class="package">openssh-server</span> および <span class="package">openssh</span> パッケージがインストールされていなければいけません。Fedora において新しいパッケージをインストールする方法の詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</a>を参照してください。
+ </div></div></div><a id="idm124050128" class="indexterm"></a><div class="para">
+ <code class="command">sshd</code> デーモンを起動するには、シェルプロンプトにおいて以下のとおり入力します。
+ </div><pre class="screen"><code class="command">systemctl start sshd.service</code></pre><a id="idm124281344" class="indexterm"></a><div class="para">
+ 実行中の <code class="command">sshd</code> デーモンを停止するには、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl stop sshd.service</code></pre><div class="para">
+ ブート時にデーモンが自動的に起動するようにしたいならば、以下を入力します:
+ </div><pre class="screen"><code class="command">systemctl enable sshd.service</code></pre><div class="para">
+ Fedora において、サービスを設定する方法の詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </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">
+ これを防ぐには、<code class="filename">/etc/ssh/</code> ディレクトリから関連するファイルをバックアップできます (完全な一覧は <a class="xref" href="#table-ssh-configuration-configs-system">表10.1「システム全体の設定ファイル」</a> を参照してください)、そうするとシステムを再インストールしたときはそれらをリストアできます。
+ </div></div><div class="section" id="s2-ssh-configuration-requiring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.3. リモート接続に対する SSH の要求</h3></div></div></div><a id="idm58787008" class="indexterm"></a><a id="idm118483920" 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">
+ これらのサービスが実行していないことを確実にするには、シェルプロンプトにおいて以下のコマンドを入力します:
+ </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">
+ Fedora において、サービスを設定する方法の詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s2-ssh-configuration-keypairs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.4. キー認証の使用</h3></div></div></div><a id="idm110087408" class="indexterm"></a><div class="para">
+ システムのセキュリティをさらに向上させるために、標準的なパスワード認証を無効にすることにより、キーによる認証を強制できます。そうするために、テキストエディターで <code class="filename">/etc/ssh/sshd_config</code> ファイルを開いて、<code class="option">PasswordAuthentication</code> オプションを以下のように変更します:
+ </div><pre class="programlisting">PasswordAuthentication no</pre><div class="para">
+ サーバーにクライアントから接続するために <code class="command">ssh</code>, <code class="command">scp</code>, や <code class="command">sftp</code> を使用できるようにするには、以下の手順に従って認可キーペアを生成します。キーは各ユーザーがそれぞれ生成しなければいけないことに注意してください。
+ </div><div class="para">
+ Fedora 17 はデフォルトで 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">
+ システムを再インストールして、前に生成したキーペアを維持したいならば、<code class="filename">~/.ssh/</code> ディレクトリをバックアップします。再インストール後、それをホームディレクトリにコピーして戻します。このプロセスは <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">10.2.4.1. 鍵ペアの生成</h4></div></div></div><a id="idm93280464" class="indexterm"></a><a id="idm70363760" class="indexterm"></a><div class="para">
+ SSH プロトコルバージョン 2 用の RSA キーペアを生成するには、これらの手順に従います:
+ </div><a id="idm112667328" 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/john/.ssh/id_rsa):</pre></li><li class="step"><div class="para">
+ 新しく作成するキーに対するデフォルトの位置（つまり、<code class="filename">~/.ssh/id_rsa</code>）を確認するために <span class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div class="para">
+ パスフレーズを入力して、プロンプトが出たとき再び入力することにより確認します。セキュリティの理由により、アカウントにログインするために使用するパスワードと同じものを使用することは避けます。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/id_rsa.
+Your public key has been saved in /home/john/.ssh/id_rsa.pub.
+The key fingerprint is:
+e7:97:c7:e2:0e:f9:0e:fc:c4:d7:cb:e5:31:11:92:14 john at 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">
+ <code class="filename">~/.ssh/</code> ディレクトリのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 755 ~/.ssh</code></pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/id_rsa.pub</code> の内容を接続したいサーバーの <code class="filename">~/.ssh/authorized_keys</code> の中にコピーします。もしファイルがすでに存在すれば、その最後に追加します。
+ </div></li><li class="step"><div class="para">
+ 以下のコマンドを用いて <code class="filename">~/.ssh/authorized_keys</code> ファイルのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><a id="idm71531120" class="indexterm"></a><a id="idm98052656" class="indexterm"></a><div class="para">
+ SSH プロトコルバージョン 2 用の DSA キーペアを生成するには、これらの手順に従います:
+ </div><a id="idm100618640" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ シェルプロンプトにおいて以下のとおり入力することにより DSA キーペアを生成します:
+ </div><pre class="screen">~]$ <code class="command">ssh-keygen -t dsa</code>
+Generating public/private dsa key pair.
+Enter file in which to save the key (/home/john/.ssh/id_dsa):</pre></li><li class="step"><div class="para">
+ 新しく作成するキーに対するデフォルトの位置（つまり、<code class="filename">~/.ssh/id_dsa</code>）を確認するために <span class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div class="para">
+ パスフレーズを入力して、プロンプトが出たとき再び入力することにより確認します。セキュリティの理由により、アカウントにログインするために使用するパスワードと同じものを使用することは避けます。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/id_dsa.
+Your public key has been saved in /home/john/.ssh/id_dsa.pub.
+The key fingerprint is:
+81:a1:91:a8:9f:e8:c5:66:0d:54:f5:90:cc:bc:cc:27 john at penguin.example.com
+The key's randomart image is:
++--[ DSA 1024]----+
+| .oo*o. |
+| ...o Bo |
+| .. . + o. |
+|. . E o |
+| o..o S |
+|. o= . |
+|. + |
+| . |
+| |
++-----------------+</pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/</code> ディレクトリのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 775 ~/.ssh</code></pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/id_dsa.pub</code> の内容を接続したいサーバーの <code class="filename">~/.ssh/authorized_keys</code> の中にコピーします。もしファイルがすでに存在すれば、その最後に追加します。
+ </div></li><li class="step"><div class="para">
+ 以下のコマンドを用いて <code class="filename">~/.ssh/authorized_keys</code> ファイルのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><a id="idm113493680" class="indexterm"></a><a id="idm118761632" class="indexterm"></a><div class="para">
+ SSH プロトコルバージョン 1 用の R\nSA キーペアを生成するには、これらの手順に従います:
+ </div><a id="idm124869744" 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 rsa1</code>
+Generating public/private rsa1 key pair.
+Enter file in which to save the key (/home/john/.ssh/identity):</pre></li><li class="step"><div class="para">
+ 新しく作成するキーに対するデフォルトの位置（つまり、<code class="filename">~/.ssh/identity</code>）を確認するために <span class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div class="para">
+ パスフレーズを入力して、そうするようプロンプトが表示されたとき、入力することによりそれを確認します。セキュリティの理由のため、あたなのアカウントにログインするために使用するものと同じパスワードを使用することは避けてください。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/identity.
+Your public key has been saved in /home/john/.ssh/identity.pub.
+The key fingerprint is:
+cb:f6:d5:cb:6e:5f:2b:28:ac:17:0c:e4:62:e4:6f:59 john at penguin.example.com
+The key's randomart image is:
++--[RSA1 2048]----+
+| |
+| . . |
+| o o |
+| + o E |
+| . o S |
+| = + . |
+| . = . o . .|
+| . = o o..o|
+| .o o o=o.|
++-----------------+</pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/</code> ディレクトリのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 755 ~/.ssh</code></pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/identity.pub</code> の内容を接続したいサーバーの <code class="filename">~/.ssh/authorized_keys</code> の中にコピーします。もしファイルがすでに存在すれば、その最後に追加します。
+ </div></li><li class="step"><div class="para">
+ 以下のコマンドを用いて <code class="filename">~/.ssh/authorized_keys</code> ファイルのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><div class="para">
+ システムにパスフレーズを記憶させる方法については<a class="xref" href="#s3-ssh-configuration-keypairs-agent">「ssh-agent の設定」</a>を参照してください。
+ </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">10.2.4.2. ssh-agent の設定</h4></div></div></div><a id="idp1727888" class="indexterm"></a><a id="idm106484336" class="indexterm"></a><a id="idm106482896" class="indexterm"></a><a id="idm112706128" 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/john/.ssh/id_rsa:</pre><div class="para">
+ ログアウトするとき、パスフレーズが忘れられることに注意してください。仮想コンソールやターミナルウィンドウにログインするたびにコマンドを実行しなければいけません。
+ </div></div></div></div><div class="section" id="s1-ssh-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.3. OpenSSH クライアント</h2></div></div></div><a id="idm104128416" class="indexterm"></a><div class="note"><div class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div class="admonition"><div class="para">
+ クライアントマシンから OpenSSH サーバーに接続するには、<span class="package">openssh-clients</span> および <span class="package">openssh</span> パッケージをインストールしなければいけません。Fedora に新しいパッケージをインストールする方法は<a class="xref" href="#sec-Installing">「パッケージのインストール」</a>を参照してください。
+ </div></div></div><div class="section" id="s2-ssh-clients-ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.1. ssh ユーティリティの使用方法</h3></div></div></div><a id="idm90252176" class="indexterm"></a><a id="idm108935744" class="indexterm"></a><div class="para">
+ <code class="command">ssh</code> はリモートマシンにログインしたり、そこでコマンドを実行したりできます。<code class="command">rlogin</code>, <code class="command">rsh</code>, および <code class="command">telnet</code> プログラムのセキュアな代替品です。
+ </div><div class="para">
+ <code class="command">telnet</code> と同じように、<code class="systemitem">penguin.example.com</code> というリモートマシンにログインするには、シェルプロンプトにおいて以下のコマンドを入力します:
+ </div><pre class="screen">~]$ <code class="command">ssh penguin.example.com</code></pre><div class="para">
+ これはローカルマシンにおいて使用しているものと同じユーザー名を用いてログインします。異なるものを指定したい場合、<code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code> 形式でコマンドを使用します。たとえば、<code class="systemitem">john</code> としてログインするには、このように入力します:
+ </div><pre class="screen">~]$ <code class="command">ssh john at penguin.example.com</code></pre><div class="para">
+ はじめて接続するとき、このようなメッセージが表示されます:
+ </div><pre class="screen">The authenticity of host 'penguin.example.com' can't be established.
+RSA key fingerprint is 94:68:3a:3a:bc:f3:9a:9b:01:5d:b3:07:38:e2:11:0c.
+Are you sure you want to continue connecting (yes/no)?</pre><div class="para">
+ 確認するために <strong class="userinput"><code>yes</code></strong> と入力します。サーバーが既知のホストのリストに追加されることに注意してください。そして、パスワードを問い合わせるプロンプトが出ます:
+ </div><pre class="screen">Warning: Permanently added 'penguin.example.com' (RSA) to the list of known hosts.
+john at penguin.example.com's password:</pre><div class="important"><div class="admonition_header"><h2>SSH サーバーのホストキーの更新方法</h2></div><div class="admonition"><div class="para">
+ SSH サーバーのホストキーが変更されると、サーバーのホストキーが <code class="filename">~/.ssh/known_hosts</code> ファイルから削除されるまで接続を進めることができないことを、クライアントがユーザーに通知します。そうするには、テキストエディターでファイルを開いて、先頭にリモートマシン名を含む行を削除します。しかし、これを実行する前に、サーバーが侵入されていないことを確認するために、SSH サーバーのシステム管理者に問い合わせてください。
+ </div></div></div><div class="para">
+ パスワードを入力した後、リモートマシンのシェルプロンプトを提供されます。
+ </div><div class="para">
+ 代わりに、<code class="command">ssh</code> プログラムがシェルプロンプトにログインすることなく、リモートマシンにおいてコマンドを実行するためにも使うことができます。そのための構文は <code class="command">ssh [<em class="replaceable"><code>username</code></em>@]<em class="replaceable"><code>hostname</code></em> <em class="replaceable"><code>command</code></em></code> です。たとえば、<code class="systemitem">penguin.example.com</code>において <code class="command">whoami</code> コマンドを実行したいならば、次のように入力します:
+ </div><pre class="screen">~]$ <code class="command">ssh john at penguin.example.com whoami</code>
+john at penguin.example.com's password:
+john</pre><div class="para">
+ 正しいパスワードが入力された後、ユーザー名が表示され、ローカルのシェルプロンプトに戻ってきます。
+ </div></div><div class="section" id="s2-ssh-clients-scp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.2. <code class="command">scp</code> ユーティリティの使用方法</h3></div></div></div><a id="idm104023984" class="indexterm"></a><a id="idm104022064" class="indexterm"></a><a id="idm118543824" 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 john at penguin.example.com:.vim/plugin/taglist.vim</code>
+john at 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/* john at penguin.example.com:.vim/plugin/</code>
+john at 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 john at penguin.example.com:.vimrc .vimrc</code>
+john at 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">10.3.3. <code class="command">sftp</code> ユーティリティの使用方法</h3></div></div></div><a id="idm121502000" class="indexterm"></a><a id="idm118152976" 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">
+ たとえば、ユーザー名に <code class="systemitem">john</code> を用いて、<code class="systemitem">penguin.example.com</code> という名前のリモートマシンにログインするには、次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">sftp john at penguin.example.com</code>
+john at 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">表10.3「利用可能な sftp コマンドの選定品」</a>を参照してください）。
+ </div><div class="table" id="table-ssh-clients-sftp"><h6>表10.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">
+ 利用可能なコマンドの完全な一覧は <code class="command">sftp</code> のマニュアルページを参照してください。
+ </div></div></div><div class="section" id="s1-ssh-beyondshell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.4. 安全なシェル以上のもの</h2></div></div></div><div class="para">
+ 安全なコマンドラインインターフェイスは、 SSH が使用できる多くの方法の単なる一部分です。充分なバンド幅があれば、 X11 セッションは １ つの 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">10.4.1. X11 転送</h3></div></div></div><a id="idm122274608" 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">
+ たとえば、ユーザー名に <code class="systemitem">john</code> を用いて、<code class="systemitem">penguin.example.com</code> という名前のリモートマシンにログインするには、次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">ssh -Y john at penguin.example.com</code>
+john at penguin.example.com's password:</pre><div class="para">
+ 安全なシェルプロンプトから X プログラムが実行されると、 SSH クライアントとサーバーは新しい安全なチャンネルを作成し、 X プログラムデータはそのチャンネルを通じて透過的にクライアントマシンに送信されます。
+ </div><div class="para">
+ X11 転送は非常に有用です。<span class="application"><strong>プリンター設定</strong></span>ユーティリティのセキュアな対話式セッションを作成するために使用できます。これをするために、<span class="application"><strong>ssh</strong></span> を使用してサーバーに接続して、次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">system-config-printer &</code></pre><div class="para">
+ <span class="application"><strong>プリンター設定ツール</strong></span>が表示され、リモートユーザーがリモートシステムにある印刷環境を安全に設定できるようになります。
+ </div></div><div class="section" id="s2-ssh-beyondshell-tcpip"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.2. ポート転送</h3></div></div></div><a id="idm103858448" 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">
+ 1024 以下のポートをリスンする為のポート転送をセットするには、 root レベルのアクセスが必要です。
+ </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">10.5. 追加のリソース</h2></div></div></div><a id="idm47624464" class="indexterm"></a><a id="idm47623024" class="indexterm"></a><div class="para">
+ OpenSSH と OpenSSL プロジェクトの開発は常に進められているため、これらに関する最新情報は該当する Web サイトを参照してください。 OpenSSH と OpenSSL ツールの man ページでも詳細情報を参照することができます。
+ </div><div class="section" id="s2-openssh-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.5.1. インストールされているドキュメント</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">man ssh</code></span></dt><dd><div class="para">
+ <span class="application"><strong>ssh</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man scp</code></span></dt><dd><div class="para">
+ <span class="application"><strong>scp</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sftp</code></span></dt><dd><div class="para">
+ <span class="application"><strong>sftp</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sshd</code></span></dt><dd><div class="para">
+ <span class="application"><strong>sshd</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ssh-keygen</code></span></dt><dd><div class="para">
+ <span class="application"><strong>ssh-keygen</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ssh_config</code></span></dt><dd><div class="para">
+ SSH クライアントの利用可能な設定オプションの完全な説明を持つマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sshd_config</code></span></dt><dd><div class="para">
+ SSH デーモンの利用可能な設定オプションの完全な説明を持つマニュアルページです。
+ </div></dd></dl></div></div><div class="section" id="s2-openssh-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.5.2. 役に立つ Web サイト</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.openssh.com/">http://www.openssh.com/</a></span></dt><dd><div class="para">
+ さらなるドキュメント、よくある質問、メーリングリストへのリンク、バグ報告、および他の有用なリソースがある OpenSSH のホームページです。
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.openssl.org/">http://www.openssl.org/</a></span></dt><dd><div class="para">
+ さらなるドキュメント、よくある質問、メーリングリストへのリンク、および他の有用なリソースがある OpenSSL のホームページです。
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.freesshd.com/">http://www.freesshd.com/</a></span></dt><dd><div class="para">
+ SSH サーバーのもう一つの実装です。
+ </div></dd></dl></div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="ftn.idm123686432" class="footnote"><div class="para"><a href="#idm123686432" class="para"><sup class="para">[2] </sup></a>
+ 多重化された接続は共有された一般的なメディア上で送られる複数の信号から構成されます。SSH では、異なるチャネルが共通のセキュアなコネクション上で送られます。
+ </div></div></div></div></div><div class="part" id="part-Servers"><div class="titlepage"><div><div text-align="center"><h1 class="title">パート V. サーバー</h1></div></div></div><div class="partintro" id="idm112328416"><div></div><div class="para">
+ このパートは、ウェブサーバーを導入する、またはネットワーク上にファイルとディレクトリを共有する方法のようなサーバーに関連したさまざまな話題を説明しています。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="#ch-DHCP_Servers">11. DHCP サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-dhcp-why">11.1. DHCP を使用する理由</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-server">11.2. DHCP サーバーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">11.2.1. 設定ファイル</a></span></dt><dt><span class="section"><a href="#lease-database">11.2.2. リースデータベース</a></span></dt><dt><span class="section"><a href="#idm122588480">11.2.3. サーバーの起動と停止</a></span></dt><dt><span class="section"><a href="#dhcp-relay-agent">11.2.4. DHCP リレーエージェント</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp-configuring-client">11.3. DHCP クライアントの設定</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server"
>11.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-dns_Host_Configuration">11.4.1. ホストã®è¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">11.5. IPv6 å‘ã‘ DHCP (DHCPv6)</a></span></dt><dt><span class="section"><a href="#s1-dhcp-additional-resources">11.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dhcp-installed-docs">11.6.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-DNS_Servers">12. DNS サーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Introduction_to_DNS">12.1. DNS ã®æ¦‚è¦</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dns-introduction-zones">12.1.1. ãƒãƒ¼ãƒ サーãƒãƒ¼ã‚¾ãƒ¼ãƒ³</a></span></dt><dt><span class="section"><a href="#s2-dns-introduction-nameservers">12.1.2. ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚
¤ãƒ—</a></span></dt><dt><span class="section"><a href="#s2-dns-introduction-bind">12.1.3. ãƒãƒ¼ãƒ サーãƒãƒ¼ã¨ã—ã¦ã® BIND</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-BIND">12.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-namedconf">12.2.1. named サービスã®è¨å®š</a></span></dt><dt><span class="section"><a href="#s2-bind-zone">12.2.2. ゾーンファイルã®ç·¨é›†</a></span></dt><dt><span class="section"><a href="#s2-bind-rndc">12.2.3. rndc ユーティリティã®ä½¿ç”¨æ³•</a></span></dt><dt><span class="section"><a href="#s2-bind-dig">12.2.4. dig ユーティリティã®ä½¿ç”¨</a></span></dt><dt><span class="section"><a href="#s2-bind-features">12.2.5. BIND ã®é«˜åº¦ãªæ©Ÿèƒ½</a></span></dt><dt><span class="section"><a href="#s2-bind-mistakes">12.2.6. よãã‚ã‚‹é–“é•ã„ã‚’é¿ã‘ã‚‹ãŸã‚ã«</a></span></dt><dt><span class="section"><a href="#s2-bind-additional-resources">12.2.7. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></sp
an></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Web_Servers">13. ウェブ サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-The_Apache_HTTP_Server">13.1. Apache HTTP サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-version2-features">13.1.1. 新機能</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-changes">13.1.2. 注目すべき変更</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">13.1.3. 設定の更新</a></span></dt><dt><span class="section"><a href="#s2-apache-running">13.1.4. httpd サービスの実行方法</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">13.1.5. 設定ファイルの編集</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">13.1.6. Working with Modules</a></span></dt><dt><span class="section"><a href="#s2-apache-virtualhosts">13.1.7. 仮想ホストのセットアップ</a></span></
dt><dt><span class="section"><a href="#s2-apache-mod_ssl">13.1.8. SSL サーバーのセットアップ</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">13.1.9. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Mail_Servers">14. メールサーバー</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">14.1. 電子メールプロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protocols-send">14.1.1. メール トランスポートのプロトコル</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">14.1.2. メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">14.2. 電子メールプログラム分類</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">14.2.1. メール転送エージェント (Mail Transport Agent)</a></span></dt><d
t><span class="section"><a href="#s2-email-types-mda">14.2.2. メール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">14.2.3. メール ユーザー エージェント</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mta">14.3. Mail Transport Agent</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-postfix">14.3.1. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-sendmail">14.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">14.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="#s2-email-switchmail">14.3.4. Mail Transport Agent (MTA) の設定</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mda">14.4. メール配送エージェント</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">14.4.1. Procmail の設定</a></span></dt><
dt><span class="section"><a href="#s2-email-procmail-recipes">14.4.2. Procmail レシピ</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">14.5. メールユーザーエージェント</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">14.5.1. 通信のセキュリティ</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">14.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">14.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">14.6.2. 役に立つ Web サイト</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">14.6.3. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Directory_Servers">15. ディレクトリー サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="
#s1-OpenLDAP">15.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">15.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">15.1.2. OpenLDAP 製品群のインストール</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">15.1.3. OpenLDAP サーバーの設定法</a></span></dt><dt><span class="section"><a href="#s2-ldap-running">15.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">15.1.5. システムが OpenLDAP を使用して認証を実行するように設定する</a></span></dt><dt><span class="section"><a href="#s2-ldap-resources">15.1.6. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-File_and_Print_Servers">16. ファイルサーバーおよびプリントサーバー</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Samba">16.1. Samba</a></span><
/dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">16.1.1. Samba の概要</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">16.1.2. Samba デーモンと関連サービス</a></span></dt><dt><span class="section"><a href="#s2-samba-connect-share">16.1.3. Samba シェアへの接続</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">16.1.4. Samba サーバーの設定</a></span></dt><dt><span class="section"><a href="#s2-samba-startstop">16.1.5. Samba の開始と停止</a></span></dt><dt><span class="section"><a href="#s2-samba-servers">16.1.6. Samba サーバー形式と <code class="filename">smb.conf</code> ファイル</a></span></dt><dt><span class="section"><a href="#s2-samba-security-modes">16.1.7. Samba のセキュリティモード</a></span></dt><dt><span class="section"><a href="#s2-samba-account-info-dbs">16.1.8. Samba のアカウント情報データベース</a></span></dt><dt><span class="section"><a
href="#s2-samba-network-browsing">16.1.9. Samba ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ–ラウジング</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">16.1.10. CUPS å°åˆ·ã‚µãƒãƒ¼ãƒˆã‚’使ã£ãŸ Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">16.1.11. Samba ディストリビューションプãƒã‚°ãƒ©ãƒ </a></span></dt><dt><span class="section"><a href="#s2-samba-resources">16.1.12. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">16.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol">16.2.1. ファイルä¼é€ãƒ—ãƒãƒˆã‚³ãƒ«</a></span></dt><dt><span class="section"><a href="#s2-ftp-servers">16.2.2. FTP サーãƒãƒ¼</a></span></dt><dt><span class="section"><a href="#s3-ftp-vsftpd-conf">16.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-start">16.2.4. <code class="command">vsftpd</code> ã®é–
‹å§‹ã¨åœæ¢</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">16.2.5. <code class="command">vsftpd</code> è¨å®šã‚ªãƒ—ション</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">16.2.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration">16.3. プリンタã®è¨å®š</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">16.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="#sec-Setting_Printer">16.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="#sec-Adding_Other_Printer">16.3.3. ãƒãƒ¼ã‚«ãƒ«ãƒ—リンタã®è¿½åŠ </a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">16.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">16.3.5. IPP プリンタã®è¿½åŠ </a></span></dt><dt><s
pan class="section"><a href="#sec-printing-LPDLPR-printer">16.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">16.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">16.3.8. プリンタモデルã®é¸æŠžã¨çµ‚了</a></span></dt><dt><span class="section"><a href="#s1-printing-test-page">16.3.9. Printing a test page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">16.3.10. æ—¢å˜ãƒ—リンタã®å¤‰æ›´</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">16.3.11. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd></dl></dd></dl></div></div><div xml:lang="ja-JP" class="chapter" id="ch-DHCP_Servers" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第11ç« DHCP サーãƒãƒ¼</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-dhcp-why">11.1. DHCP を使用ã™ã‚‹ç
†ç”±</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-server">11.2. DHCP サーãƒãƒ¼ã®è¨å®š</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">11.2.1. è¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></span></dt><dt><span class="section"><a href="#lease-database">11.2.2. リースデータベース</a></span></dt><dt><span class="section"><a href="#idm122588480">11.2.3. サーãƒãƒ¼ã®èµ·å‹•ã¨åœæ¢</a></span></dt><dt><span class="section"><a href="#dhcp-relay-agent">11.2.4. DHCP リレーエージェント</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp-configuring-client">11.3. DHCP クライアントã®è¨å®š</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server">11.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-dns_Host_Configuration">11.4.1. ホストã®è¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp_for_ipv
6_dhcpv6">11.5. IPv6 向け DHCP (DHCPv6)</a></span></dt><dt><span class="section"><a href="#s1-dhcp-additional-resources">11.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dhcp-installed-docs">11.6.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a id="idm88598672" class="indexterm"></a><a id="idm106720496" class="indexterm"></a><div class="para">
+ <acronym class="acronym">DHCP</acronym> (Dynamic Host Configuration Protocol) は、クライアントマシンに自動的に TCP/IP 情報を割り当てるネットワークプロトコルです。各 DHCP クライアントは、中央に配置された DHCP サーバーに接続し、このサーバーが IP アドレス、ゲートウェイ、 DNS サーバーなどクライアントのネットワーク設定情報 (IP アドレス、ゲートウェイ、 DNS サーバーを含む) を返します。
+ </div><div class="section" id="s1-dhcp-why"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.1. DHCP を使用する理由</h2></div></div></div><a id="idm130372480" class="indexterm"></a><div class="para">
+ DHCP はクライアントのネットワークインターフェースを自動で設定するのに便利です。クライアントシステムを設定するとき DHCP を選択すれば、 IP アドレス、ネットマスク、ゲートウェイ、 DNS サーバーを入力する必要がありません。クライアントはこれらの情報を DHCP サーバーから受け取ります。また、管理者が多数のシステムの IP アドレスを変更する場合も DHCP は便利です。すべてのシステムの再設定を行う代わりに、サーバー上の DHCP 設定ファイルを編集することによって、新規の IP アドレスセットを設定できます。組織の DNS サーバーが変更された場合は、 DHCP クライアントで変更を行うのではなく、 DHCP サーバーで変更を行います。クライアントでネットワークが再起動 （またはクライアントがリブート） されると、変
更が反映されます。
+ </div><div class="para">
+ 組織が、機能中の DHCP サーバーをネットワークに正しく接続している場合、ラップトップや他の携帯コンピュータの使用者はそのようなデバイスをオフィスからオフィスへと移動して使用できます。
+ </div></div><div class="section" id="s1-dhcp-configuring-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.2. DHCP サーバーの設定</h2></div></div></div><a id="idm133169568" class="indexterm"></a><div class="para">
+ <code class="filename">dhcp</code> パッケージは ISC DHCP サーバーを含みます。まず、<code class="systemitem">root</code> としてパッケージをインストールします:
+ </div><pre class="screen"><code class="command">yum install dhcp</code></pre><div class="para">
+ <code class="filename">dhcp</code> パッケージをインストールすることにより、単に空の設定ファイル <code class="filename">/etc/dhcp/dhcpd.conf</code> が作成されます:
+ </div><pre class="programlisting">#
+# DHCP Server Configuration file.
+# see /usr/share/doc/dhcp*/dhcpd.conf.sample
+# see dhcpd.conf(5) man page
+#</pre><div class="para">
+ サンプル設定ファイルが <code class="filename">/usr/share/doc/dhcp-<em class="replaceable"><code>version</code></em>/dhcpd.conf.sample</code> にあります。以下に説明されている <code class="filename">/etc/dhcp/dhcpd.conf</code> を設定する助けにするために、このファイルを使用すべきです。
+ </div><div class="para">
+ DHCP はクライアントの払い出しデータベースを保存するために <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> ファイルも使用します。詳細は<a class="xref" href="#lease-database">「リースデータベース」</a>を参照してください。
+ </div><div class="section" id="config-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.2.1. 設定ファイル</h3></div></div></div><a id="idm113153616" class="indexterm"></a><a id="idm97250224" class="indexterm"></a><div class="para">
+ DHCP サーバーを設定する第一歩は、クライアントのネットワーク情報を保存する設定ファイルを作成することです。クライアントシステムのオプションや全体オプションを宣言するためにこのファイルを使用します。
+ </div><div class="para">
+ 設定ファイルはフォーマットがしやすいように余計なタブや空白行を含めることができます。キーワードは大文字小文字を区別しません。また、ハッシュ記号 (#) から始まる行はコメント行と見なされます。
+ </div><div class="para">
+ 設定ファイルのステートメントには、次の2タイプがあります：
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ パラメーター — タスクがどのように実行されるか、またはクライアントに送られるネットワーク設定オプションを述べます。
+ </div></li><li class="listitem"><div class="para">
+ 宣言 — ネットワークのトポロジーを記述します、クライアントを記述します、クライアントのアドレスを提供します、または宣言のグループにパラメーターのグループを適用します。
+ </div></li></ul></div><a id="idm119886272" class="indexterm"></a><div class="para">
+ キーワードオプションで始まるパラメーターは<em class="firstterm">オプション</em>として見なされます。これらのオプションは DHCP オプションを制御します。一方、パラメーターはオプションではない値を設定します、または、DHCP サーバーがどのように振る舞うかを制御します。
+ </div><a id="idm1267376" class="indexterm"></a><div class="para">
+ 中かっこ （{ }） で囲まれたセクションの前に宣言されたパラメータとオプションは、グローバルパラメータとみなされます。グローバルパラメータは、それ以降のすべてのセクションに適用されます。
+ </div><div class="important"><div class="admonition_header"><h2>変更を反映するには DHCP デーモンを再起動します</h2></div><div class="admonition"><div class="para">
+ 設定ファイルが変更されても、DHCP デーモンを再起動するまで、変更が有効になりません。そうするには、<code class="systemitem">root</code> としてシェルプロンプトにおいて以下を入力します:
+ </div><pre class="screen"><code class="command">systemctl restart dhcpd.service</code></pre></div></div><div class="note"><div class="admonition_header"><h2>omshell コマンドを使用する</h2></div><div class="admonition"><div class="para">
+ DHCP 設定ファイルを変更して、毎回サービスを再起動する代わりに、<code class="command">omshell</code> コマンドを使用することにより、DHCP サーバーに接続し、その設定を問い合わせ、変更する非対話式の方法が提供されます。<code class="command">omshell</code> を使用することにより、すべての変更はサーバーが実行中に反映されます。<code class="command">omshell</code> の詳細は <code class="command">omshell</code> マニュアルページを参照してください。
+ </div></div></div><div class="para">
+ <a class="xref" href="#subnet">例11.1「サブネット宣言」</a>において、<code class="filename">routers</code>, <code class="filename">subnet-mask</code>, <code class="filename">domain-search</code>, <code class="filename">domain-name-servers</code>, および <code class="filename">time-offset</code> オプションはその下に宣言されたすべての <code class="filename">host</code> ステートメントに対して使用できます。
+ </div><a id="idm134334064" class="indexterm"></a><div class="para">
+ さらに、<code class="filename">subnet</code> が宣言され、<code class="filename">subnet</code> 宣言がネットワークにあるすべてのサブネットに対して含めなければいけません。もしなければ、DHCP サーバーが起動に失敗します。
+ </div><div class="para">
+ この例では、サブネットと宣言された <code class="filename">range</code> においてすべての DHCP クライアントに対する全体オプションがあります。クライアントは <code class="filename">range</code> の中にある IP アドレスが割り当てられます。
+ </div><div class="example" id="subnet"><h6>例11.1 サブネット宣言</h6><div class="example-contents"><pre class="programlisting">subnet 192.168.1.0 netmask 255.255.255.0 {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ range 192.168.1.10 192.168.1.100;
+}</pre></div></div><br class="example-break" /><div class="para">
+ 動的 IP アドレスをサブネットにあるシステムに払い出す DHCP サーバーを設定するには、値を持つ<a class="xref" href="#dynamic-ip">例11.2「range パラメーター」</a>を変更します。デフォルトの払い出し期間、最大の払い出し期間、およびクライアントに対するネットワーク設定値を宣言します。この例はクライアントシステムに対して <code class="filename">range</code> 192.168.1.10 と 192.168.1.100 にある IP アドレスを割り当てます。
+ </div><div class="example" id="dynamic-ip"><h6>例11.2 range パラメーター</h6><div class="example-contents"><pre class="programlisting">default-lease-time 600;
+max-lease-time 7200;
+option subnet-mask 255.255.255.0;
+option broadcast-address 192.168.1.255;
+option routers 192.168.1.254;
+option domain-name-servers 192.168.1.1, 192.168.1.2;
+option domain-search "example.com";
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.10 192.168.1.100;
+}</pre></div></div><br class="example-break" /><div class="para">
+ To assign an IP address to a client based on the MAC address of the network interface card, use the <code class="filename">hardware ethernet</code> parameter within a <code class="filename">host</code> declaration. As demonstrated in <a class="xref" href="#static-ip">例11.3「DHCP を用いた静的 IP アドレス」</a>, the <code class="filename">host apex</code> declaration specifies that the network interface card with the MAC address 00:A0:78:8E:9E:AA always receives the IP address 192.168.1.4.
+ </div><div class="para">
+ オプションのパラメーター <code class="filename">host-name</code> はホスト名をクライアントに割り当てるために使用されます。
+ </div><div class="example" id="static-ip"><h6>例11.3 DHCP を用いた静的 IP アドレス</h6><div class="example-contents"><pre class="programlisting">host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}</pre></div></div><br class="example-break" /><a id="idm74907120" class="indexterm"></a><div class="para">
+ All subnets that share the same physical network should be declared within a <code class="filename">shared-network</code> declaration as shown in <a class="xref" href="#shared-network">例11.4「shared-network 宣言」</a>. Parameters within the <code class="filename">shared-network</code>, but outside the enclosed <code class="filename">subnet</code> declarations, are considered to be global parameters. The name of the <code class="filename">shared-network</code> must be a descriptive title for the network, such as using the title 'test-lab' to describe all the subnets in a test lab environment.
+ </div><div class="example" id="shared-network"><h6>例11.4 shared-network 宣言</h6><div class="example-contents"><pre class="programlisting">shared-network name {
+ option domain-search "test.redhat.com";
+ option domain-name-servers ns1.redhat.com, ns2.redhat.com;
+ option routers 192.168.0.254;
+ more parameters for EXAMPLE shared-network
+ subnet 192.168.1.0 netmask 255.255.252.0 {
+ parameters for subnet
+ range 192.168.1.1 192.168.1.254;
+ }
+ subnet 192.168.2.0 netmask 255.255.252.0 {
+ parameters for subnet
+ range 192.168.2.1 192.168.2.254;
+ }
+}</pre></div></div><br class="example-break" /><a id="idm110509184" class="indexterm"></a><div class="para">
+ As demonstrated in <a class="xref" href="#group">例11.5「group 宣言」</a>, the <code class="filename">group</code> declaration is used to apply global parameters to a group of declarations. For example, shared networks, subnets, and hosts can be grouped.
+ </div><div class="example" id="group"><h6>例11.5 group 宣言</h6><div class="example-contents"><pre class="programlisting">group {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+ }
+ host raleigh {
+ option host-name "raleigh.example.com";
+ hardware ethernet 00:A1:DD:74:C3:F2;
+ fixed-address 192.168.1.6;
+ }
+}</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>サンプル設定ファイルの使用法</h2></div><div class="admonition"><div class="para">
+ The sample configuration file provided can be used as a starting point and custom configuration options can be added to it. To copy it to the proper location, use the following command:
+ </div><pre class="screen"><code class="command">cp /usr/share/doc/dhcp-<em class="replaceable"><code>version-number</code></em>/dhcpd.conf.sample /etc/dhcp/dhcpd.conf</code></pre><div class="para">
+ ... ここで <em class="replaceable"><code>version-number</code></em> は DHCP バージョン番号です。
+ </div></div></div><div class="para">
+ For a complete list of option statements and what they do, refer to the <code class="filename">dhcp-options</code> man page.
+ </div></div><div class="section" id="lease-database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.2.2. リースデータベース</h3></div></div></div><div class="para">
+ On the DHCP server, the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> stores the DHCP client lease database. Do not change this file. DHCP lease information for each recently assigned IP address is automatically stored in the lease database. The information includes the length of the lease, to whom the IP address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card that was used to retrieve the lease.
+ </div><div class="para">
+ リースデータベースにおける時刻はすべて、ローカル時でなく UTC (Coordinated Universal Time) を使用します。
+ </div><div class="para">
+ The lease database is recreated from time to time so that it is not too large. First, all known leases are saved in a temporary lease database. The <code class="filename">dhcpd.leases</code> file is renamed <code class="filename">dhcpd.leases~</code> and the temporary lease database is written to <code class="filename">dhcpd.leases</code>.
+ </div><div class="para">
+ The DHCP daemon could be killed or the system could crash after the lease database has been renamed to the backup file but before the new file has been written. If this happens, the <code class="filename">dhcpd.leases</code> file does not exist, but it is required to start the service. Do not create a new lease file. If you do, all old leases are lost which causes many problems. The correct solution is to rename the <code class="filename">dhcpd.leases~</code> backup file to <code class="filename">dhcpd.leases</code> and then start the daemon.
+ </div></div><div class="section" id="idm122588480"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm122588480">11.2.3. サーバーの起動と停止</h3></div></div></div><a id="idm122587712" class="indexterm"></a><a id="idm86544608" class="indexterm"></a><a id="idm86543008" class="indexterm"></a><a id="idm54703504" class="indexterm"></a><div class="important"><div class="admonition_header"><h2>DHCP サーバーの始めての起動</h2></div><div class="admonition"><div class="para">
+ When the DHCP server is started for the first time, it fails unless the <code class="filename">dhcpd.leases</code> file exists. Use the command <code class="command">touch /var/lib/dhcpd/dhcpd.leases</code> to create the file if it does not exist.
+ </div><div class="para">
+ If the same server is also running BIND as a DNS server, this step is not necessary, as starting the <code class="command">named</code> service automatically checks for a <code class="filename">dhcpd.leases</code> file.
+ </div></div></div><div class="para">
+ DHCP サーバーを開始するには、次のとおり入力します:
+ </div><pre class="screen"><code class="command">systemctl start dhcpd.service</code></pre><div class="para">
+ DHCP サーバーを停止するには、次のとおり入力します:
+ </div><pre class="screen"><code class="command">systemctl stop dhcpd.service</code></pre><div class="para">
+ デフォルトで、DHCP サービスはブート時に開始しません。ブート時に自動的に開始するようデーモンを設定するには、以下を実行します:
+ </div><pre class="screen"><code class="command">systemctl enable dhcpd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法の詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div><a id="idm124947440" class="indexterm"></a><a id="idm101665120" class="indexterm"></a><div class="para">
+ If more than one network interface is attached to the system, but the DHCP server should only be started on one of the interfaces, configure the DHCP server to start only on that device. In <code class="filename">/etc/sysconfig/dhcpd</code>, add the name of the interface to the list of <code class="command">DHCPDARGS</code>:
+ </div><pre class="programlisting"># Command line options here
+DHCPDARGS=eth0</pre><div class="para">
+ これは、ネットワークカードが2つあるファイアウォールマシンに便利な機能です。一方のネットワークカードを DHCP クライアントとして設定してインターネット用の IP アドレスを取得します。もう一方のネットワークカードは、ファイアウォール内の内部ネットワーク用の DHCP サーバーとして使用できます。内部ネットワークに接続されたネットワークカードだけを指定することにより、ユーザーがインターネット経由でデーモンに接続できなくなるので、システムがより安全になります。
+ </div><div class="para">
+ Other command line options that can be specified in <code class="filename">/etc/sysconfig/dhcpd</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-p <em class="replaceable"><code>portnum</code></em> </code> — Specifies the UDP port number on which <code class="command">dhcpd</code> should listen. The default is port 67. The DHCP server transmits responses to the DHCP clients at a port number one greater than the UDP port specified. For example, if the default port 67 is used, the server listens on port 67 for requests and responses to the client on port 68. If a port is specified here and the DHCP relay agent is used, the same port on which the DHCP relay agent should listen must be specified. Refer to <a class="xref" href="#dhcp-relay-agent">「DHCP リレーエージェント」</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f</code> — Runs the daemon as a foreground process. This is mostly used for debugging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> — Logs the DHCP server daemon to the standard error descriptor. This is mostly used for debugging. If this is not specified, the log is written to <code class="filename">/var/log/messages</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-cf <em class="replaceable"><code>filename</code></em> </code> — Specifies the location of the configuration file. The default location is <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-lf <em class="replaceable"><code>filename</code></em> </code> — Specifies the location of the lease database file. If a lease database file already exists, it is very important that the same file be used every time the DHCP server is started. It is strongly recommended that this option only be used for debugging purposes on non-production machines. The default location is <code class="filename">/var/lib/dhcpd/dhcpd.leases</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-q</code> — デーモンを起動するときに全体の著作権メッセージを表示しません。
+ </div></li></ul></div></div><div class="section" id="dhcp-relay-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.2.4. DHCP リレーエージェント</h3></div></div></div><a id="idm137782208" class="indexterm"></a><a id="idm112537712" class="indexterm"></a><a id="idm112536080" class="indexterm"></a><div class="para">
+ DHCP リレーエージェント (<code class="command">dhcrelay</code>) は、DHCP と BOOTP 要求を DHCP サーバーを持つサブネットから他のサブネットにある1つ以上の DHCP サーバーまでリレーできます。
+ </div><div class="para">
+ DHCP クライアントが情報を要求すると、 DHCP リレーエージェントは自身の起動時に指定された一覧に含まれる DHCP サーバーに要求を転送します。 DHCP サーバーのいずれかから応答が返されると、その応答はオリジナルの要求を送信したネットワークにブロードキャストされたりユニキャストされたりします。
+ </div><div class="para">
+ The DHCP Relay Agent listens for DHCP requests on all interfaces unless the interfaces are specified in <code class="filename">/etc/sysconfig/dhcrelay</code> with the <code class="computeroutput">INTERFACES</code> directive.
+ </div><div class="para">
+ DHCP リレーエージェントを開始するには、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl start dhcrelay.service</code></pre></div></div><div class="section" id="s1-dhcp-configuring-client"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.3. DHCP クライアントの設定</h2></div></div></div><a id="idm112039296" class="indexterm"></a><a id="idm130969856" class="indexterm"></a><div class="para">
+ DHCP クライアントを手動で設定するには、ネットワークを有効にするために <code class="filename">/etc/sysconfig/network</code> ファイルを、また <code class="filename">/etc/sysconfig/network-scripts</code> ディレクトリにある各ネットワークデバイス用の設定ファイルを変更します。このディレクトリにおいて、各デバイス <code class="filename">ifcfg-eth0</code> という名前の設定ファイルを持たなければいけません。ここで <code class="filename">eth0</code> はネットワークデバイス名です。
+ </div><div class="para">
+ <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code> ファイルは以下の行を含まなければいけません:
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ DHCP を使用するよう設定するデバイスごとに設定ファイルが必要です。
+ </div><div class="para">
+ ネットワークスクリプト用に含まれるその他のオプション:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">DHCP_HOSTNAME</code> — Only use this option if the DHCP server requires the client to specify a hostname before receiving an IP address. (The DHCP server daemon in Fedora does not support this feature.)
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">PEERDNS=<em class="replaceable"><code>answer</code></em> </code>、ここで<code class="literal"><em class="replaceable"><code>answer</code></em> </code> は以下のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — サーバーからの情報を用いて <code class="filename">/etc/resolv.conf</code> を変更します。DHCP を使用しているならば、<code class="command">yes</code> はデフォルトです。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — <code class="filename">/etc/resolv.conf</code> を変更しません。
+ </div></li></ul></div></li></ul></div><div class="note"><div class="admonition_header"><h2>高度な設定</h2></div><div class="admonition"><div class="para">
+ For advanced configurations of client DHCP options such as protocol timing, lease requirements and requests, dynamic DNS support, aliases, as well as a wide variety of values to override, prepend, or append to client-side configurations, refer to the <code class="command">dhclient</code> and <code class="command">dhclient.conf</code> man pages.
+ </div></div></div></div><div class="section" id="sect-Configuring_a_Multihomed_DHCP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.4. Configuring a Multihomed DHCP Server</h2></div></div></div><a id="idm96058800" class="indexterm"></a><div class="para">
+ A multihomed DHCP server serves multiple networks, that is, multiple subnets. The examples in these sections detail how to configure a DHCP server to serve multiple networks, select which network interfaces to listen on, and how to define network settings for systems that move networks.
+ </div><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="para">
+ The DHCP daemon listens on all network interfaces unless otherwise specified. Use the <code class="filename">/etc/sysconfig/dhcpd</code> file to specify which network interfaces the DHCP daemon listens on. The following <code class="filename">/etc/sysconfig/dhcpd</code> example specifies that the DHCP daemon listens on the <code class="filename">eth0</code> and <code class="filename">eth1</code> interfaces:
+ </div><pre class="programlisting">DHCPDARGS="eth0 eth1";</pre><div class="para">
+ If a system has three network interfaces cards -- <code class="filename">eth0</code>, <code class="filename">eth1</code>, and <code class="filename">eth2</code> -- and it is only desired that the DHCP daemon listens on <code class="filename">eth0</code>, then only specify <code class="computeroutput">eth0</code> in <code class="filename">/etc/sysconfig/dhcpd</code>:
+ </div><pre class="programlisting">DHCPDARGS="eth0";</pre><div class="para">
+ The following is a basic <code class="filename">/etc/dhcp/dhcpd.conf</code> file, for a server that has two network interfaces, <code class="filename">eth0</code> in a 10.0.0.0/24 network, and <code class="filename">eth1</code> in a 172.16.0.0/24 network. Multiple <code class="computeroutput">subnet</code> declarations allow different settings to be defined for multiple networks:
+ </div><pre class="programlisting">default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="computeroutput">subnet <em class="replaceable"><code>10.0.0.0</code></em> netmask <em class="replaceable"><code>255.255.255.0</code></em>;</code></span></dt><dd><div class="para">
+ A <code class="computeroutput">subnet</code> declaration is required for every network your DHCP server is serving. Multiple subnets require multiple <code class="computeroutput">subnet</code> declarations. If the DHCP server does not have a network interface in a range of a <code class="computeroutput">subnet</code> declaration, the DHCP server does not serve that network.
+ </div><div class="para">
+ If there is only one <code class="computeroutput">subnet</code> declaration, and no network interfaces are in the range of that subnet, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">dhcpd: No subnet declaration for eth0 (0.0.0.0).
+dhcpd: ** Ignoring requests on eth0. If this is not what
+dhcpd: you want, please write a subnet declaration
+dhcpd: in your dhcpd.conf file for the network segment
+dhcpd: to which interface eth1 is attached. **
+dhcpd:
+dhcpd:
+dhcpd: Not configured to listen on any interfaces!</pre></dd><dt class="varlistentry"><span class="term"><code class="computeroutput">option subnet-mask <em class="replaceable"><code>255.255.255.0</code></em>;</code></span></dt><dd><div class="para">
+ <code class="computeroutput">option subnet-mask</code> オプションはサブネットマスクを定義します。<code class="computeroutput">subnet</code> 宣言における <code class="computeroutput">netmask</code> 値を上書きします。簡単な例では、サブネットとネットマスクの値は同じです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="computeroutput">option routers <em class="replaceable"><code>10.0.0.1</code></em>;</code></span></dt><dd><div class="para">
+ The <code class="computeroutput">option routers</code> option defines the default gateway for the subnet. This is required for systems to reach internal networks on a different subnet, as well as external networks.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="computeroutput">range <em class="replaceable"><code>10.0.0.5</code></em> <em class="replaceable"><code>10.0.0.15</code></em>;</code></span></dt><dd><div class="para">
+ <code class="computeroutput">range</code> オプションは利用可能な IP アドレスのプールを指定します。システムは指定された IP アドレスの範囲からアドレスを割り当てられます。
+ </div></dd></dl></div><div class="para">
+ 詳細は <code class="computeroutput">dhcpd.conf(5)</code> マニュアルページを参照してください。
+ </div><div class="warning"><div class="admonition_header"><h2>エイリアス・インターフェースを使用しないでください</h2></div><div class="admonition"><div class="para">
+ エイリアス・インターフェースは DHCP によりサポートされません。エイリアス・インターフェースが <code class="filename">/etc/dhcp/dhcpd.conf</code> において指定されている唯一のサブネットにおける唯一のインターフェースならば、DHCP デーモンは開始に失敗します。
+ </div></div></div><div class="section" id="sect-dns_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.4.1. ホストの設定</h3></div></div></div><a id="idm113711664" class="indexterm"></a><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm100627888">Configuring a single system for multiple networks</h5>
+ 以下の <code class="filename">/etc/dhcp/dhcpd.conf</code> の例は2つのサブネットを作成し、接続しているネットワークに応じて同じシステムに対する IP アドレスを設定します。
+ </div><pre class="programlisting">default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}
+host example0 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 10.0.0.20;
+}
+host example1 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 172.16.0.20;
+}</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="computeroutput">host <em class="replaceable"><code>example0</code></em> </code></span></dt><dd><div class="para">
+ The <code class="computeroutput">host</code> declaration defines specific parameters for a single system, such as an IP address. To configure specific parameters for multiple hosts, use multiple <code class="computeroutput">host</code> declarations.
+ </div><div class="para">
+ Most DHCP clients ignore the name in <code class="computeroutput">host</code> declarations, and as such, this name can anything, as long as it is unique to other <code class="computeroutput">host</code> declarations. To configure the same system for multiple networks, use a different name for each <code class="computeroutput">host</code> declaration, otherwise the DHCP daemon fails to start. Systems are identified by the <code class="computeroutput">hardware ethernet</code> option, not the name in the <code class="computeroutput">host</code> declaration.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">hardware ethernet <em class="replaceable"><code>00:1A:6B:6A:2E:0B</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">hardware ethernet</code> option identifies the system. To find this address, run the <code class="command">ip link</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="computeroutput">fixed-address <em class="replaceable"><code>10.0.0.20</code></em>;</code></span></dt><dd><div class="para">
+ The <code class="computeroutput">fixed-address</code> option assigns a valid IP address to the system specified by the <code class="computeroutput">hardware ethernet</code> option. This address must be outside the IP address pool specified with the <code class="computeroutput">range</code> option.
+ </div></dd></dl></div><div class="para">
+ If <code class="computeroutput">option</code> statements do not end with a semicolon, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">/etc/dhcp/dhcpd.conf line 20: semicolon expected.
+dhcpd: }
+dhcpd: ^
+dhcpd: /etc/dhcp/dhcpd.conf line 38: unexpected end of file
+dhcpd:
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting</pre><div class="formalpara"><h5 class="formalpara" id="idm99222480">複数のネットワークインターフェースを持つシステムの設定</h5>
+ The following <code class="computeroutput">host</code> declarations configure a single system, that has multiple network interfaces, so that each interface receives the same IP address. This configuration will not work if both network interfaces are connected to the same network at the same time:
+ </div><pre class="programlisting">host interface0 {
+ hardware ethernet 00:1a:6b:6a:2e:0b;
+ fixed-address 10.0.0.18;
+}
+host interface1 {
+ hardware ethernet 00:1A:6B:6A:27:3A;
+ fixed-address 10.0.0.18;
+}</pre><div class="para">
+ For this example, <code class="computeroutput">interface0</code> is the first network interface, and <code class="computeroutput">interface1</code> is the second interface. The different <code class="computeroutput">hardware ethernet</code> options identify each interface.
+ </div><div class="para">
+ If such a system connects to another network, add more <code class="computeroutput">host</code> declarations, remembering to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ assign a valid <code class="computeroutput">fixed-address</code> for the network the host is connecting to.
+ </div></li><li class="listitem"><div class="para">
+ make the name in the <code class="computeroutput">host</code> declaration unique.
+ </div></li></ul></div><div class="para">
+ When a name given in a <code class="computeroutput">host</code> declaration is not unique, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">dhcpd: /etc/dhcp/dhcpd.conf line 31: host interface0: already exists
+dhcpd: }
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting</pre><div class="para">
+ This error was caused by having multiple <code class="computeroutput">host interface0</code> declarations defined in <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></div></div><div class="section" id="s1-dhcp_for_ipv6_dhcpv6"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.5. IPv6 向け DHCP (DHCPv6)</h2></div></div></div><a id="idm91643376" class="indexterm"></a><a id="idm138004304" class="indexterm"></a><div class="para">
+ The ISC DHCP includes support for IPv6 (DHCPv6) since the 4.x release with a DHCPv6 server, client and relay agent functionality. The server, client and relay agents support both IPv4 and IPv6. However, the client and the server can only manage one protocol at a time — for dual support they must be started separately for IPv4 and IPv6.
+ </div><div class="para">
+ DHCPv6 サーバーの設定ファイルは <code class="filename">/etc/dhcp/dhcpd6.conf</code> に見つけられます。
+ </div><div class="para">
+ The sample server configuration file can be found at <code class="filename">/usr/share/doc/dhcp-version/dhcpd6.conf.sample</code>.
+ </div><div class="para">
+ DHCPv6 サービスを開始するには、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl start dhcpd6.service</code></pre><div class="para">
+ DHCPv6 サーバーの簡単な設定ファイルはこのように見えます:
+ </div><pre class="programlisting">subnet6 2001:db8:0:1::/64 {
+ range6 2001:db8:0:1::129 2001:db8:0:1::254;
+ option dhcp6.name-servers fec0:0:0:1::1;
+ option dhcp6.domain-search "domain.example";
+}</pre></div><div class="section" id="s1-dhcp-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.6. その他のリソース</h2></div></div></div><a id="idm85570736" class="indexterm"></a><div class="para">
+ For additional information, refer to <em class="citetitle">The DHCP Handbook; Ralph Droms and Ted Lemon; 2003</em> or the following resources.
+ </div><div class="section" id="s2-dhcp-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.6.1. インストールされているドキュメント</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">dhcpd</code> マニュアルページ — DHCP デーモンがどうように動作するかを説明します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.conf</code> man page — Explains how to configure the DHCP configuration file; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.leases</code> マニュアルページ — リースの永続的なデータベースを説明しています。
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcp-options</code> man page — Explains the syntax for declaring DHCP options in <code class="filename">dhcpd.conf</code>; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcrelay</code> マニュアルページ — DHCP リレーエージェントおよびその設定オプションを説明しています。
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/dhcp-<em class="replaceable"><code>version</code></em>/</code> — 現在のバージョンの DHCP サービスに関するサンプルファイル、README ファイル、およびリリースノートがあります。
+ </div></li></ul></div></div></div></div><div xml:lang="ja-JP" class="chapter" id="ch-DNS_Servers" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第12章 DNS サーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-Introduction_to_DNS">12.1. DNS の概要</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dns-introduction-zones">12.1.1. ネームサーバーゾーン</a></span></dt><dt><span class="section"><a href="#s2-dns-introduction-nameservers">12.1.2. ネームサーバーのタイプ</a></span></dt><dt><span class="section"><a href="#s2-dns-introduction-bind">12.1.3. ネームサーバーとしての BIND</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-BIND">12.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-namedconf">12.2.1. named サービスの設定</a></span></dt><dt><span class="section"><a href="#s2-bind-zone">12.2.2. ゾーンファイルの編集
</a></span></dt><dt><span class="section"><a href="#s2-bind-rndc">12.2.3. rndc ユーティリティの使用法</a></span></dt><dt><span class="section"><a href="#s2-bind-dig">12.2.4. dig ユーティリティの使用</a></span></dt><dt><span class="section"><a href="#s2-bind-features">12.2.5. BIND の高度な機能</a></span></dt><dt><span class="section"><a href="#s2-bind-mistakes">12.2.6. よくある間違いを避けるために</a></span></dt><dt><span class="section"><a href="#s2-bind-additional-resources">12.2.7. その他のリソース</a></span></dt></dl></dd></dl></div><a id="idm111443696" class="indexterm"></a><a id="idm124877664" class="indexterm"></a><div class="para">
+ <code class="systemitem">DNS</code> (Domain Name System) は、<em class="firstterm">ネームサーバー</em>としても知られ、ホスト名とそれぞれの IP アドレスを関連づけるネットワークシステムです。ユーザーにとって、ネットワークにあるマシンを名前で参照できるという利便性があります。通常これは数値のネットワークアドレスよりも記憶しやすいです。システム管理者にとって、ネームサーバーを使用することにより、名前に基づいた問い合わせに影響を与えることなくホストの IP アドレスを変更したり、どのマシンがこれらの問い合わせを処理するかを決めたりできるようになります。
+ </div><div class="section" id="s1-Introduction_to_DNS"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.1. DNS の概要</h2></div></div></div><a id="idm111441088" class="indexterm"></a><div class="para">
+ DNS は、集中化されたドメインに対して権威のある、1つか複数の集中化されたサーバーを使用して実装されます。クライアントホストがネームサーバーから情報を要求するとき、通常ポート 53 に接続します。そして、ネームサーバーは要求された名前を解決しようとします。権威のある回答を持たなければ、または以前の問い合わせからキャッシュされた回答をすでに持っていなければ、どのネームサーバーが問い合わせにある名前に対して権威があるかを決めるために、<em class="firstterm">ルートネームサーバー</em>と呼ばれる他のネームサーバーに問い合わせます。そして、要求された名前を取得するためにそのサーバーに問い合わせます。
+ </div><div class="section" id="s2-dns-introduction-zones"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.1. ネームサーバーゾーン</h3></div></div></div><a id="idm138186144" class="indexterm"></a><a id="idm138188096" class="indexterm"></a><a id="idm138189712" class="indexterm"></a><a id="idm138190672" class="indexterm"></a><div class="para">
+ BIND のような DNS サーバーにおいて、すべての情報は<em class="firstterm">リソースレコード</em> (RR) と呼ばれる基本的なデータ要素に保存されます。リソースレコードは通常ホストの <em class="firstterm">fully qualified domain name</em> (FQDN) です。そして、ツリー構造の階層の中に整理された複数のセクションに分解されます。この階層は、主幹、一次分岐、二次分岐などから構成されます。以下はリソースレコードの例です:
+ </div><pre class="programlisting">bob.sales.example.com</pre><a id="idm132159424" class="indexterm"></a><div class="para">
+ 階層の各レベルはピリオド（つまり、<code class="literal">.</code>）により分割されます。上の例では、<code class="literal">com</code> は<em class="firstterm">トップレベルドメイン</em>、そのサブドメイン <code class="literal">example</code>、<code class="literal">example</code> のサブドメイン <code class="literal">sales</code> を定義します。この場合、<code class="literal">bob</code> は <code class="systemitem">sales.example.com</code> ドメインの一部であるリソースレコードを識別します。最も左にある部分（つまり、<code class="literal">bob</code>）を除き、これらのセクションの各部は<em class="firstterm">ゾーン</em>と呼ばれ、具体的な<em class="firstterm">名前空間</em>を定義します。
+ </div><a id="idm127483296" class="indexterm"></a><a id="idm127485024" class="indexterm"></a><div class="para">
+ ゾーンã¯<em class="firstterm">ゾーンファイル</em>ã®ä½¿ç”¨ã«ã‚ˆã‚Šæ¨©å¨ãƒãƒ¼ãƒ サーãƒãƒ¼ã«ãŠã„ã¦å®šç¾©ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€å„ゾーンã«ãŠã‘るリソースレコードã®å®šç¾©ã‚’å«ã¿ã¾ã™ã€‚ゾーンファイルã¯<em class="firstterm">プライマリãƒãƒ¼ãƒ サーãƒãƒ¼</em>（<em class="firstterm">マスターãƒãƒ¼ãƒ サーãƒãƒ¼</em>ã¨ã‚‚呼ã°ã‚Œã¾ã™ï¼‰ã«ãŠã„ã¦ï¼ˆå¤‰æ›´ã¯ãƒ•ã‚¡ã‚¤ãƒ«ã«å¯¾ã—ã¦è¡Œã‚ã‚Œã¾ã™ï¼‰ã€ãŠã‚ˆã³ã€<em class="firstterm">セカンダリãƒãƒ¼ãƒ サーãƒãƒ¼</em>（<em class="firstterm">スレーブãƒãƒ¼ãƒ サーãƒãƒ¼</em>ã¨ã‚‚呼ã°ã‚Œã¾ã™ï¼‰ã«ãŠã„ã¦ï¼ˆãƒ—ライマリãƒãƒ¼ãƒ サーãƒãƒ¼ã‹ã‚‰ã‚¾ãƒ¼ãƒ³å®šç¾©ã‚’å—ä¿¡ã—ã¾ã™ï¼‰ä¿å˜ã•ã‚Œã¾ã™ã€‚プライマリã¨ã‚»ã‚«ãƒ³ãƒ€ãƒªã©ã¡ã‚‰ã®ãƒãƒ¼ãƒ サーãƒãƒ¼ã‚‚ゾーンã«å¯¾ã™ã‚‹æ¨©å¨ã§ã‚ã‚Šã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«åŒã˜ã‚ˆã†ã«è¦‹ãˆã¾ã™ã€‚è¨å®šã«ã‚ˆã£ã¦ã¯ã€ã™ã¹ã¦ã®ãƒãƒ¼ãƒ サーãƒãƒ¼ãŒè¤‡æ•°ã®ã‚¾ãƒ¼ãƒ³ã«å
¯¾ã—ã¦åŒæ™‚ã«ãƒ—ライマリã¾ãŸã¯ã‚»ã‚«ãƒ³ãƒ€ãƒªã‚µãƒ¼ãƒãƒ¼ã¨ã—ã¦ã‚‚処ç†ã§ãã¾ã™ã€‚
+ </div></div><div class="section" id="s2-dns-introduction-nameservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.2. ネームサーバーのタイプ</h3></div></div></div><div class="para">
+ ネームサーバーの設定種別が2つあります:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm115926528" class="indexterm"></a>
+ <a id="idm137263088" class="indexterm"></a>
+ <a id="idm137264672" class="indexterm"></a>
+ <a id="idm120410912" class="indexterm"></a>
+ <a id="idm120413552" class="indexterm"></a>
+ <a id="idm120414992" class="indexterm"></a>
+ 権威</span></dt><dd><div class="para">
+ 権威ネームサーバーはそれらのゾーンのみの一部であるリソースレコードに回答します。この分類はプライマリ（マスター）およびセカンダリ（スレーブ）ネームサーバーを含みます。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm138211728" class="indexterm"></a>
+ <a id="idm138213616" class="indexterm"></a>
+ 再帰</span></dt><dd><div class="para">
+ 再帰ネームサーバーは解決サービスを提供しますが、あらゆるゾーンに対して権威的ではありません。すべての解決に対する回答は、取り出したリソースレコードにより指定された、一定期間メモリーにキャッシュされます。
+ </div></dd></dl></div><div class="para">
+ ネームサーバーは同時に権威および再帰になれますが、設定の種別を組み合わせることは推奨されません。これらの機能を実行できるようにするには、権威サーバーがいつでもすべてのクライアントに利用可能であるべきです。一方、再帰問い合わせは権威のある応答よりも時間がかかるので、再帰サーバーは制限された数のクライアントのみに利用可能であるべきです。そうしなければ、分散サービス妨害（DDoS）攻撃を受けやすくなります。
+ </div></div><div class="section" id="s2-dns-introduction-bind"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.3. ネームサーバーとしての BIND</h3></div></div></div><a id="idm129873968" class="indexterm"></a><a id="idm129877184" class="indexterm"></a><a id="idm138573440" class="indexterm"></a><a id="idm138575248" class="indexterm"></a><a id="idm132438416" class="indexterm"></a><a id="idm132437040" class="indexterm"></a><div class="para">
+ BIND は DNS 関連のプログラム群から構成されています。<code class="systemitem">named</code> という画一的なネームサーバー、<code class="command">rndc</code> という管理ユーティリティ、および <code class="command">dig</code> というデバッグツールを含みます。Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div></div><div xml:lang="ja-JP" class="section" id="s1-BIND" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.2. BIND</h2></div></div></div><a id="idm91922576" class="indexterm"></a><div class="para">
+ 本章は Fedora に含まれる DNS サーバーである <code class="systemitem">BIND</code> (Berkeley Internet Name Domain) を取り扱います。その設定ファイルの構造に焦点を当て、ローカルおよびリモートで管理する方法について説明しています。
+ </div><div class="section" id="s2-bind-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.1. named サービスの設定</h3></div></div></div><a id="idm91926480" class="indexterm"></a><div class="para">
+ <code class="systemitem">named</code> サービスが起動するとき、<a class="xref" href="#table-bind-namedconf-files">表12.1「named サービス設定ファイル」</a>において説明されているように、ファイルから設定が読み込まれます。
+ </div><a id="idm94382512" class="indexterm"></a><a id="idm129326208" class="indexterm"></a><a id="idm129328640" class="indexterm"></a><div class="table" id="table-bind-namedconf-files"><h6>表12.1 named サービス設定ファイル</h6><div class="table-contents"><table summary="named サービス設定ファイル" border="1"><colgroup><col width="38%" class="path" /><col width="63%" class="description" /></colgroup><thead><tr><th class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="filename">/etc/named.conf</code>
+ </td><td class="">
+ 主要な設定ファイル。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/named/</code>
+ </td><td class="">
+ 主要な設定ファイルから取り込まれる設定ファイルのための補助ディレクトリ。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The configuration file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (that is, <code class="literal">{</code> and <code class="literal">}</code>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <code class="systemitem">named</code> service will not start. A typical <code class="filename">/etc/named.conf</code> file is organized as follows:
+ </div><pre class="programlisting"><em class="replaceable"><code>statement-1</code></em> ["<em class="replaceable"><code>statement-1-name</code></em>"] [<em class="replaceable"><code>statement-1-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-2</code></em> ["<em class="replaceable"><code>statement-2-name</code></em>"] [<em class="replaceable"><code>statement-2-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-N</code></em> ["<em class="replaceable"><code>statement-N-name</code></em>"] [<em class="replaceable"><code>statement-N-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};</pre><div class="note"><div class="admonition_header"><h2>chroot 環境における BIND の実行</h2></div><div class="admonition"><div class="para">
+ If you have installed the <span class="package">bind-chroot</span> package, the BIND service will run in the <code class="filename">/var/named/chroot</code> environment. In that case, the initialization script will mount the above configuration files using the <code class="command">mount --bind</code> command, so that you can manage the configuration outside this environment.
+ </div></div></div><div class="section" id="s3-bind-namedconf-state"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.1.1. 一般的なステートメントのタイプ</h4></div></div></div><div class="para">
+ 以下の種類の宣言が一般的に <code class="filename">/etc/named.conf</code> において使用されます:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm124936976" class="indexterm"></a>
+ <code class="option">acl</code></span></dt><dd><div class="para">
+ <code class="option">acl</code> (Access Control List) ステートメントによりホストのグループを定義できます。それにより、ネームサーバーへのアクセスを許可および拒否できます。これは以下の形式をとります:
+ </div><pre class="programlisting">acl <em class="replaceable"><code>acl-name</code></em> {
+ <em class="replaceable"><code>match-element</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>acl-name</code></em> statement name is the name of the access control list, and the <em class="replaceable"><code>match-element</code></em> option is usually an individual IP address (such as <code class="literal">10.0.1.1</code>) or a CIDR network notation (for example, <code class="literal">10.0.1.0/24</code>). For a list of already defined keywords, see <a class="xref" href="#table-bind-namedconf-common-acl">表12.2「事前定義済みアクセス制御リスト」</a>.
+ </div><div class="table" id="table-bind-namedconf-common-acl"><h6>表12.2 事前定義済みアクセス制御リスト</h6><div class="table-contents"><table summary="事前定義済みアクセス制御リスト" border="1"><colgroup><col width="25%" class="keyword" /><col width="75%" class="description" /></colgroup><thead><tr><th class="">
+ キーワード
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">any</code>
+ </td><td class="">
+ すべての IP アドレスに一致します。
+ </td></tr><tr><td class="">
+ <code class="option">localhost</code>
+ </td><td class="">
+ ローカルシステムにおいて使用中のすべての IP アドレスに一致します。
+ </td></tr><tr><td class="">
+ <code class="option">localnets</code>
+ </td><td class="">
+ ローカルシステムが接続されているすべてのネットワークにある IP アドレスに一致します。
+ </td></tr><tr><td class="">
+ <code class="option">none</code>
+ </td><td class="">
+ どの IP アドレスにも一致しません。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="option">acl</code> statement can be especially useful with conjunction with other statements such as <code class="option">options</code>. <a class="xref" href="#example-bind-namedconf-common-acl">例12.1「オプションと併用した ACL の使用」</a> defines two access control lists, <code class="literal">black-hats</code> and <code class="literal">red-hats</code>, and adds <code class="literal">black-hats</code> on the blacklist while granting <code class="literal">red-hats</code> a normal access.
+ </div><div class="example" id="example-bind-namedconf-common-acl"><h6>例12.1 オプションと併用した ACL の使用</h6><div class="example-contents"><pre class="programlisting">acl black-hats {
+ 10.0.2.0/24;
+ 192.168.0.0/24;
+ 1234:5678::9abc/24;
+};
+acl red-hats {
+ 10.0.1.0/24;
+};
+options {
+ blackhole { black-hats; };
+ allow-query { red-hats; };
+ allow-query-cache { red-hats; };
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm109323248" class="indexterm"></a>
+ <code class="option">include</code></span></dt><dd><div class="para">
+ The <code class="option">include</code> statement allows you to include files in the <code class="filename">/etc/named.conf</code>, so that potentially sensitive data can be placed in a separate file with restricted permissions. It takes the following form:
+ </div><pre class="programlisting">include "<em class="replaceable"><code>file-name</code></em>"</pre><div class="para">
+ The <em class="replaceable"><code>file-name</code></em> statement name is an absolute path to a file.
+ </div><div class="example" id="example-bind-namedconf-common-include"><h6>例12.2 /etc/named.conf へのファイルの取り込み</h6><div class="example-contents"><pre class="programlisting">include "/etc/named.rfc1912.zones";</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm102024224" class="indexterm"></a>
+ <code class="option">options</code></span></dt><dd><div class="para">
+ The <code class="option">options</code> statement allows you to define global server configuration options as well as to set defaults for other statements. It can be used to specify the location of the <code class="systemitem">named</code> working directory, the types of queries allowed, and much more. It takes the following form:
+ </div><pre class="programlisting">options {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ For a list of frequently used <em class="replaceable"><code>option</code></em> directives, see <a class="xref" href="#table-bind-namedconf-common-options">表12.3「一般的に使用されるオプション」</a> below.
+ </div><div class="table" id="table-bind-namedconf-common-options"><h6>表12.3 一般的に使用されるオプション</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">allow-query</code>
+ </td><td class="">
+ ネームサーバーに権威リソースレコードを問い合わせできるホストを指定します。アクセス制御リスト、IP アドレスの組、または CIDR 表記のネットワークを受け付けます。すべてのホストがデフォルトで許可されます。
+ </td></tr><tr><td class="">
+ <code class="option">allow-query-cache</code>
+ </td><td class="">
+ ネームサーバーに再帰問い合わせのような権威のないデータを問い合わせできるホストを指定します。<code class="literal">localhost</code> および <code class="literal">localnets</code> のみがデフォルトで許可されます。
+ </td></tr><tr><td class="">
+ <code class="option">blackhole</code>
+ </td><td class="">
+ ネームサーバーに問い合わせを許可され<span class="emphasis"><em>ない</em></span>ホストを指定します。このオプションは特定のホストやネットワークがサーバーをリクエストであふれさせるときに使われるべきです。デフォルトのオプションは <code class="literal">none</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">directory</code>
+ </td><td class="">
+ <code class="systemitem">named</code> サービスの作業ディレクトリを指定します。デフォルトオプションは <code class="literal">/var/named/</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">dnssec-enable</code>
+ </td><td class="">
+ DNSSEC 関連リソースレコードを返すかどうかを指定します。デフォルトオプションは <code class="literal">yes</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">dnssec-validation</code>
+ </td><td class="">
+ リソースレコードが DNSSEC 経由で認証されることを検証するかどうかを指定します。初期オプションは <code class="option">yes</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">forwarders</code>
+ </td><td class="">
+ 要求を解決するために転送されるネームサーバーの有効な IP アドレス一覧を指定します。
+ </td></tr><tr><td class="">
+ <code class="option">forward</code>
+ </td><td class="">
+ <div class="para">
+ <code class="option">forwarders</code> ディレクティブの挙動を指定します。以下のオプションを受け取ります:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">first</code> — The server will query the nameservers listed in the <code class="option">forwarders</code> directive before attempting to resolve the name on its own.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">only</code> — When unable to query the nameservers listed in the <code class="option">forwarders</code> directive, the server will not attempt to resolve the name on its own.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">listen-on</code>
+ </td><td class="">
+ 問い合わせを受け付ける IPv4 ネットワークインターフェースを指定します。ゲートウェイとしても動作する DNS サーバーにおいて、単一のネットワークのみから問い合わせを受け付けるために、このオプションを使用できます。すべての IPv4 インターフェースがデフォルトで使用されます。
+ </td></tr><tr><td class="">
+ <code class="option">listen-on-v6</code>
+ </td><td class="">
+ 問い合わせを受け付ける IPv6 ネットワークインターフェースを指定します。ゲートウェイとしても動作する DNS サーバーにおいて、単一のネットワークのみから問い合わせを受け付けるために、このオプションを使用できます。すべての IPv6 インターフェースがデフォルトで使用されます。
+ </td></tr><tr><td class="">
+ <code class="option">max-cache-size</code>
+ </td><td class="">
+ サーバーキャッシュのために使用されるメモリーの最大量を指定します。制限に達するとき、制限を越えないように、サーバーはレコードを早めに期限切れさせます。複数のビューを持つサーバーにおいては、制限は各ビューのキャッシュにそれぞれ適用されます。デフォルトのオプションは <code class="literal">32M</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">notify</code>
+ </td><td class="">
+ <div class="para">
+ ゾーンが更新されたときに、セカンダリーネームサーバーに通知するかどうかを指定します。以下のオプションを受け付けます:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — サーバーはすべてのセカンダリーネームサーバーに通知します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — サーバーはどのセカンダリーネームサーバーにも通知<span class="emphasis"><em>しません</em></span>。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — サーバーはゾーンのマスターサーバーのみに通知します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — zone 文の中の <code class="option">also-notify</code> 一覧に指定されているセカンダリーサーバーのみに通知します。
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">pid-file</code>
+ </td><td class="">
+ <code class="systemitem">named</code> サービスにより作成されるプロセス ID ファイルの位置を指定します。
+ </td></tr><tr><td class="">
+ <code class="option">recursion</code>
+ </td><td class="">
+ 再帰的サーバーとして動作するかどうかを指定します。オプションの初期値は <code class="literal">yes</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">statistics-file</code>
+ </td><td class="">
+ 統計ファイルの代替位置を指定します。<code class="filename">/var/named/named.stats</code> ファイルが標準で使用されます。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="important"><div class="admonition_header"><h2>Restrict recursive servers to selected clients only</h2></div><div class="admonition"><div class="para">
+ To prevent distributed denial of service (DDoS) attacks, it is recommended that you use the <code class="option">allow-query-cache</code> option to restrict recursive DNS services for a particular subset of clients only.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#s3-bind-installed-docs">「インストールされているドキュメント」</a>, and the <code class="filename">named.conf</code> manual page for a complete list of available options.
+ </div><div class="example" id="example-bind-namedconf-common-options"><h6>例12.3 options 宣言の使用法</h6><div class="example-contents"><pre class="programlisting">options {
+ allow-query { localhost; };
+ listen-on port 53 { 127.0.0.1; };
+ listen-on-v6 port 53 { ::1; };
+ max-cache-size 256M;
+ directory "/var/named";
+ statistics-file "/var/named/data/named_stats.txt";
+
+ recursion yes;
+ dnssec-enable yes;
+ dnssec-validation yes;
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm98104272" class="indexterm"></a>
+ <code class="option">zone</code></span></dt><dd><div class="para">
+ The <code class="option">zone</code> statement allows you to define the characteristics of a zone, such as the location of its configuration file and zone-specific options, and can be used to override the global <code class="option">options</code> statements. It takes the following form:
+ </div><pre class="programlisting">zone <em class="replaceable"><code>zone-name</code></em> [<em class="replaceable"><code>zone-class</code></em>] {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is the name of the zone, <em class="replaceable"><code>zone-class</code></em> is the optional class of the zone, and <em class="replaceable"><code>option</code></em> is a <code class="option">zone</code> statement option as described in <a class="xref" href="#table-bind-namedconf-common-zone">表12.4「一般的に使用されるオプション」</a>.
+ </div><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is particularly important, as it is the default value assigned for the <code class="option">$ORIGIN</code> directive used within the corresponding zone file located in the <code class="filename">/var/named/</code> directory. The <code class="systemitem">named</code> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file. For example, if a <code class="option">zone</code> statement defines the namespace for <code class="literal">example.com</code>, use <code class="literal">example.com</code> as the <em class="replaceable"><code>zone-name</code></em> so that it is placed at the end of hostnames within the <code class="literal">example.com</code> zone file.
+ </div><div class="para">
+ For more information about zone files, refer to <a class="xref" href="#s2-bind-zone">「ゾーンファイルの編集」</a>.
+ </div><div class="table" id="table-bind-namedconf-common-zone"><h6>表12.4 一般的に使用されるオプション</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">allow-query</code>
+ </td><td class="">
+ Specifies which clients are allowed to request information about this zone. This option overrides global <code class="option">allow-query</code> option. All query requests are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-transfer</code>
+ </td><td class="">
+ Specifies which secondary servers are allowed to request a transfer of the zone's information. All transfer requests are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-update</code>
+ </td><td class="">
+ <div class="para">
+ Specifies which hosts are allowed to dynamically update information in their zone. The default option is to deny all dynamic update requests.
+ </div>
+ <div class="para">
+ Note that you should be careful when allowing hosts to update information about their zone. Do not set IP addresses in this option unless the server is in the trusted network. Instead, use TSIG key as described in <a class="xref" href="#s3-bind-features-tsig">「Transaction SIGnatures (TSIG)」</a>.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="option">file</code>
+ </td><td class="">
+ Specifies the name of the file in the <code class="systemitem">named</code> working directory that contains the zone's configuration data.
+ </td></tr><tr><td class="">
+ <code class="option">masters</code>
+ </td><td class="">
+ Specifies from which IP addresses to request authoritative zone information. This option is used only if the zone is defined as <code class="option">type</code> <code class="option">slave</code>.
+ </td></tr><tr><td class="">
+ <code class="option">notify</code>
+ </td><td class="">
+ <div class="para">
+ ゾーンが更新されたときに、セカンダリーネームサーバーに通知するかどうかを指定します。以下のオプションを受け付けます:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — サーバーはすべてのセカンダリーネームサーバーに通知します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — サーバーはどのセカンダリーネームサーバーにも通知<span class="emphasis"><em>しません</em></span>。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — サーバーはゾーンのマスターサーバーのみに通知します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — zone 文の中の <code class="option">also-notify</code> 一覧に指定されているセカンダリーサーバーのみに通知します。
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">type</code>
+ </td><td class="">
+ <div class="para">
+ Specifies the zone type. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">delegation-only</code> — Enforces the delegation status of infrastructure zones such as COM, NET, or ORG. Any answer that is received without an explicit or implicit delegation is treated as <code class="literal">NXDOMAIN</code>. This option is only applicable in TLDs or root zone files used in recursive or caching implementations.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">forward</code> — Forwards all requests for information about this zone to other nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">hint</code> — A special type of zone used to point to the root nameservers which resolve queries when a zone is not otherwise known. No configuration beyond the default is necessary with a <code class="option">hint</code> zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master</code> — Designates the nameserver as authoritative for this zone. A zone should be set as the <code class="option">master</code> if the zone's configuration files reside on the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">slave</code> — Designates the nameserver as a slave server for this zone. Master server is specified in <code class="option">masters</code> directive.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Most changes to the <code class="filename">/etc/named.conf</code> file of a primary or secondary nameserver involve adding, modifying, or deleting <code class="option">zone</code> statements, and only a small subset of <code class="option">zone</code> statement options is usually needed for a nameserver to work efficiently.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-namedconf-common-zone-primary">例12.4「A zone statement for a primary nameserver」</a>, the zone is identified as <code class="literal">example.com</code>, the type is set to <code class="literal">master</code>, and the <code class="systemitem">named</code> service is instructed to read the <code class="filename">/var/named/example.com.zone</code> file. It also allows only a secondary nameserver (<code class="literal">192.168.0.2</code>) to transfer the zone.
+ </div><div class="example" id="example-bind-namedconf-common-zone-primary"><h6>例12.4 A zone statement for a primary nameserver</h6><div class="example-contents"><pre class="programlisting">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-transfer { 192.168.0.2; };
+};</pre></div></div><br class="example-break" /><div class="para">
+ A secondary server's <code class="option">zone</code> statement is slightly different. The type is set to <code class="literal">slave</code>, and the <code class="literal">masters</code> directive is telling <code class="systemitem">named</code> the IP address of the master server.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-namedconf-common-zone-secondary">例12.5「A zone statement for a secondary nameserver」</a>, the <code class="systemitem">named</code> service is configured to query the primary server at the <code class="literal">192.168.0.1</code> IP address for information about the <code class="literal">example.com</code> zone. The received information is then saved to the <code class="filename">/var/named/slaves/example.com.zone</code> file. Note that you have to put all slave zones to <code class="filename">/var/named/slaves</code> directory, otherwise the service will fail to transfer the zone.
+ </div><div class="example" id="example-bind-namedconf-common-zone-secondary"><h6>例12.5 A zone statement for a secondary nameserver</h6><div class="example-contents"><pre class="programlisting">zone "example.com" {
+ type slave;
+ file "slaves/example.com.zone";
+ masters { 192.168.0.1; };
+};</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s3-bind-namedconf-state-other"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.1.2. 他のステートメント形式</h4></div></div></div><div class="para">
+ The following types of statements are less commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm190593520" class="indexterm"></a>
+ <code class="option">controls</code></span></dt><dd><div class="para">
+ The <code class="option">controls</code> statement allows you to configure various security requirements necessary to use the <code class="command">rndc</code> command to administer the <code class="systemitem">named</code> service.
+ </div><div class="para">
+ <code class="command">rndc</code> ユーティリティとその使用法の詳細は<a class="xref" href="#s2-bind-rndc">「rndc ユーティリティの使用法」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm111434624" class="indexterm"></a>
+ <code class="option">key</code></span></dt><dd><div class="para">
+ The <code class="option">key</code> statement allows you to define a particular key by name. Keys are used to authenticate various actions, such as secure updates or the use of the <code class="command">rndc</code> command. Two options are used with <code class="option">key</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">algorithm <em class="replaceable"><code>algorithm-name</code></em></code> — 使用されるアルゴリズムの種類 (たとえば、<code class="literal">hmac-md5</code>)。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">secret "<em class="replaceable"><code>key-value</code></em>"</code> — 暗号化キー。
+ </div></li></ul></div><div class="para">
+ <code class="command">rndc</code> ユーティリティとその使用法の詳細は<a class="xref" href="#s2-bind-rndc">「rndc ユーティリティの使用法」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm120359216" class="indexterm"></a>
+ <code class="option">logging</code></span></dt><dd><div class="para">
+ The <code class="option">logging</code> statement allows you to use multiple types of logs, so called <em class="firstterm">channels</em>. By using the <code class="option">channel</code> option within the statement, you can construct a customized type of log with its own file name (<code class="option">file</code>), size limit (<code class="option">size</code>), versioning (<code class="option">version</code>), and level of importance (<code class="option">severity</code>). Once a customized channel is defined, a <code class="option">category</code> option is used to categorize the channel and begin logging when the <code class="systemitem">named</code> service is restarted.
+ </div><div class="para">
+ By default, <code class="systemitem">named</code> sends standard messages to the <code class="systemitem">rsyslog</code> daemon, which places them in <code class="filename">/var/log/messages</code>. Several standard channels are built into BIND with various severity levels, such as <code class="literal">default_syslog</code> (which handles informational logging messages) and <code class="literal">default_debug</code> (which specifically handles debugging messages). A default category, called <code class="literal">default</code>, uses the built-in channels to do normal logging without any special configuration.
+ </div><div class="para">
+ Customizing the logging process can be a very detailed process and is beyond the scope of this chapter. For information on creating custom BIND logs, refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#s3-bind-installed-docs">「インストールされているドキュメント」</a>.
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm114290224" class="indexterm"></a>
+ <code class="option">server</code></span></dt><dd><div class="para">
+ The <code class="option">server</code> statement allows you to specify options that affect how the <code class="systemitem">named</code> service should respond to remote nameservers, especially with regard to notifications and zone transfers.
+ </div><div class="para">
+ The <code class="option">transfer-format</code> option controls the number of resource records that are sent with each message. It can be either <code class="literal">one-answer</code> (only one resource record), or <code class="literal">many-answers</code> (multiple resource records). Note that while the <code class="literal">many-answers</code> option is more efficient, it is not supported by older versions of BIND.
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm113326048" class="indexterm"></a>
+ <code class="option">trusted-keys</code></span></dt><dd><div class="para">
+ The <code class="option">trusted-keys</code> statement allows you to specify assorted public keys used for secure DNS (DNSSEC). Refer to <a class="xref" href="#s3-bind-features-dnssec">「DNS Security Extensions (DNSSEC)」</a> for more information on this topic.
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm98728480" class="indexterm"></a>
+ <code class="option">view</code></span></dt><dd><div class="para">
+ The <code class="option">view</code> statement allows you to create special views depending upon which network the host querying the nameserver is on. This allows some hosts to receive one answer regarding a zone while other hosts receive totally different information. Alternatively, certain zones may only be made available to particular trusted hosts while non-trusted hosts can only make queries for other zones.
+ </div><div class="para">
+ Multiple views can be used as long as their names are unique. The <code class="option">match-clients</code> option allows you to specify the IP addresses that apply to a particular view. If the <code class="option">options</code> statement is used within a view, it overrides the already configured global options. Finally, most <code class="option">view</code> statements contain multiple <code class="option">zone</code> statements that apply to the <code class="option">match-clients</code> list.
+ </div><div class="para">
+ Note that the order in which the <code class="option">view</code> statements are listed is important, as the first statement that matches a particular client's IP address is used. For more information on this topic, refer to <a class="xref" href="#s3-bind-features-views">「複数ビュー」</a>.
+ </div></dd></dl></div></div><div class="section" id="s3-bind-namedconf-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.1.3. コメントタグ</h4></div></div></div><a id="idm112199536" class="indexterm"></a><div class="para">
+ Additionally to statements, the <code class="filename">/etc/named.conf</code> file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to a user. The following are valid comment tags:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="literal">//</code></span></dt><dd><div class="para">
+ <code class="literal">//</code> 文字列の後ろにあるテキストは行末までがコメントとみなされます。たとえば:
+ </div><pre class="programlisting">notify yes; // notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">#</code></span></dt><dd><div class="para">
+ <code class="literal">#</code> 記号の後ろにあるテキストは行末までがコメントとみなされます。たとえば:
+ </div><pre class="programlisting">notify yes; # notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">/*</code> と <code class="literal">*/</code></span></dt><dd><div class="para">
+ <code class="literal">/*</code> と <code class="literal">*/</code> に囲まれたテキストのブロックはコメントとみなされます。たとえば:
+ </div><pre class="programlisting">notify yes; /* notify all secondary nameservers */</pre></dd></dl></div></div></div><div class="section" id="s2-bind-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.2. ゾーンファイルの編集</h3></div></div></div><a id="idm122887056" class="indexterm"></a><a id="idm122890480" class="indexterm"></a><a id="idm122891888" class="indexterm"></a><a id="idm85477904" class="indexterm"></a><div class="para">
+ As outlined in <a class="xref" href="#s2-dns-introduction-zones">「ネームサーバーゾーン」</a>, zone files contain information about a namespace. They are stored in the <code class="systemitem">named</code> working directory located in <code class="filename">/var/named/</code> by default, and each zone file is named according to the <code class="option">file</code> option in the <code class="option">zone</code> statement, usually in a way that relates to the domain in question and identifies the file as containing zone data, such as <code class="filename">example.com.zone</code>.
+ </div><div class="table" id="table-bind-zone-files"><h6>表12.5 The named service zone files</h6><div class="table-contents"><table summary="The named service zone files" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="filename">/var/named/</code>
+ </td><td class="">
+ <code class="systemitem">named</code> サービスの作業ディレクトリです。ネームサーバーはこのディレクトリに書き込みが許可<span class="emphasis"><em>されません</em></span>。
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/slaves/</code>
+ </td><td class="">
+ セカンダリ・ゾーン向けのディレクトリです。このディレクトリは <code class="systemitem">named</code> サービスにより書き込み可能です。
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/dynamic/</code>
+ </td><td class="">
+ The directory for other files, such as dynamic DNS (DDNS) zones or managed DNSSEC keys. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/data/</code>
+ </td><td class="">
+ The directory for various statistics and debugging files. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ A zone file consists of directives and resource records. Directives tell the nameserver to perform tasks or apply special settings to the zone, resource records define the parameters of the zone and assign identities to individual hosts. While the directives are optional, the resource records are required in order to provide name service to a zone.
+ </div><div class="para">
+ すべてのディレクティブとリソースレコードは、個々の行に記載する必要があります。
+ </div><div class="section" id="s3-bind-zone-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.2.1. 一般的なディレクティブ</h4></div></div></div><div class="para">
+ Directives begin with the dollar sign character (that is, <code class="literal">$</code>) followed by the name of the directive, and usually appear at the top of the file. The following directives are commonly used in zone files:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm133530304" class="indexterm"></a>
+ <code class="command">$INCLUDE</code></span></dt><dd><div class="para">
+ The <code class="command">$INCLUDE</code> directive allows you to include another file at the place where it appears, so that other zone settings can be stored in a separate zone file.
+ </div><div class="example" id="example-bind-zone-directive-include"><h6>例12.6 $INCLUDE ディレクティブの使用法</h6><div class="example-contents"><pre class="programlisting">$INCLUDE /var/named/penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm138169184" class="indexterm"></a>
+ <code class="command">$ORIGIN</code></span></dt><dd><div class="para">
+ The <code class="command">$ORIGIN</code> directive allows you to append the domain name to unqualified records, such as those with the hostname only. Note that the use of this directive is not necessary if the zone is specified in <code class="filename">/etc/named.conf</code>, since the zone name is used by default.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-directive-origin">例12.7「$ORIGIN ディレクティブの使用法」</a>, any names used in resource records that do not end in a trailing period (that is, the <code class="literal">.</code> character) are appended with <code class="literal">example.com</code>.
+ </div><div class="example" id="example-bind-zone-directive-origin"><h6>例12.7 $ORIGIN ディレクティブの使用法</h6><div class="example-contents"><pre class="programlisting">$ORIGIN example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm106936784" class="indexterm"></a>
+ <code class="command">$TTL</code></span></dt><dd><div class="para">
+ The <code class="command">$TTL</code> directive allows you to set the default <em class="firstterm">Time to Live</em> (TTL) value for the zone, that is, how long is a zone record valid. Each resource record can contain its own TTL value, which overrides this directive.
+ </div><div class="para">
+ この値を増加させると、リモートネームサーバーは、このゾーンの情報をより長時間キャッシュします。こうすると、このゾーンについて行われるクエリの数は減りますが、リソースレコード変更を伝えるのに要する時間は長くなります。
+ </div><div class="example" id="example-bind-zone-directive-ttl"><h6>例12.8 $TTL ディレクティブの使用</h6><div class="example-contents"><pre class="programlisting">$TTL 1D</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s4-bind-zone-rr"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.2.2. Common Resource Records</h4></div></div></div><div class="para">
+ The following resource records are commonly used in zone files:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm109942720" class="indexterm"></a>
+ <code class="command">A</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Address</em> record specifies an IP address to be assigned to a name. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>hostname</code></em> IN A <em class="replaceable"><code>IP-address</code></em></pre><div class="para">
+ If the <em class="replaceable"><code>hostname</code></em> value is omitted, the record will point to the last specified <em class="replaceable"><code>hostname</code></em>.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-a">例12.9「A リソースレコードの使用法」</a>, the requests for <code class="systemitem">server1.example.com</code> are pointed to <code class="literal">10.0.1.3</code> or <code class="literal">10.0.1.5</code>.
+ </div><div class="example" id="example-bind-zone-rr-a"><h6>例12.9 A リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">server1 IN A 10.0.1.3
+ IN A 10.0.1.5</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm112085696" class="indexterm"></a>
+ <code class="command">CNAME</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Canonical Name</em> record maps one name to another. Because of this, this type of record is sometimes referred to as an <em class="firstterm">alias record</em>. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>alias-name</code></em> IN CNAME <em class="replaceable"><code>real-name</code></em></pre><div class="para">
+ <code class="command">CNAME</code> records are most commonly used to point to services that use a common naming scheme, such as <code class="literal">www</code> for Web servers. However, there are multiple restrictions for their usage:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ CNAME records should not point to other CNAME records. This is mainly to avoid possible infinite loops.
+ </div></li><li class="listitem"><div class="para">
+ CNAME records should not contain other resource record types (such as A, NS, MX, etc.). The only exception are DNSSEC related records (that is, RRSIG, NSEC, etc.) when the zone is signed.
+ </div></li><li class="listitem"><div class="para">
+ Other resource record that point to the fully qualified domain name (FQDN) of a host (that is, NS, MX, PTR) should not point to a CNAME record.
+ </div></li></ul></div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-cname">例12.10「CNAME リソースレコードの使用法」</a>, the <code class="command">A</code> record binds a hostname to an IP address, while the <code class="command">CNAME</code> record points the commonly used <code class="literal">www</code> hostname to it.
+ </div><div class="example" id="example-bind-zone-rr-cname"><h6>例12.10 CNAME リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">server1 IN A 10.0.1.5
+www IN CNAME server1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm88988096" class="indexterm"></a>
+ <code class="command">MX</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Mail Exchange</em> record specifies where the mail sent to a particular namespace controlled by this zone should go. It takes the following form:
+ </div><pre class="programlisting">IN MX <em class="replaceable"><code>preference-value</code></em> <em class="replaceable"><code>email-server-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>email-server-name</code></em> is a fully qualified domain name (FQDN). The <em class="replaceable"><code>preference-value</code></em> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <code class="command">MX</code> resource record with the lowest <em class="replaceable"><code>preference-value</code></em> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-mx">例12.11「MX リソースレコードの使用法」</a>, the first <code class="systemitem">mail.example.com</code> email server is preferred to the <code class="systemitem">mail2.example.com</code> email server when receiving email destined for the <code class="systemitem">example.com</code> domain.
+ </div><div class="example" id="example-bind-zone-rr-mx"><h6>例12.11 MX リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">example.com. IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm94754592" class="indexterm"></a>
+ <code class="command">NS</code></span></dt><dd><div class="para">
+ <em class="firstterm">ネームサーバー</em>レコードは、他のゾーンに対する権威ネームサーバーを知らせます。以下の形式をとります:
+ </div><pre class="programlisting">IN NS <em class="replaceable"><code>nameserver-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>nameserver-name</code></em> should be a fully qualified domain name (FQDN). Note that when two nameservers are listed as authoritative for the domain, it is not important whether these nameservers are secondary nameservers, or if one of them is a primary server. They are both still considered authoritative.
+ </div><div class="example" id="example-bind-zone-rr-ns"><h6>例12.12 NS リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">IN NS dns1.example.com.
+IN NS dns2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm108861728" class="indexterm"></a>
+ <code class="command">PTR</code></span></dt><dd><div class="para">
+ <em class="firstterm">ポインター</em> レコードは、名前空間の他の場所を示します。以下の形式をとります:
+ </div><pre class="programlisting"><em class="replaceable"><code>last-IP-digit</code></em> IN PTR <em class="replaceable"><code>FQDN-of-system</code></em></pre><div class="para">
+ The <em class="replaceable"><code>last-IP-digit</code></em> directive is the last number in an IP address, and the <em class="replaceable"><code>FQDN-of-system</code></em> is a fully qualified domain name (FQDN).
+ </div><div class="para">
+ <code class="command">PTR</code> records are primarily used for reverse name resolution, as they point IP addresses back to a particular name. Refer to <a class="xref" href="#s3-bind-configuration-zone-reverse">「逆引き名前解決ゾーンファイル」</a> for more examples of <code class="command">PTR</code> records in use.
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm80232640" class="indexterm"></a>
+ <code class="command">SOA</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Start of Authority</em> record announces important authoritative information about a namespace to the nameserver. Located after the directives, it is the first resource record in a zone file. It takes the following form:
+ </div><pre class="programlisting">@ IN SOA <em class="replaceable"><code>primary-name-server</code></em> <em class="replaceable"><code>hostmaster-email</code></em> (
+ <em class="replaceable"><code>serial-number</code></em>
+ <em class="replaceable"><code>time-to-refresh</code></em>
+ <em class="replaceable"><code>time-to-retry</code></em>
+ <em class="replaceable"><code>time-to-expire</code></em>
+ <em class="replaceable"><code>minimum-TTL</code></em> )</pre><div class="para">
+ ディレクティブは以下のとおりです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="literal">@</code> symbol places the <code class="command">$ORIGIN</code> directive (or the zone's name if the <code class="command">$ORIGIN</code> directive is not set) as the namespace being defined by this <code class="command">SOA</code> resource record.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>primary-name-server</code></em> directive is the hostname of the primary nameserver that is authoritative for this domain.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>hostmaster-email</code></em> directive is the email of the person to contact about the namespace.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>serial-number</code></em> directive is a numerical value incremented every time the zone file is altered to indicate it is time for the <code class="systemitem">named</code> service to reload the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-refresh</code></em> directive is the numerical value secondary nameservers use to determine how long to wait before asking the primary nameserver if any changes have been made to the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-retry</code></em> directive is a numerical value used by secondary nameservers to determine the length of time to wait before issuing a refresh request in the event that the primary nameserver is not answering. If the primary server has not replied to a refresh request before the amount of time specified in the <em class="replaceable"><code>time-to-expire</code></em> directive elapses, the secondary servers stop responding as an authority for requests concerning that namespace.
+ </div></li><li class="listitem"><div class="para">
+ In BIND 4 and 8, the <em class="replaceable"><code>minimum-TTL</code></em> directive is the amount of time other nameservers cache the zone's information. In BIND 9, it defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (that is, <code class="option">3H</code>).
+ </div></li></ul></div><div class="para">
+ When configuring BIND, all times are specified in seconds. However, it is possible to use abbreviations when specifying units of time other than seconds, such as minutes (<code class="literal">M</code>), hours (<code class="literal">H</code>), days (<code class="literal">D</code>), and weeks (<code class="literal">W</code>). <a class="xref" href="#tb-bind-seconds">表12.6「他の時間単位と比較した秒数」</a> shows an amount of time in seconds and the equivalent time in another format.
+ </div><div class="table" id="tb-bind-seconds"><h6>表12.6 他の時間単位と比較した秒数</h6><div class="table-contents"><table summary="他の時間単位と比較した秒数" border="1"><colgroup><col width="50%" class="seconds" /><col width="50%" class="other" /></colgroup><thead><tr><th class="">
+ 秒
+ </th><th class="">
+ 他の時間単位
+ </th></tr></thead><tbody><tr><td class="">
+ 60
+ </td><td class="">
+ <code class="literal">1M</code>
+ </td></tr><tr><td class="">
+ 1800
+ </td><td class="">
+ <code class="literal">30M</code>
+ </td></tr><tr><td class="">
+ 3600
+ </td><td class="">
+ <code class="literal">1H</code>
+ </td></tr><tr><td class="">
+ 10800
+ </td><td class="">
+ <code class="literal">3H</code>
+ </td></tr><tr><td class="">
+ 21600
+ </td><td class="">
+ <code class="literal">6H</code>
+ </td></tr><tr><td class="">
+ 43200
+ </td><td class="">
+ <code class="literal">12H</code>
+ </td></tr><tr><td class="">
+ 86400
+ </td><td class="">
+ <code class="literal">1D</code>
+ </td></tr><tr><td class="">
+ 259200
+ </td><td class="">
+ <code class="literal">3D</code>
+ </td></tr><tr><td class="">
+ 604800
+ </td><td class="">
+ <code class="literal">1W</code>
+ </td></tr><tr><td class="">
+ 31536000
+ </td><td class="">
+ <code class="literal">365D</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-bind-zone-rr-soa"><h6>例12.13 SOA リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s3-bind-zone-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.2.3. コメントタグ</h4></div></div></div><a id="idm137306272" class="indexterm"></a><div class="para">
+ Additionally to resource records and directives, a zone file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to the user. Any text after the semicolon character (that is, <code class="literal">;</code>) to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting"> 604800 ; 1 週間後に期限切れ</pre></div><div class="section" id="s3-bind-zone-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.2.4. 使用例</h4></div></div></div><div class="para">
+ 以下の例はゾーンファイルの基本的な使用法を示しています。
+ </div><div class="section" id="s4-bind-zone-examples-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.2.2.4.1. 簡単なゾーンファイル</h5></div></div></div><a id="idm99322912" class="indexterm"></a><div class="para">
+ <a class="xref" href="#example-bind-zone-examples-basic">例12.14「簡単なゾーンファイル」</a>は標準的なディレクティブと <code class="command">SOA</code> 値の使用法を説明します。
+ </div><div class="example" id="example-bind-zone-examples-basic"><h6>例12.14 簡単なゾーンファイル</h6><div class="example-contents"><pre class="programlisting">$ORIGIN example.com.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+;
+ IN NS dns1.example.com.
+ IN NS dns2.example.com.
+dns1 IN A 10.0.1.1
+ IN AAAA aaaa:bbbb::1
+dns2 IN A 10.0.1.2
+ IN AAAA aaaa:bbbb::2
+;
+;
+@ IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.
+mail IN A 10.0.1.5
+ IN AAAA aaaa:bbbb::5
+mail2 IN A 10.0.1.6
+ IN AAAA aaaa:bbbb::6
+;
+;
+; This sample zone file illustrates sharing the same IP addresses
+; for multiple services:
+;
+services IN A 10.0.1.10
+ IN AAAA aaaa:bbbb::10
+ IN A 10.0.1.11
+ IN AAAA aaaa:bbbb::11
+
+ftp IN CNAME services.example.com.
+www IN CNAME services.example.com.
+;
+;</pre></div></div><br class="example-break" /><div class="para">
+ In this example, the authoritative nameservers are set as <code class="systemitem">dns1.example.com</code> and <code class="systemitem">dns2.example.com</code>, and are tied to the <code class="systemitem">10.0.1.1</code> and <code class="systemitem">10.0.1.2</code> IP addresses respectively using the <code class="command">A</code> record.
+ </div><div class="para">
+ The email servers configured with the <code class="command">MX</code> records point to <code class="systemitem">mail</code> and <code class="systemitem">mail2</code> via <code class="command">A</code> records. Since these names do not end in a trailing period (that is, the <code class="literal">.</code> character), the <code class="command">$ORIGIN</code> domain is placed after them, expanding them to <code class="systemitem">mail.example.com</code> and <code class="systemitem">mail2.example.com</code>.
+ </div><div class="para">
+ Services available at the standard names, such as <code class="systemitem">www.example.com</code> (<acronym class="acronym">WWW</acronym>), are pointed at the appropriate servers using the <code class="command">CNAME</code> record.
+ </div><div class="para">
+ このゾーンファイルは、<code class="filename">/etc/named.conf</code> ファイルにおいて、以下のような <code class="option">zone</code> ステートメントを用いたサービスの中に呼び出されます:
+ </div><pre class="programlisting">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-update { none; };
+};</pre></div><div class="section" id="s3-bind-configuration-zone-reverse"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.2.2.4.2. 逆引き名前解決ゾーンファイル</h5></div></div></div><a id="idm139720048" class="indexterm"></a><div class="para">
+ 逆引き名前解決ゾーンファイルは、特定の名前空間にある IP アドレスを完全修飾ドメイン名（FQDN）に変換するために使用されます。これは、<a class="xref" href="#example-bind-zone-examples-reverse">例12.15「逆引き名前解決ゾーンファイル」</a>にあるよように、<code class="command">PTR</code> リソースレコードが IP アドレスを完全修飾ドメイン名にリンクするために使用されることを除いて、標準的なゾーンファイルによく似ています。
+ </div><div class="example" id="example-bind-zone-examples-reverse"><h6>例12.15 逆引き名前解決ゾーンファイル</h6><div class="example-contents"><pre class="programlisting">$ORIGIN 1.0.10.in-addr.arpa.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+@ IN NS dns1.example.com.
+;
+1 IN PTR dns1.example.com.
+2 IN PTR dns2.example.com.
+;
+5 IN PTR server1.example.com.
+6 IN PTR server2.example.com.
+;
+3 IN PTR ftp.example.com.
+4 IN PTR ftp.example.com.</pre></div></div><br class="example-break" /><div class="para">
+ この例において、IP アドレス <code class="systemitem">10.0.1.1</code> から <code class="systemitem">10.0.1.6</code> は対応する完全修飾ドメイン名に対応づけられます。
+ </div><div class="para">
+ このゾーンファイルは、<code class="filename">/etc/named.conf</code> ファイルにおいて、以下のような <code class="option">zone</code> ステートメントを用いたサービスの中に呼び出されます:
+ </div><pre class="programlisting">zone "1.0.10.in-addr.arpa" IN {
+ type master;
+ file "example.com.rr.zone";
+ allow-update { none; };
+};</pre><div class="para">
+ There is very little difference between this example and a standard <code class="command">zone</code> statement, except for the zone name. Note that a reverse name resolution zone requires the first three blocks of the IP address reversed followed by <code class="command">.in-addr.arpa</code>. This allows the single block of IP numbers used in the reverse name resolution zone file to be associated with the zone.
+ </div></div></div></div><div class="section" id="s2-bind-rndc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.3. rndc ユーティリティの使用法</h3></div></div></div><a id="idm124148096" class="indexterm"></a><div class="para">
+ <code class="command">rndc</code> ユーティリティは、<code class="systemitem">named</code> サービスをローカルおよびリモートマシンから管理できるコマンドラインツールです。以下のように使用します:
+ </div><pre class="screen"><code class="command">rndc</code> [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command-option</code></em>]</pre><div class="section" id="s3-bind-rndc-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.1. ユーティリティの設定法</h4></div></div></div><div class="para">
+ To prevent unauthorized access to the service, <code class="systemitem">named</code> must be configured to listen on the selected port (that is, <code class="literal">953</code> by default), and an identical key must be used by both the service and the <code class="command">rndc</code> utility.
+ </div><div class="table" id="table-bind-rndc-configuration-files"><h6>表12.7 関連ファイル</h6><div class="table-contents"><table summary="関連ファイル" border="1"><colgroup><col width="38%" class="path" /><col width="63%" class="description" /></colgroup><thead><tr><th class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <a id="idm139723504" class="indexterm"></a>
+ <code class="filename">/etc/named.conf</code>
+ </td><td class="">
+ <code class="systemitem">named</code> サービスのデフォルトの設定ファイルです。
+ </td></tr><tr><td class="">
+ <a id="idm108823072" class="indexterm"></a>
+ <code class="filename">/etc/rndc.conf</code>
+ </td><td class="">
+ <code class="command">rndc</code> ユーティリティのデフォルトの設定ファイルです。
+ </td></tr><tr><td class="">
+ <a id="idm108919712" class="indexterm"></a>
+ <code class="filename">/etc/rndc.key</code>
+ </td><td class="">
+ キーのデフォルトの場所です。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">rndc</code> configuration is located in <code class="filename">/etc/rndc.conf</code>. If the file does not exist, the utility will use the key located in <code class="filename">/etc/rndc.key</code>, which was generated automatically during the installation process using the <code class="command">rndc-confgen -a</code> command.
+ </div><div class="para">
+ The <code class="systemitem">named</code> service is configured using the <code class="option">controls</code> statement in the <code class="filename">/etc/named.conf</code> configuration file as described in <a class="xref" href="#s3-bind-namedconf-state-other">「他のステートメント形式」</a>. Unless this statement is present, only the connections from the loopback address (that is, <code class="systemitem">127.0.0.1</code>) will be allowed, and the key located in <code class="filename">/etc/rndc.key</code> will be used.
+ </div><div class="para">
+ For more information on this topic, refer to manual pages and the <em class="citetitle">BIND 9 Administrator Reference Manual</em> listed in <a class="xref" href="#s2-bind-additional-resources">「その他のリソース」</a>.
+ </div><div class="important"><div class="admonition_header"><h2>正しいパーミッションを設定します</h2></div><div class="admonition"><div class="para">
+ 権限のないユーザーがサービスに制御コマンドを送るのを防ぐには、確実に root のみが <code class="filename">/etc/rndc.key</code> ファイルを読み込めるようにします。
+ </div><pre class="screen">~]# <code class="command">chmod o-rwx /etc/rndc.key</code></pre></div></div></div><div class="section" id="s3-bind-rndc-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.2. サービスの状態の確認法</h4></div></div></div><div class="para">
+ <code class="systemitem">named</code> サービスの現在の状態を確認するには、以下のコマンドを使用します:
+ </div><pre class="screen">~]# <code class="command">rndc status</code>
+version: 9.7.0-P2-RedHat-9.7.0-5.P2.el6
+CPUs found: 1
+worker threads: 1
+number of zones: 16
+debug level: 0
+xfers running: 0
+xfers deferred: 0
+soa queries in progress: 0
+query logging is OFF
+recursive clients: 0/0/1000
+tcp clients: 0/100
+server is up and running</pre></div><div class="section" id="s3-bind-rndc-reload"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.3. 設定およびゾーン情報の再読み込み</h4></div></div></div><div class="para">
+ To reload both the configuration file and zones, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">rndc reload</code>
+server reload successful</pre><div class="para">
+ This will reload the zones while keeping all previously cached responses, so that you can make changes to the zone files without losing all stored name resolutions.
+ </div><div class="para">
+ To reload a single zone, specify its name after the <code class="command">reload</code> command, for example:
+ </div><pre class="screen">~]# <code class="command">rndc reload localhost</code>
+zone reload up-to-date</pre><div class="para">
+ 最後に、設定ファイルを読み込み、新しく追加されたゾーンのみを追加するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">rndc reconfig</code></pre><div class="note"><div class="admonition_header"><h2>ダイナミック DNS を用いたゾーンの編集</h2></div><div class="admonition"><div class="para">
+ ダイナミック DNS (DDNS: Dynamic DNS) を使用するゾーンを手動で編集したければ、まず <code class="command">freeze</code> コマンドを必ず実行してください:
+ </div><pre class="screen">~]# <code class="command">rndc freeze localhost</code></pre><div class="para">
+ 完了すると、再び DDNS を許可するために <code class="command">thaw</code> コマンドを実行して、ゾーンを再読み込みします:
+ </div><pre class="screen">~]# <code class="command">rndc thaw localhost</code>
+The zone reload and thaw was successful.</pre></div></div></div><div class="section" id="s3-bind-rndc-sign"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.4. ゾーンキーの更新</h4></div></div></div><div class="para">
+ DNSSEC キーを更新して、ゾーンを署名するには、<code class="command">sign</code> コマンドを使用します。たとえば:
+ </div><pre class="screen">~]# <code class="command">rndc sign localhost</code></pre><div class="para">
+ 上のコマンドを用いてゾーンを署名するには、<code class="option">auto-dnssec</code> オプションが zone ステートメントにおいて <code class="literal">maintain</code> に設定されていなければいけないことに注意してください。たとえば:
+ </div><pre class="programlisting">zone "localhost" IN {
+ type master;
+ file "named.localhost";
+ allow-update { none; };
+ auto-dnssec maintain;
+};</pre></div><div class="section" id="s3-bind-rndc-validation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.5. DNSSEC 検証の有効化</h4></div></div></div><div class="para">
+ DNSSEC 検証を有効にするには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">rndc validation on</code></pre><div class="para">
+ 同様に、このオプションを無効にするには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">rndc validation off</code></pre><div class="para">
+ <code class="filename">/etc/named.conf</code> においてこのオプションを設定する方法については<code class="option">options</code> statement described in <a class="xref" href="#s3-bind-namedconf-state">「一般的なステートメントのタイプ」</a>を参照してください。
+ </div></div><div class="section" id="s3-bind-rndc-querylog"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.6. クエリーロギングの有効化</h4></div></div></div><div class="para">
+ クエリーロギングを有効（または現在有効な場合に無効）にするには、以下のコマンドを実行します:
+ </div><pre class="screen">~]# <code class="command">rndc querylog</code></pre><div class="para">
+ 現在の設定を確認するには、<a class="xref" href="#s3-bind-rndc-status">「サービスの状態の確認法」</a> で説明されているように <code class="command">status</code> コマンドを使用します。
+ </div></div></div><div class="section" id="s2-bind-dig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.4. dig ユーティリティの使用</h3></div></div></div><a id="idm97693136" class="indexterm"></a><div class="para">
+ <code class="command">dig</code> ユーティリティは、DNS 検索の実行およびネームサーバーの設定のデバッグを実行できるようにするコマンドラインツールです。その典型的な使用方法は以下のとおりです:
+ </div><pre class="screen"><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>type</code></em></pre><div class="para">
+ 一般的な <em class="replaceable"><code>type</code></em> の一覧は<a class="xref" href="#s4-bind-zone-rr">「Common Resource Records」</a>を参照してください。
+ </div><div class="section" id="s3-bind-dig-ns"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.4.1. ネームサーバーの検索</h4></div></div></div><div class="para">
+ 特定のドメインに対するネームサーバーを検索するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> NS</pre><div class="para">
+ <a class="xref" href="#example-bind-dig-ns">例12.16「ネームサーバーの検索例」</a>において、<code class="command">dig</code> ユーティリティが <code class="systemitem">example.com</code> のネームサーバーを表示するために使用されます。
+ </div><div class="example" id="example-bind-dig-ns"><h6>例12.16 ネームサーバーの検索例</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com NS</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com NS
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57883
+;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN NS
+
+;; ANSWER SECTION:
+example.com. 99374 IN NS a.iana-servers.net.
+example.com. 99374 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:04:06 2010
+;; MSG SIZE rcvd: 77</pre></div></div><br class="example-break" /></div><div class="section" id="s3-bind-dig-a"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.4.2. IP アドレスの検索</h4></div></div></div><div class="para">
+ 特定のドメインに割り当てられた IP アドレスを検索するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> A</pre><div class="para">
+ <a class="xref" href="#example-bind-dig-a">例12.17「IP アドレスの検索例」</a>において、<code class="command">dig</code> ユーティリティが <code class="systemitem">example.com</code> の IP アドレスを表示するために使用されます。
+ </div><div class="example" id="example-bind-dig-a"><h6>例12.17 IP アドレスの検索例</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com A</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com A
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4849
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN A
+
+;; ANSWER SECTION:
+example.com. 155606 IN A 192.0.32.10
+
+;; AUTHORITY SECTION:
+example.com. 99175 IN NS a.iana-servers.net.
+example.com. 99175 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:07:25 2010
+;; MSG SIZE rcvd: 93</pre></div></div><br class="example-break" /></div><div class="section" id="s3-bind-dig-x"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.4.3. ホスト名の検索</h4></div></div></div><div class="para">
+ 特定の IP アドレスに対するホスト名を検索するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code class="command">dig</code> <code class="option">-x</code> <em class="replaceable"><code>address</code></em></pre><div class="para">
+ <a class="xref" href="#example-bind-dig-x">例12.18「ホスト名の検索例」</a>において、<code class="command">dig</code> ユーティリティが <code class="systemitem">192.0.32.10</code> に割り当てられたホスト名を表示するために使用されます。
+ </div><div class="example" id="example-bind-dig-x"><h6>例12.18 ホスト名の検索例</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig -x 192.0.32.10</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> -x 192.0.32.10
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29683
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6
+
+;; QUESTION SECTION:
+;10.32.0.192.in-addr.arpa. IN PTR
+
+;; ANSWER SECTION:
+10.32.0.192.in-addr.arpa. 21600 IN PTR www.example.com.
+
+;; AUTHORITY SECTION:
+32.0.192.in-addr.arpa. 21600 IN NS b.iana-servers.org.
+32.0.192.in-addr.arpa. 21600 IN NS c.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS d.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS ns.icann.org.
+32.0.192.in-addr.arpa. 21600 IN NS a.iana-servers.net.
+
+;; ADDITIONAL SECTION:
+a.iana-servers.net. 13688 IN A 192.0.34.43
+b.iana-servers.org. 5844 IN A 193.0.0.236
+b.iana-servers.org. 5844 IN AAAA 2001:610:240:2::c100:ec
+c.iana-servers.net. 12173 IN A 139.91.1.10
+c.iana-servers.net. 12173 IN AAAA 2001:648:2c30::1:10
+ns.icann.org. 12884 IN A 192.0.34.126
+
+;; Query time: 156 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:25:15 2010
+;; MSG SIZE rcvd: 310</pre></div></div><br class="example-break" /></div></div><div class="section" id="s2-bind-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.5. BIND の高度な機能</h3></div></div></div><div class="para">
+ Most BIND implementations only use the <code class="systemitem">named</code> service to provide name resolution services or to act as an authority for a particular domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient DNS service.
+ </div><div class="important"><div class="admonition_header"><h2>機能がサポートされていることを確認します</h2></div><div class="admonition"><div class="para">
+ DNSSEC, TSIG, た IXFR のような高度な機能を使用しようとする前に、とくに古いバージョンの BIND や BIND 以外のサーバーを使用するときに、その機能がネットワーク環境にあるすべてのネームサーバーにおいてサポートされていることを確認してください。
+ </div></div></div><div class="para">
+ All of the features mentioned are discussed in greater detail in the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#s3-bind-installed-docs">「インストールされているドキュメント」</a>.
+ </div><div class="section" id="s3-bind-features-views"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.1. 複数ビュー</h4></div></div></div><a id="idm104353168" class="indexterm"></a><div class="para">
+ Optionally, different information can be presented to a client depending on the network a request originates from. This is primarily used to deny sensitive DNS entries from clients outside of the local network, while allowing queries from clients inside the local network.
+ </div><div class="para">
+ To configure multiple views, add the <code class="command">view</code> statement to the <code class="filename">/etc/named.conf</code> configuration file. Use the <code class="option">match-clients</code> option to match IP addresses or entire networks and give them special options and zone data.
+ </div></div><div class="section" id="s3-bind-features-ixfr"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.2. Incremental Zone Transfers (IXFR)</h4></div></div></div><a id="idm94768560" class="indexterm"></a><div class="para">
+ <em class="firstterm">Incremental Zone Transfers</em> (<em class="firstterm">IXFR</em>) allow a secondary nameserver to only download the updated portions of a zone modified on a primary nameserver. Compared to the standard transfer process, this makes the notification and update process much more efficient.
+ </div><a id="idm105117136" class="indexterm"></a><div class="para">
+ Note that IXFR is only available when using dynamic updating to make changes to master zone records. If manually editing zone files to make changes, <em class="firstterm">Automatic Zone Transfer</em> (<em class="firstterm">AXFR</em>) is used.
+ </div></div><div class="section" id="s3-bind-features-tsig"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.3. Transaction SIGnatures (TSIG)</h4></div></div></div><a id="idm117156672" class="indexterm"></a><div class="para">
+ <em class="firstterm">Transaction SIGnatures</em> (TSIG) ensure that a shared secret key exists on both primary and secondary nameserver before allowing a transfer. This strengthens the standard IP address-based method of transfer authorization, since attackers would not only need to have access to the IP address to transfer the zone, but they would also need to know the secret key.
+ </div><div class="para">
+ Since version 9, BIND also supports <em class="firstterm">TKEY</em>, which is another shared secret key method of authorizing zone transfers.
+ </div><div class="important"><div class="admonition_header"><h2>Secure the transfer</h2></div><div class="admonition"><div class="para">
+ When communicating over an insecure network, do not rely on IP address-based authentication only.
+ </div></div></div></div><div class="section" id="s3-bind-features-dnssec"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.4. DNS Security Extensions (DNSSEC)</h4></div></div></div><a id="idm94514016" class="indexterm"></a><div class="para">
+ <em class="firstterm">Domain Name System Security Extensions</em> (<em class="firstterm">DNSSEC</em>) provide origin authentication of DNS data, authenticated denial of existence, and data integrity. When a particular domain is marked as secure, the <code class="literal">SERFVAIL</code> response is returned for each resource record that fails the validation.
+ </div><a id="idm123971744" class="indexterm"></a><div class="para">
+ Note that to debug a DNSSEC-signed domain or a DNSSEC-aware resolver, you can use the <code class="command">dig</code> utility as described in <a class="xref" href="#s2-bind-dig">「dig ユーティリティの使用」</a>. Useful options are <code class="option">+dnssec</code> (requests DNSSEC-related resource records by setting the DNSSEC OK bit), <code class="option">+cd</code> (tells recursive nameserver not to validate the response), and <code class="option">+bufsize=512</code> (changes the packet size to 512B to get through some firewalls).
+ </div></div><div class="section" id="s3-bind-features-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.5. インターネットプロトコル・バージョン 6 (IPv6: Internet Protocol version 6)</h4></div></div></div><a id="idm122422336" class="indexterm"></a><div class="para">
+ <em class="firstterm">Internet Protocol version 6</em> (<em class="firstterm">IPv6</em>) is supported through the use of <code class="option">AAAA</code> resource records, and the <code class="option">listen-on-v6</code> directive as described in <a class="xref" href="#table-bind-namedconf-common-options">表12.3「一般的に使用されるオプション」</a>.
+ </div></div></div><div class="section" id="s2-bind-mistakes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.6. よくある間違いを避けるために</h3></div></div></div><a id="idm98246064" class="indexterm"></a><div class="para">
+ The following is a list of advices how to avoid common mistakes users make when configuring a nameserver:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Use semicolons and curly brackets correctly</span></dt><dd><div class="para">
+ An omitted semicolon or unmatched curly bracket in the <code class="filename">/etc/named.conf</code> file can prevent the <code class="systemitem">named</code> service from starting.
+ </div></dd><dt class="varlistentry"><span class="term">Use period (that is, the <code class="literal">.</code> character) correctly</span></dt><dd><div class="para">
+ In zone files, a period at the end of a domain name denotes a fully qualified domain name. If omitted, the <code class="systemitem">named</code> service will append the name of the zone or the value of <code class="option">$ORIGIN</code> to complete it.
+ </div></dd><dt class="varlistentry"><span class="term">Increment the serial number when editing a zone file</span></dt><dd><div class="para">
+ If the serial number is not incremented, the primary nameserver will have the correct, new information, but the secondary nameservers will never be notified of the change, and will not attempt to refresh their data of that zone.
+ </div></dd><dt class="varlistentry"><span class="term">ファイアウォールを設定します</span></dt><dd><div class="para">
+ ファイアウォールが <code class="systemitem">named</code> サービスから他のネームサーバーへの接続をブロックするならば、推奨される最善策はできる限りファイアウォールの設定を変更することです。
+ </div><div class="warning" id="warning-Warning-Avoid_Using_Fixed_UDP_Source_Ports"><div class="admonition_header"><h2>固定 UDP ポートの使用を避けます</h2></div><div class="admonition"><div class="para">
+ DNS セキュリティに関する最近の研究によると、DNS の問い合わせに固定 UDP ポートを使用することは、潜在的なセキュリティ脆弱性となります。これは、攻撃者がより簡単にキャッシュポイズニングを引き起こせます。これを防ぐには、ファイアウォールがランダム UDP ソースポートから問い合わせをできるように設定します。
+ </div></div></div></dd></dl></div></div><div class="section" id="s2-bind-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.7. その他のリソース</h3></div></div></div><div class="para">
+ 以下の情報源は、 BIND に関する追加情報を提供します。
+ </div><div class="section" id="s3-bind-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.7.1. インストールされているドキュメント</h4></div></div></div><a id="idm131873232" class="indexterm"></a><div class="para">
+ BIND features a full range of installed documentation covering many different topics, each placed in its own subject directory. For each item below, replace <em class="replaceable"><code>version</code></em> with the version of the <span class="package">bind</span> package installed on the system:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/</code></span></dt><dd><div class="para">
+ メインディレクトリに最新のドキュメントがあります。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/arm/</code></span></dt><dd><div class="para">
+ The directory containing the <em class="citetitle">BIND 9 Administrator Reference Manual</em> in HTML and SGML formats, which details BIND resource requirements, how to configure different types of nameservers, how to perform load balancing, and other advanced topics. For most new users of BIND, this is the best place to start.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/draft/</code></span></dt><dd><div class="para">
+ The directory containing assorted technical documents that review issues related to the DNS service, and propose some methods to address them.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/misc/</code></span></dt><dd><div class="para">
+ The directory designed to address specific advanced issues. Users of BIND version 8 should consult the <code class="filename">migration</code> document for specific changes they must make when moving to BIND 9. The <code class="filename">options</code> file lists all of the options implemented in BIND 9 that are used in <code class="filename">/etc/named.conf</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/rfc/</code></span></dt><dd><div class="para">
+ BIND に関連するすべての RFC ドキュメントを提供しているディレクトリーです。
+ </div></dd></dl></div><div class="para">
+ There is also a number of man pages for the various applications and configuration files involved with BIND:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">man rndc</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">rndc</code> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man named</code></span></dt><dd><div class="para">
+ The manual page for <code class="systemitem">named</code> containing the documentation on assorted arguments that can be used to control the BIND nameserver daemon.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man lwresd</code></span></dt><dd><div class="para">
+ The manual page for <code class="systemitem">lwresd</code> containing the full documentation on the lightweight resolver daemon and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man named.conf</code></span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="systemitem">named</code> configuration file.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man rndc.conf</code></span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="command">rndc</code> configuration file.
+ </div></dd></dl></div></div><div class="section" id="s3-bind-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.7.2. 役に立つ Web サイト</h4></div></div></div><a id="idm93227984" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.isc.org/software/bind">http://www.isc.org/software/bind</a></span></dt><dd><div class="para">
+ <em class="citetitle">BIND 9 Administrator Reference Manual</em> の PDF バージョンなど現在のリリースに関する情報が含まれている、BIND プロジェクトのホームページです。
+ </div></dd></dl></div></div><div class="section" id="s3-bind-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.7.3. 関連書籍</h4></div></div></div><a id="idm77727184" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="citetitle">DNS and BIND</em>、Paul Albitz and Cricket Liu; O'Reilly & Associates</span></dt><dd><div class="para">
+ 一般的な設定オプションと難解なもの両方を説明している人気のあるリファレンスです。また、DNS サーバーをセキュア化するための手法を提供しています。
+ </div></dd><dt class="varlistentry"><span class="term"><em class="citetitle">The Concise Guide to DNS and BIND</em>、Nicolai Langfeldt; Que</span></dt><dd><div class="para">
+ Looks at the connection between multiple network services and BIND, with an emphasis on task-oriented, technical topics.
+ </div></dd></dl></div></div></div></div></div><div xml:lang="ja-JP" class="chapter" id="ch-Web_Servers" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第13章 ウェブ サーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-The_Apache_HTTP_Server">13.1. Apache HTTP サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-version2-features">13.1.1. 新機能</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-changes">13.1.2. 注目すべき変更</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">13.1.3. 設定の更新</a></span></dt><dt><span class="section"><a href="#s2-apache-running">13.1.4. httpd サービスの実行方法</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">13.1.5. 設定ファイルの編集</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">13.1.6. Working with Modules</a></span></d
t><dt><span class="section"><a href="#s2-apache-virtualhosts">13.1.7. 仮想ホストのセットアップ</a></span></dt><dt><span class="section"><a href="#s2-apache-mod_ssl">13.1.8. SSL サーバーのセットアップ</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">13.1.9. その他のリソース</a></span></dt></dl></dd></dl></div><a id="idm81293376" class="indexterm"></a><a id="idm107682608" class="indexterm"></a><div class="para">
+ <code class="systemitem">HTTP</code> (ハイパーテキスト転送プロトコル)サーバー、あるいは<em class="firstterm">ウェブサーバー</em>は、ウェブ経由でクライアントにコンテンツを提供するネットワークサービスです。これは通常ウェブページを意味しますが、他の文書も同様に提供することができます。
+ </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">13.1. Apache HTTP サーバー</h2></div></div></div><a id="idm89464368" class="indexterm"></a><div class="para">
+ This section 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 <a href="http://www.apache.org/">Apache Software Foundation</a>, that is included in Fedora 17. It describes the basic configuration of the <code class="systemitem">httpd</code> service, and covers advanced topics such as adding server modules, setting up virtual hosts, or configuring the secure HTTP server.
+ </div><div class="para">
+ Apache HTTP Server 2.2 とバージョン 2.0 の間には大きな変更点があります。以前のリリースの Fedora からアップグレードしているならば、必要に応じて <code class="systemitem">httpd</code> サービス設定を更新する必要があります。このセクションは、いくつかの新しく追加された機能、重要な変更点の概要、および古い設定ファイルの更新について詳しく説明しているガイドを概観します。
+ </div><div class="section" id="s2-apache-version2-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.1. 新機能</h3></div></div></div><a id="idm81294848" class="indexterm"></a><div class="para">
+ Apache HTTP Server バージョン 2.2 は以下の機能拡張をしています:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="idm94726080" class="indexterm"></a>
+ <a id="idm94728384" class="indexterm"></a>
+ つまり、改良されたキャッシュモジュール <code class="systemitem">mod_cache</code> および <code class="systemitem">mod_disk_cache</code>。
+ </div></li><li class="listitem"><div class="para">
+ <a id="idm84402576" class="indexterm"></a>
+ つまり、プロキシ負荷分散のサポート <code class="systemitem">mod_proxy_balancer</code> モジュール。
+ </div></li><li class="listitem"><div class="para">
+ 32ビットアーキテクチャーにおける大容量ファイルのサポート、ウェブサーバーが2GBより大きなファイルを取り扱えます。
+ </div></li><li class="listitem"><div class="para">
+ 認証モジュールを置き換える、認証と認可のサポートの新しい構成は、前のバージョンで提供されました。
+ </div></li></ul></div></div><div class="section" id="s2-apache-version2-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.2. 注目すべき変更</h3></div></div></div><a id="idm95160960" class="indexterm"></a><div class="para">
+ 2.0 以降、デフォルトの <code class="systemitem">httpd</code> サービス設定にいくつかの変更がありました:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="idm139730736" class="indexterm"></a>
+ <a id="idm139732672" class="indexterm"></a>
+ 以下のモジュールはもはやデフォルトで読み込まれません: <code class="systemitem">mod_cern_meta</code> および <code class="systemitem">mod_asis</code>。
+ </div></li><li class="listitem"><div class="para">
+ <a id="idm134499712" class="indexterm"></a>
+ 以下のモジュールは新しくデフォルトで読み込まれます: <code class="systemitem">mod_ext_filter</code>。
+ </div></li></ul></div></div><div class="section" id="s2-apache-version2-migrating"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.3. 設定の更新</h3></div></div></div><a id="idm125754432" class="indexterm"></a><div class="para">
+ Apache HTTP Server バージョン 2.0 から設定ファイルを更新するには、以下の手順に従ってください:
+ </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="idm120977408" 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">service httpd configtest</code></pre><div class="para">
+ Apache HTTP Server のバージョン 2.0 から 2.2 に設定を更新することに関する詳細は <a href="http://httpd.apache.org/docs/2.2/upgrading.html">http://httpd.apache.org/docs/2.2/upgrading.html</a> を参照してください。
+ </div></div><div class="section" id="s2-apache-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.4. 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 as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install httpd</code></pre><div class="para">
+ For more information on the concept of runlevels and how to manage system services in Fedora in general, refer to <a class="xref" href="#ch-Services_and_Daemons">8章<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">13.1.4.1. サービスの開始</h4></div></div></div><a id="idm130664688" 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">
+ ブート時にサービスを自動的に開始したければ、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl enable httpd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div><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">13.1.4.2. さービスの停止</h4></div></div></div><a id="idm115969776" 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">
+ 起動時にサービスが自動的に開始しないようにするには、次のように入力します:
+ </div><pre class="screen"><code class="command">systemctl disable httpd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s3-apache-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.4.3. サービスの再開</h4></div></div></div><a id="idm133812624" class="indexterm"></a><div class="para">
+ 実行中の <code class="systemitem">httpd</code> サービスを再起動するには、二つの異なる方法があります:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ サービスを完全に再起動するには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のとおり入力します:
+ </div><pre class="screen"><code class="command">systemctl restart httpd.service</code></pre><div class="para">
+ これは実行中の <code class="systemitem">httpd</code> サービスを停止して、その後再び開始します。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 will cause the running <code class="systemitem">httpd</code> service to reload the configuration file. Note that any requests being currently 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">
+ 処理中の内容に影響を与えることなく設定を再読み込みするには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="screen"><code class="command">service httpd graceful</code></pre><div class="para">
+ This will cause the running <code class="systemitem">httpd</code> service to reload the configuration file. Note that any requests being currently processed will use the old configuration.
+ </div></li></ol></div><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s3-apache-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.4.4. サービスの状態確認</h4></div></div></div><a id="idm71410192" class="indexterm"></a><div class="para">
+ サービスが実行中であるかどうかを確認するには、シェルプロンプトにおいて次のとおり入力します:
+ </div><pre class="screen"><code class="command">systemctl is-active httpd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div></div><div class="section" id="s2-apache-editing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.5. 設定ファイルの編集</h3></div></div></div><div class="para">
+ <code class="systemitem">httpd</code> サービスが開始するとき、<a class="xref" href="#table-apache-editing-files">表13.1「httpd サービス設定ファイル」</a>に一覧化されている位置から設定が読み込まれます。
+ </div><div class="table" id="table-apache-editing-files"><h6>表13.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="idm21346480" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf/httpd.conf</code>
+ </td><td class="">
+ 中心となる設定ファイルです。
+ </td></tr><tr><td class="">
+ <a id="idm20496112" 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. Refer to <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="idm121691712" class="indexterm"></a><div class="para">
+ 起こりえるエラーに対して設定を確認するには、シェルプロンプトにおいて次のとおり入力します:
+ </div><pre class="screen"><code class="command">service httpd configtest</code></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">13.1.5.1. 一般的な httpd.conf ディレクティブ</h4></div></div></div><a id="idm122599184" 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="idm120300416" 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>例13.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="idm108467248" 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>例13.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="idm101480864" 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>例13.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="idm124064208" 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>例13.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="idm121229296" 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>例13.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="idm137349792" 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">表13.2「利用可能な <VirtualHost> オプション」</a>に記載されている特別な形式を使用できます。
+ </div><div class="table" id="table-apache-httpdconf-virtualhost"><h6>表13.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>例13.6 <VirtualHost> ディレクティブの使用法</h6><div class="example-contents"><pre class="programlisting"><VirtualHost *:80>
+ ServerAdmin webmaster at 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="idm124104688" 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="idm108777296" class="indexterm"></a><a id="idm108779568" class="indexterm"></a><div class="para">
+ <em class="replaceable"><code>filename</code></em> は要求されたディレクトリにおいて探すファイルの名前です。デフォルトで、サーバーは <code class="filename">.htaccess</code> を探します。
+ </div><a id="idm89747280" class="indexterm"></a><a id="idm89750064" 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>例13.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="idm107618144" 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>例13.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="idm127903312" 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>例13.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="idm100288288" 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>例13.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="idm138197744" 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>例13.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="idm101487328" 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>表13.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>例13.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="idm91187168" 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>例13.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="idm71947120" 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>例13.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="idm91161232" 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>例13.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="idm57896800" 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>例13.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="idm120000576" 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="idm71510816" 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>例13.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="idm106930640" 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>例13.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="idm89654160" class="indexterm"></a>
+ <code class="option">AllowOverride</code></span></dt><dd><a id="idm89656944" class="indexterm"></a><a id="idm126913120" 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">表13.4「利用可能な AllowOverride オプション」</a>.
+ </div><div class="table" id="table-apache-httpdconf-allowoverride"><h6>表13.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>例13.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="idm59442128" 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>例13.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="idm125420112" 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>例13.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="idm215047696" 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>例13.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="idm120672272" 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">表13.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>表13.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>例13.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="idm128036672" 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>例13.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="idm109368448" 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>例13.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="idm15452608" 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">表13.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>表13.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>例13.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="idm53100288" 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="idm116348160" 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>例13.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="idm86902576" 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="idm109257296" 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>例13.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="idm109262464" 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>例13.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="idm108454992" 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>例13.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="idm119697280" 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>例13.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="idm134409568" 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>例13.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="idm84796896" 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="idm84801200" 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>例13.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="idm137464688" 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>例13.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="idm70866960" 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="idm107455824" 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>例13.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="idm17938432" 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">表13.7「利用可能な ExtendedStatus オプション」</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" id="table-apache-httpdconf-extendedstatus"><h6>表13.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>例13.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="idm101878208" 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>例13.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="idm139498400" 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>例13.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="idm131817248" 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">表13.8「利用可能な HostnameLookups オプション」</a>において説明されている有効なキーワードである必要があります。サーバーにおいてリソースを保護するために、オプションの初期値は <code class="option">Off</code> です。
+ </div><div class="table" id="table-apache-httpdconf-hostnamelookup"><h6>表13.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>例13.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="idm116823408" 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="idm138035696" 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>例13.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="idm110516992" 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>例13.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="idm18654848" 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">表13.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>表13.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>例13.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="idm105795056" 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">表13.10「利用可能な KeepAlive オプション」</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" id="table-apache-httpdconf-keepalive"><h6>表13.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>例13.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="idm85731200" 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>例13.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="idm81921856" 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>例13.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="idm112277696" 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>例13.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="idm94424336" 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="idm98414592" class="indexterm"></a><a id="idm98416832" 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">
+ Apache HTTP Server の DSO サポートの詳細は<a class="xref" href="#s2-apache-dso">「Working with Modules」</a>を参照してください。
+ </div><div class="example" id="example-apache-httpdconf-loadmodule"><h6>例13.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="idm67861360" 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">表13.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>表13.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>例13.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="idm121479264" 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">表13.12「利用可能な LogLevel オプション」</a>. The default option is <code class="option">warn</code>.
+ </div><div class="table" id="table-apache-httpdconf-loglevel"><h6>表13.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>例13.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="idm113984944" 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>例13.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="idm130197280" 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>例13.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="idm135253104" 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">表13.13「利用できるサーバーの機能」</a>に説明されている有効なキーワードでなければいけません。
+ </div><div class="table" id="table-apache-httpdconf-options"><h6>表13.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>例13.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="idm112584160" 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">表13.14「利用可能な Order オプション」</a>. The default option is <code class="option">allow,deny</code>.
+ </div><div class="table" id="table-apache-httpdconf-order"><h6>表13.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>例13.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="idm122637504" 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="idm137517280" 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>例13.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="idm83923984" 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">表13.15「利用可能な ProxyRequests オプション」</a> に説明されている有効なキーワードである必要があります。初期オプションは <code class="option">Off</code> です。
+ </div><div class="table" id="table-apache-httpdconf-proxyrequests"><h6>表13.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>例13.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="idm86719920" 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>例13.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="idm86720080" 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">表13.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>表13.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="idm89252960" 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>例13.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="idm106564544" 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="idm87998048" 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>例13.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="idm101633728" 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 at 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>例13.59 ServerAdmin ディレクティブの使用法</h6><div class="example-contents"><pre class="programlisting">ServerAdmin webmaster at penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm98760064" 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>例13.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="idm147824448" 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="idm99940656" 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>例13.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="idm120677456" 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">表13.17「利用可能な ServerSignature オプション」</a>において説明されている有効なキーワードである必要があります。オプションの初期値は <code class="option">On</code> です。
+ </div><div class="table" id="table-apache-httpdconf-serversignature"><h6>表13.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>例13.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="idm116622496" 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">表13.18「利用可能な ServerTokens オプション」</a>. The default option is <code class="option">OS</code>.
+ </div><div class="table" id="table-apache-httpdconf-servertokens"><h6>表13.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>例13.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="idm86816128" 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>例13.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="idm117028576" 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>例13.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="idm96580464" 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="idm131178128" 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>例13.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="idm91621088" 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">表13.19「利用可能な UseCanonicalName オプション」</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" id="table-apache-httpdconf-usecanonicalname"><h6>表13.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>例13.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="idm133597808" 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>例13.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="idm81525216" 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="idm94831488" 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">表13.20「利用可能な UserDir オプション」</a>. The default option is <code class="option">disabled</code>.
+ </div><div class="table" id="table-apache-httpdconf-userdir"><h6>表13.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>例13.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">13.1.5.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="idm90296832" 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="idm90298960" 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">表13.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>表13.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>例13.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">
+ <code class="filename">/etc/httpd/conf.d/ssl.conf</code> ファイルが存在するには、<span class="package">mod_ssl</span> がインストールされている必要があることに注意してください。SSL サーバーのインストールと設定に関する詳細は<a class="xref" href="#s2-apache-mod_ssl">「SSL サーバーのセットアップ」</a>を参照してください。
+ </div></div><div class="section" id="s3-apache-mpm-common"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.5.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="idm106244992" 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="idm70553408" 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>例13.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="idm120291520" 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>例13.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="idm135794688" 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>例13.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="idm97623792" 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>例13.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="idm125438512" 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>例13.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="idm70646752" 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>例13.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="idm69210064" 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>例13.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="idm134308336" 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>例13.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">13.1.6. Working with Modules</h3></div></div></div><a id="idm95907952" class="indexterm"></a><a id="idm95910736" 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">13.1.6.1. モジュールの読み込み方法</h4></div></div></div><a id="idm90349296" 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>例13.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. Refer to <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">13.1.6.2. モジュールの書き込み方法</h4></div></div></div><a id="idm102467648" 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, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum 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">13.1.7. 仮想ホストのセットアップ</h3></div></div></div><a id="idm69213792" class="indexterm"></a><a id="idm135624416" 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, hostname, or port is being requested.
+ </div><div class="para">
+ To create a name-based virtual host, find the virtual host container provided in <code class="filename">/etc/httpd/conf/httpd.conf</code> as an example, remove the hash sign (that is, <code class="literal">#</code>) from the beginning of each line, and customize the options according to your requirements as shown in <a class="xref" href="#example-apache-virtualhosts-config">例13.80「仮想ホストのサンプル設定」</a>.
+ </div><div class="example" id="example-apache-virtualhosts-config"><h6>例13.80 仮想ホストのサンプル設定</h6><div class="example-contents"><pre class="programlisting">NameVirtualHost penguin.example.com:80
+
+<VirtualHost penguin.example.com:80>
+ ServerAdmin webmaster at penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName penguin.example.com:80
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.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. Refer to <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">13.1.8. SSL サーバーのセットアップ</h3></div></div></div><a id="idm215094256" class="indexterm"></a><a id="idm215097104" class="indexterm"></a><a id="idm105816944" class="indexterm"></a><a id="idm95122160" class="indexterm"></a><a id="idm105820656" class="indexterm"></a><a id="idm95118816" 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">13.1.8.1. 証明書とセキュリティの概要</h4></div></div></div><a id="idm61908736" class="indexterm"></a><a id="idm94574416" 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="idm131427504" class="indexterm"></a><a id="idm131429744" 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 hostname, 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 issued 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 hostname listed in the certificate does not match the hostname 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">表13.22「CA lists for most common web browsers」</a>.
+ </div><div class="table" id="table-apache-mod_ssl-certificates-authorities"><h6>表13.22 CA lists for most common web browsers</h6><div class="table-contents"><table summary="CA lists for most 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/">Mozilla root CA list</a>。
+ </td></tr><tr><td class="">
+ <span class="application"><strong>Opera</strong></span>
+ </td><td class="">
+ <a href="http://my.opera.com/rootstore/blog/">The Opera Rootstore</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">Windows root certificate program members</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">13.1.8.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, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install mod_ssl openssl</code></pre><a id="idm130645888" 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">13.1.8.3. Using an Existing Key and Certificate</h4></div></div></div><a id="idm101452128" class="indexterm"></a><a id="idm127623392" 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">
+ 上のケースのどちらかにおいて、新しい証明書を取得する必要があります。このトピックの詳細は、<a class="xref" href="#s3-apache-mod_ssl-genkey">「新規キーおよび証明書の生成」</a>を参照してください。
+ </div><div class="para">
+ If you wish 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 running 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>例13.81 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">13.1.8.4. 新規キーおよび証明書の生成</h4></div></div></div><a id="idm137494032" class="indexterm"></a><a id="idm137496800" class="indexterm"></a><div class="para">
+ In order to generate a new key and certificate pair, you must to have the <span class="package">crypto-utils</span> package installed in your system. As <code class="systemitem">root</code>, you can install it by typing the following at a shell prompt:
+ </div><pre class="screen"><code class="command">yum 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, as <code class="systemitem">root</code>, 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 hostname 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">
+ ユーティリティを実行するには、<code class="systemitem">root</code> として、適切なホスト名をつけて (たとえば、<code class="systemitem">penguin.example.com</code>) <code class="command">genkey</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>図13.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">
+ <span class="keycap"><strong>上</strong></span> と <span class="keycap"><strong>下</strong></span> の矢印キーを使用して、適切なキーの大きさを選択します。大きなキーはセキュリティを向上させる一方、サーバーの応答時間も増加させることに注意してください。このため、推奨されるオプションは <code class="literal">1024 ビット</code> です。
+ </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>図13.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">
+ 証明書要求を証明書認証局に送信したいかどうかを決定します。
+ </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>図13.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>図13.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>図13.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>図13.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>図13.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">13.1.9. その他のリソース</h3></div></div></div><div class="para">
+ Apache HTTP Server に関してさらに詳細をお知りになりたい場合は、以下のリソースを参照してください。
+ </div><div class="section" id="s3-apache-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.9.1. インストールされているドキュメント</h4></div></div></div><a id="idm124244128" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://localhost/manual/">http://localhost/manual/</a></span></dt><dd><div class="para">
+ 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></dd><dt class="varlistentry"><span class="term"><code class="command">man httpd</code></span></dt><dd><div class="para">
+ <code class="systemitem">httpd</code> サービスのコマンドラインオプションの完全な一覧を含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man genkey</code></span></dt><dd><div class="para">
+ <code class="command">genkey</code> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd></dl></div></div><div class="section" id="s3-apache-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.9.2. 役に立つ Web サイト</h4></div></div></div><a id="idm115340416" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://httpd.apache.org/">http://httpd.apache.org/</a></span></dt><dd><div class="para">
+ The official website for the Apache HTTP Server with documentation on all the directives and default modules.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.modssl.org/">http://www.modssl.org/</a></span></dt><dd><div class="para">
+ <span class="application"><strong>mod_ssl</strong></span> モジュールの公式ウェブサイトです。
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.openssl.org/">http://www.openssl.org/</a></span></dt><dd><div class="para">
+ さらなるドキュメント、よくある質問、メーリングリストへのリンク、および他の有用なリソースがある OpenSSL のホームページです。
+ </div></dd></dl></div></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">第14章 メールサーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-email-protocols">14.1. 電子メールプロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protocols-send">14.1.1. メール トランスポートのプロトコル</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">14.1.2. メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">14.2. 電子メールプログラム分類</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">14.2.1. メール転送エージェント (Mail Transport Agent)</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">14.2.2. メール配送エージェント (
Mail Delivery Agent)</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">14.2.3. メール ユーザー エージェント</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mta">14.3. Mail Transport Agent</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-postfix">14.3.1. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-sendmail">14.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">14.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="#s2-email-switchmail">14.3.4. Mail Transport Agent (MTA) の設定</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mda">14.4. メール配送エージェント</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">14.4.1. Procmail の設定</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">14.4.2. Procmail レシピ</a></spa
n></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">14.5. メールユーザーエージェント</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">14.5.1. 通信のセキュリティ</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">14.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">14.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">14.6.2. 役に立つ Web サイト</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">14.6.3. 関連書籍</a></span></dt></dl></dd></dl></div><a id="idm99977968" class="indexterm"></a><div class="para">
+ <em class="firstterm">電子メール</em>は1960年代に生まれました。メールボックスは、そのユーザーのみが読み込めるユーザーのホームディレクトリにあるファイルでした。初期の電子メールアプリケーションは新しいテキストメッセージをファイルの末尾に追加しました。ユーザーはある特定のメッセージを検索するために常に大きくなるファイルを読み通します。このシステムは同じシステムにいるユーザーにメッセージを送信できるだけでした。
+ </div><div class="para">
+ 電子メールのメッセージファイルのネットワーク転送は1971年に初めて行われました。Ray Tomlinson というコンピューター技術者が、インターネットの前進である ARPANET 経由で2台のマシン間でテストメッセージを送信しました。電子メールによるコミュニケーションは、すぐに大人気になり、2年しないうちに ARPANET のトラフィックの75%を占めるようになりました。
+ </div><div class="para">
+ 今日、標準化されたネットワークプロトコルに基づいた電子メールシステムは、インターネットにおいて最も広く利用されるサービスのいくつかに進歩してきました。Fedora は電子メールを処理およびアクセスする多くの高度なアプリケーションを提供します。
+ </div><div class="para">
+ 本章は今日使用されている最近の電子メールプロトコル、および電子メールを送信および受信するよう設定されたプログラムのいくつかを概説します。
+ </div><div class="section" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">14.1. 電子メールプロトコル</h2></div></div></div><a id="idm106854304" 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">14.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">14.1.1.1. SMTP</h4></div></div></div><a id="idm100216224" 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">14.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">14.1.2.1. POP</h4></div></div></div><a id="idm96575520" 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">
+ <span class="application"><strong>Dovecot</strong></span> を使用するには、まず <code class="systemitem">root</code> として次のコマンドを実行することにより、マシンに <code class="command">dovecot</code> パッケージを確実にインストールします:
+ </div><pre class="screen"><code class="command">yum install dovecot</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</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">MDS</code> (Monash Directory Service) authentication. An encoded hash of the user's password is sent from the email client to the server rather then 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">/usr/sbin/stunnel</code> application. For more information on securing email communication, refer to <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">14.1.2.2. IMAP</h4></div></div></div><a id="idm101379344" class="indexterm"></a><div class="para">
+ Fedora における標準の <code class="systemitem">IMAP</code> サーバーは <span class="application"><strong>Dovecot</strong></span> です。<span class="package">dovecot</span> パッケージにより提供されます。<span class="application"><strong>Dovecot</strong></span> をインストールする方法の詳細は<a class="xref" href="#s3-email-protocols-pop">「POP」</a>を参照してください。
+ </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">/usr/sbin/stunnel</code> program. For more information on securing email communication, refer to <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">14.1.2.3. Dovecot</h4></div></div></div><a id="idm132690432" 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="command">#</code>) at the beginning of the line) and contains the <code class="literal">pop3</code> argument. For example:
+ </div><pre class="programlisting">protocols = imap imaps pop3 pop3s</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 specified for this variable.
+ </div></li><li class="listitem"><div class="para">
+ Make that 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.service</code></pre></li><li class="listitem"><div class="para">
+ コマンドを起動させることによって、次回のリブート後に変更を操作可能にします。
+ </div><pre class="screen"><code class="command">systemctl enable dovecot.service</code></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 username 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.conf</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 typing the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl restart dovecot.service</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">14.2. 電子メールプログラム分類</h2></div></div></div><a id="idm93524544" 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">14.2.1. メール転送エージェント (Mail Transport Agent)</h3></div></div></div><a id="idm131875728" class="indexterm"></a><a id="idm114468800" class="indexterm"></a><a id="idm114467200" 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, refer to <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">14.2.2. メール配送エージェント (Mail Delivery Agent)</h3></div></div></div><a id="idm106120208" class="indexterm"></a><a id="idm123636560" class="indexterm"></a><a id="idm94903584" 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">14.2.3. メール ユーザー エージェント</h3></div></div></div><a id="idm115665248" class="indexterm"></a><a id="idm84354208" class="indexterm"></a><a id="idm84352608" 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 the very least, 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>pine</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">14.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, although it is easy to switch the default MTA to Sendmail. To switch the default MTA to Sendmail, as <code class="systemitem">root</code>, you can either uninstall Postfix or use the following command 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/disable the desired service:
+ </div><pre class="screen"><code class="command">systemctl enable|disable <em class="replaceable"><code>service</code></em>.service</code></pre><div class="section" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">14.3.1. Postfix</h3></div></div></div><a id="idm122388384" class="indexterm"></a><a id="idm18629008" class="indexterm"></a><div class="para">
+ 元来、 IBM のセキュリティ専門家でありプログラマーの Wietse Venema によって開発された Postfix は、安全で迅速で設定が容易であるようにデザインされた Sendmail 対応の MTA です。
+ </div><div class="para">
+ セキュリティを改善する為に、 Postfix はモジュラーデザインを使用して、 <em class="firstterm">master</em> デーモンによって制限付の権限を持つ小規模のプロセスが起動できるようにします。より小規模で、権限の低いプロセスは、メール配送の各種段階における特定のタスクを実行し、外部攻撃からの影響を低減する為に変更したルート環境で動作します。
+ </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">14.3.1.1. Postfix のデフォルトインストール</h4></div></div></div><a id="idm86094416" class="indexterm"></a><div class="para">
+ The Postfix executable is <code class="filename">/usr/sbin/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, refer to <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.service</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">14.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="command">#</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 hostname 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">14.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">14.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> 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 created 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">
+ <code class="filename">/etc/postfix/ldap-aliases.cf</code> ファイルは、<code class="systemitem">LDAP</code> <code class="systemitem">SSL</code> および <code class="systemitem">STARTTLS</code> を有効化するパラメーターを含め、さまざまなパラメーターを指定できます。詳細は<code class="command">ldap_table(5)</code>マニュアルページを参照してください。
+ </div></div></div><div class="para">
+ <code class="systemitem">LDAP</code> の詳細は<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">14.3.2. Sendmail</h3></div></div></div><a id="idm121686064" class="indexterm"></a><a id="idm18595200" 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. However, Sendmail is highly configurable, allowing control over almost every aspect of how email is handled, including the protocol used. Many system administrators elect to use Sendmail as their MTA due to its power and scalability.
+ </div><div class="section" id="s3-email-mta-sendmail-purpose"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">14.3.2.1. 目的と制限</h4></div></div></div><a id="idm110642912" class="indexterm"></a><a id="idm94584480" 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. Refer to 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">14.3.2.2. Sendmail のデフォルトインストール</h4></div></div></div><a id="idm102972448" 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">yum 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">yum install sendmail-cf</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</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">
+ Sendmail の実行ファイルは <code class="filename">/usr/sbin/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>, 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> (<code class="command">~]# make all -C /etc/mail/</code>) to create a new <code class="filename">/etc/mail/sendmail.cf</code> configuration file. 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 will automatically be used by <code class="command">systemctl start|restart|reload sendmail.service</code>.
+ </div></li><li class="listitem"><div class="para">
+ Alternatively you may use the <code class="command">m4</code> macro processor to create a new <code class="filename">/etc/mail/sendmail.cf</code>. The <code class="command">m4</code> macro processor is not installed by default. Before using it to create <code class="filename">/etc/mail/sendmail.cf</code>, install the <span class="package">m4</span> package as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install m4</code></pre></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">
+ さまざまな Sendmail 設定ファイルが <code class="filename">/etc/mail/</code> ディレクトリにインストールされます:
+ </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 <code class="filename">/etc/mail/</code>, 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 command, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">makemap hash /etc/mail/<em class="replaceable"><code>name</code></em> < /etc/mail/<em class="replaceable"><code>name</code></em></code></pre><div class="para">
+ where <em class="replaceable"><code>name</code></em> represents the name of the configuration file to be updated. 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.service</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="email"><a class="email" href="mailto:bob at other-example.com">bob at other-example.com</a></code>
+ , add the following line to the <code class="filename">virtusertable</code> file:
+ </div><pre class="programlisting"><code class="command">@example.com bob at other-example.com</code></pre><div class="para">
+ 変更を完了するには、<code class="filename">virtusertable.db</code> ファイルを更新しなければいけません:
+ </div><pre class="screen"><code class="command">makemap hash /etc/mail/virtusertable < /etc/mail/virtusertable</code></pre><div class="para">
+ Sendmail will create an updated <code class="filename">virtusertable.db</code> file containing the new configuration.
+ </div></div><div class="section" id="s3-email-mta-sendmail-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">14.3.2.3. 一般的な Sendmail 設定変更</h4></div></div></div><a id="idm117570368" class="indexterm"></a><a id="idm88117280" 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">
+ <code class="filename">sendmail.cf</code> ファイルを変更する前に、バックアップのコピーを作成することは良いアイディアです。
+ </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.service</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.service</code></pre></div></div><div class="para">
+ The default configuration which ships with 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">14.3.2.4. マスカレード</h4></div></div></div><a id="idm123458224" class="indexterm"></a><a id="idm58793360" 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 instance, 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 at example.com</code> instead of <code class="computeroutput">user at 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(`bigcorp.com.')dnl
+MASQUERADE_DOMAIN(`bigcorp.com.')dnl
+MASQUERADE_AS(bigcorp.com)dnl</pre><div class="para">
+ After generating a new <code class="filename">sendmail.cf</code> 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="computeroutput">bigcorp.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">14.3.2.5. スパムの停止</h4></div></div></div><a id="idm111634224" 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.service</code></pre><div class="para">
+ However, many times users are bombarded with spam from other servers throughout 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" 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 to the spammer. 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. Refer to the <code class="filename">/usr/share/sendmail-cf/README</code> 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. Refer to <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">14.3.2.6. LDAP での Sendmail の使用</h4></div></div></div><a id="idm103796464" 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. Refer to <a class="xref" href="#s3-email-mta-sendmail-changes">「一般的な Sendmail 設定変更」</a> for instructions.
+ </div><div class="para">
+ <code class="systemitem">LDAP</code> の詳細は<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">14.3.3. Fetchmail</h3></div></div></div><a id="idp1279344" class="indexterm"></a><a id="idm117524544" 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">yum install fetchmail</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</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">14.3.3.1. Fetchmail 設定オプション</h4></div></div></div><a id="idm126535312" class="indexterm"></a><a id="idm99790592" 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 hostname, 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 username 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 hostname 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">
+ 以下は <code class="filename">.fetchmailrc</code> ファイルのサンプル例です。:
+ </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">14.3.3.2. グローバルオプション</h4></div></div></div><a id="idm126145248" class="indexterm"></a><a id="idm127802480" 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">14.3.3.3. サーバー オプション</h4></div></div></div><a id="idm104376512" class="indexterm"></a><a id="idm93220304" 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 assumed.
+ </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">14.3.3.4. ユーザー オプション</h4></div></div></div><a id="idm134086880" class="indexterm"></a><a id="idm124031888" 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">14.3.3.5. Fetchmail コマンド オプション</h4></div></div></div><a id="idm133352496" 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">14.3.3.6. 情報オプション、あるいはデバッグ オプション</h4></div></div></div><a id="idm20421008" 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">14.3.3.7. 特別なオプション</h4></div></div></div><a id="idm122534640" 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">14.3.4. Mail Transport Agent (MTA) の設定</h3></div></div></div><a id="idm120039696" class="indexterm"></a><a id="idm120038096" class="indexterm"></a><a id="idm80210000" class="indexterm"></a><a id="idm87847376" class="indexterm"></a><a id="idm87845664" class="indexterm"></a><a id="idm122789072" 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">/bin/mail</code> command to send email containing log messages to the <code class="systemitem">root</code> user of the local system.
+ </div><a id="idm117327440" class="indexterm"></a><a id="idm117326176" class="indexterm"></a><div class="para">
+ Fedora 17 は2つの MTA を提供します: Postfix および Sendmail。どちらもインストールされていれば、Postfix がデフォルトの MTA です。
+ </div></div></div><div class="section" id="s1-email-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">14.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="idm48501920" class="indexterm"></a><a id="idm109662896" 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">14.4.1. Procmail の設定</h3></div></div></div><a id="idm83396752" class="indexterm"></a><a id="idm130467520" 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">
+ たとえば、ユーザーの <code class="filename">.procmailrc</code> ファイルにある行は次のように見えるでしょう:
+ </div><pre class="programlisting">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="command">#</code>).
+ </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>, which is the login name; <code class="command">HOME</code>, which is the location of the home directory; and <code class="command">SHELL</code>, which is the default shell.
+ </div><div class="para">
+ A comprehensive explanation of all environments variables, as well as 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">14.4.2. Procmail レシピ</h3></div></div></div><a id="idm106207712" class="indexterm"></a><div class="para">
+ New users often find the construction of recipes the most difficult part of learning to use Procmail. To some extent, this is understandable, as recipes do their message matching using <em class="firstterm">regular expressions</em>, which is a particular format used to specify qualifications for a matching string. 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, refer to <a class="xref" href="#s3-email-procmail-recipes-examples">「レシピの例」</a>.
+ </div><div class="para">
+ Procmail レシピは、次の形式をとります:
+ </div><pre class="programlisting">:0<em class="replaceable"><code>flags</code></em>: <em class="replaceable"><code>lockfile-name</code></em> * <em class="replaceable"><code>special-condition-character</code></em>
+ <em class="replaceable"><code>condition-1</code></em> * <em class="replaceable"><code>special-condition-character</code></em>
+ <em class="replaceable"><code>condition-2</code></em> * <em class="replaceable"><code>special-condition-character</code></em>
+ <em class="replaceable"><code>condition-N</code></em>
+ <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. Refer to <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">14.4.2.1. 配信レシピと非配信</h4></div></div></div><a id="idm125687440" class="indexterm"></a><a id="idm112896816" 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">14.4.2.2. フラグ</h4></div></div></div><a id="idm125765760" class="indexterm"></a><div class="para">
+ フラグは、いかにレシピの条件をメッセージと比較するか、あるいはレシピの条件をメッセージと比較するかどうかを決定する際に非常に重要です。次のフラグが一般に使用されます:
+ </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 the 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">
+ 追加のフラグの詳細な一覧は <code class="filename">procmailrc</code> マニュアルページを参照してください。
+ </div></div><div class="section" id="s3-email-procmail-recipes-lockfile"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">14.4.2.3. ローカルロックファイルの指定</h4></div></div></div><a id="idm127797648" 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">14.4.2.4. 特別な条件とアクション</h4></div></div></div><a id="idm94817664" class="indexterm"></a><a id="idm125490192" 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">14.4.2.5. レシピの例</h4></div></div></div><a id="idp1677936" 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 (such as <a href="http://www.iki.fi/era/procmail/links.html">http://www.iki.fi/era/procmail/links.html</a>). 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</code> man page.
+ </div><div class="para">
+ 次の簡単なサンプルが Procmail レシピの基本的な組み立てを示し、そしてより複雑な構成の基盤を提供します。
+ </div><div class="para">
+ 基本的なレシピには、次の例で示すように条件が付いていないものさえあります：
+ </div><pre class="programlisting">: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="programlisting">:0 * ^From: spammer at domain.com /dev/null</pre><div class="para">
+ With this example, any messages sent by <code class="computeroutput">spammer at 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="programlisting">:0: * ^(From|Cc|To).*tux-lug tuxlug</pre><div class="para">
+ Any messages sent from the <code class="computeroutput">tux-lug at 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">14.4.2.6. スパムフィルタ</h4></div></div></div><a id="idm107344752" class="indexterm"></a><a id="idm121453120" class="indexterm"></a><a id="idm121451376" 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">yum install spamassassin</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</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">
+ Fedora においてサービスを設定する方法の詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </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">14.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">14.5.1. 通信のセキュリティ</h3></div></div></div><div class="para">
+ Popular MUAs included with Fedora, such as <span class="application"><strong>Evolution</strong></span> and <code class="command">mutt</code> offer SSL-encrypted email sessions.
+ </div><a id="idm83813200" class="indexterm"></a><div class="para">
+ Like any other service that flows over a network unencrypted, important email information, such as usernames, 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 usernames 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">14.5.1.1. 安全な電子メールクライアント</h4></div></div></div><a id="idm133134320" 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">14.5.1.2. 安全な電子クライアント通信</h4></div></div></div><a id="idm123504848" class="indexterm"></a><a id="idm104398736" 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">
+ 自己署名付き証明書は、テスト目的の為にのみ使用すべきものです。生産環境で使用するサーバーはすべて CA により認可された SSL 証明書を使用すべきです。
+ </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.conf</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">
+ Execute the <code class="command">systemctl restart dovecot.service</code> command to restart the <code class="command">dovecot</code> daemon.
+ </div><div class="para">
+ Alternatively, the <code class="command">stunnel</code> command can be used as an SSL 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">yum install stunnel</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</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">/usr/bin/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>, refer to the <code class="command">stunnel</code> man page or the documents in the <code class="filename">/usr/share/doc/stunnel-<em class="replaceable"><code>version-number</code></em> </code>/ directory, where <em class="replaceable"><code>version-number</code></em> is the version number of <code class="command">stunnel</code>.
+ </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">14.6. その他のリソース</h2></div></div></div><a id="idm134312672" class="indexterm"></a><a id="idm114110880" class="indexterm"></a><a id="idm114109136" class="indexterm"></a><a id="idm96592240" 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">14.6.1. インストールされているドキュメント</h3></div></div></div><a id="idm91270496" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Information on configuring Sendmail is included with the <code class="filename">sendmail</code> and <code class="filename">sendmail-cf</code> 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-<em class="replaceable"><code>version-number</code></em> </code> — Contains a large amount of information about ways to configure Postfix. Replace <em class="replaceable"><code>version-number</code></em> with the version number of Postfix.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/fetchmail-<em class="replaceable"><code>version-number</code></em> </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. Replace <em class="replaceable"><code>version-number</code></em> with the version number of Fetchmail.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/procmail-<em class="replaceable"><code>version-number</code></em> </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. Replace <em class="replaceable"><code>version-number</code></em> with the version number of Procmail.
+ </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-<em class="replaceable"><code>version-number</code></em>/</code> — Contains a large amount of information pertaining to SpamAssassin. Replace <em class="replaceable"><code>version-number</code></em> with the version number of the <code class="filename">spamassassin</code> package.
+ </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">14.6.2. 役に立つ Web サイト</h3></div></div></div><a id="idm108232672" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.sendmail.org/">http://www.sendmail.org/</a> — 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/</a> — 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://fetchmail.berlios.de/">http://fetchmail.berlios.de/</a> — Fetchmail のホームページです。オンラインマニュアルや全体的な FAQ が特徴です。
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.procmail.org/">http://www.procmail.org/</a> — 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://partmaps.org/era/procmail/mini-faq.html">http://partmaps.org/era/procmail/mini-faq.html</a> — An excellent Procmail FAQ, offers troubleshooting tips, details about file locking, and the use of wildcard characters.
+ </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.org/</a> — 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">14.6.3. 関連書籍</h3></div></div></div><a id="idm107071168" 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">第15章 ディレクトリー サーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-OpenLDAP">15.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">15.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">15.1.2. OpenLDAP 製品群のインストール</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">15.1.3. OpenLDAP サーバーの設定法</a></span></dt><dt><span class="section"><a href="#s2-ldap-running">15.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">15.1.5. システムが OpenLDAP を使用して認証を実行するように設定する</a></span></dt><dt><span class="section"><a href="#s2-ldap-r
esources">15.1.6. その他のリソース</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">15.1. OpenLDAP</h2></div></div></div><a id="idm21711296" class="indexterm"></a><a id="idm91603824" class="indexterm"></a><a id="idm91605680" class="indexterm"></a><a id="idm91607568" 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">15.1.1. Introduction to LDAP</h3></div></div></div><div class="para">
+ Using a client/server architecture, LDAP provides 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">Secure Sockets Layer</em> (<acronym class="acronym">SSL</acronym>) or <em class="firstterm">Transport Layer Security</em> (<acronym class="acronym">TLS</acronym>) cryptographic protocols 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 17 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, refer to <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">15.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="idm117239696" 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="idm122283536" 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, other 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="idm90024352" 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">15.1.1.2. OpenLDAP 機能</h4></div></div></div><a id="idm95150592" 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">15.1.1.3. OpenLDAP サーバーのセットアップ</h4></div></div></div><a id="idm76636640" 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">
+ OpenLDAP 製品群をインストールします。必要なパッケージの詳細は<a class="xref" href="#s2-ldap-installation">「OpenLDAP 製品群のインストール」</a>を参照してください。
+ </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">15.1.2. OpenLDAP 製品群のインストール</h3></div></div></div><a id="idm107039344" class="indexterm"></a><a id="idm120012640" class="indexterm"></a><div class="para">
+ OpenLDAP のライブラリとツールの製品群は以下のパッケージにより提供されます:
+ </div><div class="table" id="table-ldap-packages-openldap"><h6>表15.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>表15.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_authz_ldap</span>
+ </td><td class="">
+ <div class="para">
+ A package containing <code class="systemitem">mod_authz_ldap</code>, the LDAP authorization module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. Note that the <code class="systemitem">mod_ssl</code> module is required when using the <code class="systemitem">mod_authz_ldap</code> module.
+ </div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ これらのパッケージをインストールするには、以下の形式で <code class="command">yum</code> コマンドを使用します:
+ </div><pre class="screen"><code class="command">yum</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">yum 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, refer to <a class="xref" href="#sec-Installing">「パッケージのインストール」</a>.
+ </div><div class="section" id="s3-ldap-packages-openldap-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.2.1. OpenLDAP サーバーユーティリティの概要</h4></div></div></div><a id="idm76020224" 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>表15.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, refer to the corresponding manual pages as referred to in <a class="xref" href="#s3-ldap-installed-docs">「インストールされているドキュメント」</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">
+ 起動、停止、再起動および <code class="systemitem">slapd</code> サービスの現在の状態を確認する方法の詳細は、<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">15.1.2.2. OpenLDAP クライアントユーティリティの概要</h4></div></div></div><a id="idm137389360" class="indexterm"></a><div class="para">
+ <span class="package">openldap-clients</span> パッケージは、LDAP ディレクトリのエントリを追加、変更および削除するために使用できる以下のユーティリティをインストールします:
+ </div><div class="table" id="table-ldap-packages-openldap-clients"><h6>表15.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">15.1.2.3. 一般的な LDAP クライアントアプリケーションの概要</h4></div></div></div><a id="idm97369808" 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">15.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>表15.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="idm81252720" 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="idm104923520" 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">15.1.3.1. 全体設定の変更方法</h4></div></div></div><a id="idm128920368" class="indexterm"></a><a id="idm128922448" 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="idm104904848" 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">表15.6「利用可能な olcAllows オプション」</a>. The default option is <code class="option">bind_v2</code>.
+ </div><div class="table" id="table-ldap-configuration-olcallows"><h6>表15.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>例15.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="idm91728544" 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>例15.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="idm108669328" 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>例15.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="idm97567632" 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">表15.7「利用可能な olcDisallows オプション」</a>. No features are disabled by default.
+ </div><div class="table" id="table-ldap-configuration-olcdisallows"><h6>表15.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>例15.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="idm80014000" 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>例15.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="idm132012416" 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>例15.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="idm117481792" 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>例15.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="idm88651280" 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>例15.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">15.1.3.2. データベース固有の設定の変更法</h4></div></div></div><a id="idm81244256" class="indexterm"></a><a id="idm81245504" 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="idm98094432" 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>例15.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="idm106786320" 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>例15.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="idm80263536" 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, use the <code class="command">slappaswd</code> utility, for example:
+ </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>例15.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="idm75230976" 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>例15.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">15.1.3.3. Extending Schema</h4></div></div></div><a id="idp1736656" class="indexterm"></a><a id="idp1734176" 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, refer to <a href="http://www.openldap.org/doc/admin/schema.html">http://www.openldap.org/doc/admin/schema.html</a>.
+ </div></div></div><div class="section" id="s2-ldap-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.1.4. Running an OpenLDAP Server</h3></div></div></div><a id="idm94372512" 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, refer to <a class="xref" href="#ch-Services_and_Daemons">8章<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">15.1.4.1. サービスの開始</h4></div></div></div><a id="idm94376512" class="indexterm"></a><div class="para">
+ To run the <code class="systemitem">slapd</code> service, 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">
+ ブート時にサービスを自動的に開始したければ、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl enable slapd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s3-ldap-running-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.4.2. サービスの停止</h4></div></div></div><a id="idm92390688" class="indexterm"></a><div class="para">
+ To stop the running <code class="systemitem">slapd</code> service, 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">
+ 起動時にサービスが自動的に開始しないようにするには、次のように入力します:
+ </div><pre class="screen"><code class="command">systemctl disable slapd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s3-ldap-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.4.3. サービスの再起動方法</h4></div></div></div><a id="idm106733184" 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">
+ これにより、サービスが停止し、再び起動します。設定を再読み込みするためにこのコマンドを使用します。
+ </div></div><div class="section" id="s3-ldap-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.4.4. サービスの状態の確認方法</h4></div></div></div><a id="idm85330560" class="indexterm"></a><div class="para">
+ サービスが実行中であるかどうかを確認するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen"><code class="command">systemctl is-active slapd.service</code></pre></div></div><div class="section" id="s2-ldap-pam"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.1.5. システムが 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">yum install openldap openldap-clients nss-pam-ldapd</code></pre><div class="para">
+ <a class="xref" href="#ch-Configuring_Authentication">9章<em>認証の設定</em></a> provides detailed instructions on how to configure applications to use LDAP for authentication.
+ </div><div class="section" id="s3-ldap-migrationtools"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.5.1. 古い認証情報を LDAP フォーマットへ移行</h4></div></div></div><a id="idm129978032" 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">yum 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, refer to <a class="xref" href="#table-ldap-migrationtools">表15.8「一般的に使用される LDAP 移行スクリプト」</a>.
+ </div><div class="table" id="table-ldap-migrationtools"><h6>表15.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, refer to 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-<em class="replaceable"><code>version</code></em>/</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">15.1.6. その他のリソース</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><div class="section" id="s3-ldap-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.6.1. インストールされているドキュメント</h4></div></div></div><div class="para">
+ The following documentation is installed with the <span class="package">openldap-servers</span> package:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/openldap-servers-<em class="replaceable"><code>version</code></em>/guide.html</code></span></dt><dd><div class="para">
+ A copy of the <em class="citetitle">OpenLDAP Software Administrator's Guide</em>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/openldap-servers-<em class="replaceable"><code>version</code></em>/README.schema</code></span></dt><dd><div class="para">
+ A README file containing the description of installed schema files.
+ </div></dd></dl></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">
+ <code class="command">man ldapadd</code> — Describes how to add entries to an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapdelete</code> — Describes how to delete entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapmodify</code> — Describes how to modify entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapsearch</code> — Describes how to search for entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldappasswd</code> — Describes how to set or change the password of an LDAP user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapcompare</code> — Describes how to use the <code class="command">ldapcompare</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapwhoami</code> — Describes how to use the <code class="command">ldapwhoami</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapmodrdn</code> — 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">
+ <code class="command">man slapd</code> — 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">
+ <code class="command">man slapadd</code> — Describes command line options used to add entries to a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapcat</code> — 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">
+ <code class="command">man slapindex</code> — 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">
+ <code class="command">man slappasswd</code> — 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">
+ <code class="command">man ldap.conf</code> — Describes the format and options available within the configuration file for LDAP clients.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapd-config</code> — Describes the format and options available within the configuration directory.
+ </div></li></ul></div></dd></dl></div></div><div class="section" id="s3-ldap-additional-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.6.2. 役に立つ Web サイト</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.openldap.org/doc/admin24/">http://www.openldap.org/doc/admin24/</a></span></dt><dd><div 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://www.kingsmountain.com/ldapRoadmap.shtml</a></span></dt><dd><div 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.org/articles/</a></span></dt><dd><div 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></span></dt><dd><div 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"><h4 class="title">15.1.6.3. 関連書籍</h4></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><div xml:lang="ja-JP" class="chapter" id="ch-File_and_Print_Servers" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第16章 ファイルサーバーおよびプリントサーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-Samba">16.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">16.1.1. Samba の概要</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">16.1.2. Samba デーモンと関連サービス</a></span></dt><dt><span class="section"><a href="#s2-samba-connect-share">16.1.3. Samba シェアへの接続</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">16.1.4. Samba サーバーの設定</a></span></dt><dt><span class="section"><a href="#s2-samba-startstop">16.1.5. Samba の開始と停止</a></span></dt><dt><span class="section"><a href="#s2-samba-servers">16.1.6. Samba サーバ
ー形å¼ã¨ <code class="filename">smb.conf</code> ファイル</a></span></dt><dt><span class="section"><a href="#s2-samba-security-modes">16.1.7. Samba ã®ã‚»ã‚ュリティモード</a></span></dt><dt><span class="section"><a href="#s2-samba-account-info-dbs">16.1.8. Samba ã®ã‚¢ã‚«ã‚¦ãƒ³ãƒˆæƒ…å ±ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹</a></span></dt><dt><span class="section"><a href="#s2-samba-network-browsing">16.1.9. Samba ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ–ラウジング</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">16.1.10. CUPS å°åˆ·ã‚µãƒãƒ¼ãƒˆã‚’使ã£ãŸ Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">16.1.11. Samba ディストリビューションプãƒã‚°ãƒ©ãƒ </a></span></dt><dt><span class="section"><a href="#s2-samba-resources">16.1.12. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">16.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol">16.2.1. ファイルä¼é€ãƒ
—ãƒãƒˆã‚³ãƒ«</a></span></dt><dt><span class="section"><a href="#s2-ftp-servers">16.2.2. FTP サーãƒãƒ¼</a></span></dt><dt><span class="section"><a href="#s3-ftp-vsftpd-conf">16.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-start">16.2.4. <code class="command">vsftpd</code> ã®é–‹å§‹ã¨åœæ¢</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">16.2.5. <code class="command">vsftpd</code> è¨å®šã‚ªãƒ—ション</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">16.2.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration">16.3. プリンタã®è¨å®š</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">16.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="#sec-Setting_Printer">16.3.2. Starting Printer Setup</a></span></dt><d
t><span class="section"><a href="#sec-Adding_Other_Printer">16.3.3. ローカルプリンタの追加</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">16.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">16.3.5. IPP プリンタの追加</a></span></dt><dt><span class="section"><a href="#sec-printing-LPDLPR-printer">16.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">16.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">16.3.8. プリンタモデルの選択と終了</a></span></dt><dt><span class="section"><a href="#s1-printing-test-page">16.3.9. Printing a test page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">16.3.10. 既存プリンタの変更</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-res
ources">16.3.11. その他のリソース</a></span></dt></dl></dd></dl></div><div class="para">
+ <em class="firstterm">Server Message Block</em> (<acronym class="acronym">SMB</acronym>) プロトコルのオープンソース実装である <span class="application"><strong>Samba</strong></span> および Fedora に同梱されている主要な FTP サーバーである <span class="application"><strong>vsftpd</strong></span> のインストールおよび設定についてガイドしています。さらに、プリンターを設定するための<span class="application"><strong>プリンター設定</strong></span>ツールを使用する方法を説明しています。
+ </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">16.1. Samba</h2></div></div></div><a id="idm127418032" class="indexterm"></a><a id="idm115908176" class="indexterm"></a><div class="para">
+ <em class="firstterm">Samba</em> is an open source implementation of the <em class="firstterm">Server Message Block</em> (<code class="systemitem">SMB</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">yum install samba</code></pre><div class="para">
+ Yum を用いてパッケージをインストールする方法の詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</a>を参照してください。
+ </div></div></div><div class="section" id="samba-rgs-overview"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.1. Samba の概要</h3></div></div></div><a id="idm116685216" class="indexterm"></a><div class="para">
+ Samba の 3 番目のメジャーリリースとなる バージョン 3.0.0 は 旧バージョンから数多くの改良が導入されました。
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The ability to join an Active Directory domain by means of the <em class="firstterm">Lightweight Directory Access Protocol</em> (<code class="systemitem">LDAP</code>) and <em class="firstterm">Kerberos</em>
+ </div></li><li class="listitem"><div class="para">
+ 国際化のための組み込み Unicode サポート
+ </div></li><li class="listitem"><div class="para">
+ 最近の Microsoft Windows サーバーとクライアントのすべてのバージョンが、ローカルレジストリの変更の必要性なく、Samba サーバーへの接続をサポートします
+ </div></li><li class="listitem"><div class="para">
+ Two new documents developed by the Samba.org team, which include a 400+ page reference manual, and a 300+ page implementation and integration manual. For more information about these published titles, refer to <a class="xref" href="#s3-samba-resources-published">「関連書籍」</a>.
+ </div></li></ul></div><div class="section" id="s3-samba-abilities"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">16.1.1.1. Samba の機能</h4></div></div></div><a id="idm115910896" class="indexterm"></a><div class="para">
+ Samba はパワフルで用途の広いサーバアプリケーションです。経験豊富なシステム管理者であってもその機能や限界を学んでからインストール及び設定は行ってください。
+ </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
+ </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">16.1.2. Samba デーモンと関連サービス</h3></div></div></div><a id="idm91933872" 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">16.1.2.1. Samba デーモン</h4></div></div></div><a id="idm89467968" 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="idm97829968" 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="idm97455040" 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/<em class="firstterm">Common Internet File System</em> (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="idm101571840" class="indexterm"></a><div class="para">
+ The <code class="command">winbind</code> service resolves user and group information on a server running Windows NT, 2000, 2003 or Windows Server 2008. This makes Windows user / 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/or 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">
+ You may refer to <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">16.1.3. Samba シェアへの接続</h3></div></div></div><a id="idm127498912" 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>図16.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">16.1.3.1. コマンドライン</h4></div></div></div><a id="idm113128624" class="indexterm"></a><a id="idm113130368" class="indexterm"></a><a id="idm113134240" 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="idm86252256" class="indexterm"></a><a id="idm86255488" 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 wish 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">16.1.3.2. シェアの実装</h4></div></div></div><a id="idm107100672" 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">yum install cifs-utils</code></pre><div class="para">
+ Yum を用いてパッケージをインストールする方法の詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</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>, refer to <code class="command">man cifs.upcall</code>.
+ </div></div></div><div class="para">
+ Samba 共有のマウントに関する詳細は <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">16.1.4. Samba サーバーの設定</h3></div></div></div><a id="idm9196096" class="indexterm"></a><a id="idm9197616" 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. In other words, 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">16.1.4.1. グラフィックな設定</h4></div></div></div><a id="idm139539008" 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/samba/GUI/</a>.
+ </div></div><div class="section" id="s3-samba-configuring-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">16.1.4.2. コマンドライン管理</h4></div></div></div><a id="idm112657104" 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">16.1.4.3. 暗合化されたパスワード</h4></div></div></div><div class="para">
+ Encrypted passwords are enabled by default because it is more secure to do so. 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="idm123715952" class="indexterm"></a><a id="idm77809664" class="indexterm"></a><a id="idm77811408" class="indexterm"></a><a id="idm77814160" class="indexterm"></a><a id="idm77815888" class="indexterm"></a><a id="idm121942848" class="indexterm"></a><a id="idm121944320" 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">16.1.5. Samba の開始と停止</h3></div></div></div><a id="idm112903296" class="indexterm"></a><a id="idm112901120" class="indexterm"></a><a id="idm112903744" class="indexterm"></a><a id="idm116764992" class="indexterm"></a><a id="idm117313312" 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.
+ </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, use a service manager such as <code class="command">systemctl</code>. Refer to <a class="xref" href="#ch-Services_and_Daemons">8章<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">16.1.6. Samba サーバー形式と <code class="filename">smb.conf</code> ファイル</h3></div></div></div><a id="idm139817648" class="indexterm"></a><a id="idm139817968" 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">16.1.6.1. スタンドアローンのサーバ</h4></div></div></div><a id="idm113849552" 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">16.1.6.1.1. Anonymous 読み取り専用</h5></div></div></div><a id="idm101268688" 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">16.1.6.1.2. Anonymous 読み取り/書き込み</h5></div></div></div><a id="idm132861424" 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">16.1.6.1.3. Anonymous プリントサーバ</h5></div></div></div><a id="idm137356000" 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">16.1.6.1.4. 安全な読み取り/書き込みファイルとプリントサーバ</h5></div></div></div><a id="idm117719376" 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">16.1.6.2. ドメインメンバーサーバ</h4></div></div></div><a id="idm111613280" 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">16.1.6.2.1. Active Directory ドメインメンバーサーバ</h5></div></div></div><a id="idm59225456" 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 at 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. For more information on Kerberos, the <code class="command">/etc/krb5.conf</code> file, and the <code class="command">kinit</code> command, refer to the <em class="citetitle">Using Kerberos</em> section of the Red Hat Enterprise Linux 6 <em class="citetitle">Managing Single Sign-On and Smart Cards</em> guide.
+ </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">16.1.6.2.2. Windows NT4 ベースのドメインメンバーサーバ</h5></div></div></div><a id="idm131721136" 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">16.1.6.3. Domain Controller</h4></div></div></div><a id="idm91174656" 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">16.1.6.3.1. Primary Domain Controller (PDC) using <code class="command">tdbsam</code> </h5></div></div></div><a id="idm88624688" 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">16.1.6.3.2. Active Directory を使ったプライマリドメインコントローラ (PDC)</h5></div></div></div><a id="idm21710336" 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">16.1.7. Samba のセキュリティモード</h3></div></div></div><a id="idm105127696" 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">16.1.7.1. ユーザーレベルセキュリティ</h4></div></div></div><a id="idm119428768" 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">16.1.7.1.1. ドメインセキュリティモード (ユーザーレベルセキュリティ)</h5></div></div></div><a id="idm71446400" 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">16.1.7.1.2. Active Directory セキュリティモード (ユーザーレベルセキュリティ)</h5></div></div></div><a id="idm133801520" 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">16.1.7.1.3. サーバセキュリティモード(ユーザーレベルセキュリティ)</h5></div></div></div><a id="idm90137584" 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">16.1.7.2. Share-Level Security</h4></div></div></div><a id="idm122983952" 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">16.1.8. Samba のアカウント情報データベース</h3></div></div></div><a id="idm121247440" 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="idm108879248" class="indexterm"></a><a id="idm109376288" class="indexterm"></a><a id="idm118727648" class="indexterm"></a><a id="idm94454608" class="indexterm"></a><a id="idm102816816" class="indexterm"></a><a id="idm100331008" class="indexterm"></a><a id="idm98399760" class="indexterm"></a><a id="idm120519280" class="indexterm"></a><a id="idm134236592" 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 the <span class="application"><strong>Red Hat Directory Server</strong></span> or an <span class="application"><strong>OpenLDAP Server</strong></span>. LDAP databases are light-weight and scalable, and as such are preferred by large enterprises. Installation and configuration of directory servers is beyond the scope of this chapter. For more information on the <span class="application"><strong>Red Hat Directory Server</strong></span>, refer to the <em class="citetitle">Red Hat Directory Server 8.2 Deployment Guide</em>. 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-<em class="replaceable"><code>version</code></em>/LDAP/samba.schema</code>) and the Red Hat Directory Server schema file (<code class="filename">/usr/share/doc/samba-<em class="replaceable"><code>version</code></em>/LDAP/samba-schema-FDS.ldif</code>) have 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. Refer to <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">16.1.9. Samba ネットワークブラウジング</h3></div></div></div><a id="idm129256240" class="indexterm"></a><a id="idm102833472" 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">16.1.9.1. Domain Browsing</h4></div></div></div><a id="idm133740800" class="indexterm"></a><div class="para">
+ デフォルトでは、ドメインの Windows PDC もそのドメインのドメインマスターブラウザです。このような場合、 Samba サーバはドメインマスターサーバとして設定する必要があります。
+ </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.
+ </div></div><div class="section" id="s3-samba-wins"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">16.1.9.2. WINS (Windows Internet Name Server)</h4></div></div></div><a id="idm82931328" class="indexterm"></a><a id="idm134559664" 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">16.1.10. CUPS 印刷サポートを使った Samba</h3></div></div></div><a id="idm102760592" 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">16.1.10.1. Simple <code class="filename">smb.conf</code> Settings</h4></div></div></div><a id="idm54439936" 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">16.1.11. Samba ディストリビューションプログラム</h3></div></div></div><a id="idm83437584" class="indexterm"></a><h4 id="s3-samba-programs-findsmb"><code class="filename">findsmb</code></h4><a id="idm136929920" class="indexterm"></a><a id="idm121135360" 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="idm121098288" class="indexterm"></a><a id="idm112734128" 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 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="idm101853360" class="indexterm"></a><a id="idm113697488" 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">
+ 次がその例です。
+ </div><pre class="screen">~]$ <code class="command">nmblookup trek</code>
+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="idm81454240" class="indexterm"></a><a id="idm111253040" 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="idm93381104" class="indexterm"></a><a id="idm131985568" 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="idm123932480" class="indexterm"></a><a id="idm148533952" 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="idm89931744" class="indexterm"></a><a id="idm104893808" 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="idm101419312" class="indexterm"></a><a id="idm71445728" 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="idm109372960" class="indexterm"></a><a id="idm111861568" 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 as well as 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="idm105874528" class="indexterm"></a><a id="idm88983360" 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="idm94361952" class="indexterm"></a><a id="idm85467664" 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="idm113756016" class="indexterm"></a><a id="idm129064032" 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="idm104894560" class="indexterm"></a><a id="idm90092752" 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">/etc/samba/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 hostname and IP 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">/etc/samba/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="idm106481712" class="indexterm"></a><a id="idm128975024" 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">16.1.12. その他のリソース</h3></div></div></div><a id="idm120286544" 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">16.1.12.1. インストールされているドキュメント</h4></div></div></div><a id="idm114500272" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/samba-<em class="replaceable"><code>version-number</code></em>/</code> — All additional files included with the Samba distribution. This includes all helper scripts, sample configuration files, and documentation. This directory also contains online versions of <em class="citetitle">The Official Samba-3 HOWTO-Collection</em> and <em class="citetitle">Samba-3 by Example</em>, both of which are cited below.
+ </div><div class="note"><div class="admonition_header"><h2>Make sure you have the samba-doc package installed</h2></div><div class="admonition"><div class="para">
+ In order to use the <span class="application"><strong>Samba</strong></span> documentation, first ensure the <span class="package">samba-doc</span> package is installed on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install samba-doc</code></pre><div class="para">
+ Yum を用いてパッケージをインストールする方法の詳細は<a class="xref" href="#sec-Installing">「パッケージのインストール」</a>を参照してください。
+ </div></div></div></li></ul></div><div class="para">
+ Refer to the following manual pages for detailed information specific <span class="application"><strong>Samba</strong></span> features:
+ </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">16.1.12.2. 関連書籍</h4></div></div></div><a id="idm84967216" 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">16.1.12.3. 役に立つ Web サイト</h4></div></div></div><a id="idm96107872" 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.org/samba/archives.html </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 gmane.org, that use the NNTP 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">16.2. FTP</h2></div></div></div><a id="idm133495088" class="indexterm"></a><a id="idm108345696" 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">16.2.1. ファイル伝送プロトコル</h3></div></div></div><a id="idm127868320" 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">16.2.1.1. マルチポート、マルチモード</h4></div></div></div><a id="idp1290400" class="indexterm"></a><a id="idm123400560" class="indexterm"></a><a id="idm129654688" class="indexterm"></a><a id="idm134558064" 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. Refer to <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">16.2.2. FTP サーバー</h3></div></div></div><a id="idm118320800" class="indexterm"></a><a id="idm120797776" class="indexterm"></a><a id="idm135633904" class="indexterm"></a><a id="idm93133136" 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">
+ <span class="application"><strong>Red Hat Content Accelerator</strong></span> — A kernel-based Web server that delivers high performance Web server and <code class="systemitem">FTP</code> services. Since speed is its primary design goal, it has limited functionality and runs only as an anonymous <code class="systemitem">FTP</code> server. For more information about configuring and administering <span class="application"><strong>Red Hat Content Accelerator</strong></span>, consult the documentation available online at <a href="http://www.redhat.com/docs/manuals/tux/">http://www.redhat.com/docs/manuals/tux/</a>.
+ </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">16.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">16.2.3. Files Installed with <code class="command">vsftpd</code> </h3></div></div></div><a id="idm86057440" 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>. Refer to <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 17 <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>. Refer to <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">16.2.4. <code class="command">vsftpd</code> の開始と停止</h3></div></div></div><a id="idm90758224" class="indexterm"></a><a id="idm111862688" class="indexterm"></a><a id="idm99897824" class="indexterm"></a><a id="idm110372384" class="indexterm"></a><a id="idm89116752" 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>. Refer to <a class="xref" href="#ch-Services_and_Daemons">8章<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">16.2.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </h4></div></div></div><a id="idm112823488" class="indexterm"></a><a id="idm18499744" 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. Additional information about network configuration scripts can be found in <a class="xref" href="#ch-Network_Interfaces">7章<em>ネットワーク・インターフェース</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 <a class="xref" href="#s1-BIND">「BIND」</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">16.2.5. <code class="command">vsftpd</code> 設定オプション</h3></div></div></div><a id="idm85272336" class="indexterm"></a><a id="idm104308560" 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>, refer to the Fedora 17 <em class="citetitle">Security Guide</em>.
+ </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">16.2.5.1. デーモンオプション</h4></div></div></div><a id="idm134140640" 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">16.2.5.2. ログインオプションとアクセス制御</h4></div></div></div><a id="idm114078592" class="indexterm"></a><a id="idm114183472" 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">
+ Refer to <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">
+ Refer to <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">16.2.5.3. 匿名ユーザーオプション</h4></div></div></div><a id="idm114581776" 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">16.2.5.4. ローカルユーザーオプション</h4></div></div></div><a id="idm107108432" 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">16.2.5.5. ディレクトリオプション</h4></div></div></div><a id="idm109827312" 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">16.2.5.6. ファイル転送のオプション</h4></div></div></div><a id="idm76838112" 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">16.2.5.7. ロギングのオプション</h4></div></div></div><a id="idm74809520" 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">16.2.5.8. ネットワークオプション</h4></div></div></div><a id="idm101711984" 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. Refer to <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. Refer to <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">16.2.6. その他のリソース</h3></div></div></div><a id="idm116949056" 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">16.2.6.1. インストールされているドキュメント</h4></div></div></div><a id="idm18496096" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="filename">/usr/share/doc/vsftpd-<em class="replaceable"><code>version-number</code></em>/</code> directory — Replace <em class="replaceable"><code>version-number</code></em> with the installed version of the <code class="filename">vsftpd</code> package. 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">16.2.6.2. 役に立つ Web サイト</h4></div></div></div><a id="idm84738448" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/</a> — 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.com/other/ftp.html</a> — 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.org/rfc/rfc0959.txt</a> — 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">16.3. プリンタの設定</h2></div></div></div><a id="idm69492416" class="indexterm"></a><a id="idm118281440" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Printer Configuration</strong></span> 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="idm100543280" 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">16.3.1. Starting the Printer Configuration Tool</h3></div></div></div><div class="para">
+ With the Printer Configuration tool you can perform various operations on existing printers and set up new printers.
+ </div><div class="para">
+ On the upper panel, go to <span class="guimenu"><strong>Activities</strong></span>, choose <span class="guisubmenu"><strong>Applications</strong></span> and click <span class="guimenuitem"><strong>Printing</strong></span>. Alternatively, run the <code class="command">system-config-printer</code> command from the command line to start the tool.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Printer Configuration</strong></span> window depicted in <a class="xref" href="#fig-printconf-main">図16.2「Printer 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="Printer Configuration window" /><div class="longdesc"><div class="para">
+ Printer Configuration window
+ </div></div></div></div><h6>図16.2 Printer 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">16.3.2. Starting Printer Setup</h3></div></div></div><a id="idm125109504" 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 the root 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 Printer Configuration tool (refer to <a class="xref" href="#sec-Starting_Printer_Config">「Starting the Printer Configuration Tool」</a>).
+ </div></li><li class="step"><div class="para">
+ Go to <span class="guimenu"><strong>Server</strong></span> → <span class="guisubmenu"><strong>New</strong></span> → <span class="guimenuitem"><strong>Printer</strong></span>.
+ </div></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Authentication Required</strong></span> box, type the root user password and confirm.
+ </div></li><li class="step"><div class="para">
+ Select the printer connection type and provide its details in the area on the right.
+ </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">16.3.3. ローカルプリンタの追加</h3></div></div></div><a id="idm134247344" 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">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>図16.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. Refer to <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">16.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">New Printer</code> dialog (refer to <a class="xref" href="#sec-Starting_Printer_Config">「Starting the Printer 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 hostname or IP 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>図16.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. Refer to <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">16.3.5. IPP プリンタの追加</h3></div></div></div><a id="idm55404944" class="indexterm"></a><div class="para">
+ IPP プリンタは同じ TCP/IP ネットワーク上にある別のシステムに接続されたプリンタです。このプリンタが接続されるシステムは CUPS を実行しているか単純に IPP を使用するよう設定されているかのどちらかです。
+ </div><div class="para">
+ If a firewall is enabled on the printer server, then the firewall must be configured to allow incoming TCP connections on port 631. 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 UDP packets on port 631.
+ </div><div class="procedure" id="proc-Adding_IPP_Printer"><div class="para">
+ Follow this procedure to add an IPP 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> 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 hostname for the system that controls the 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 IPP Printer
+ </div></div></div></div><h6>図16.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. Refer to <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">16.3.6. Adding an LPD/LPR Host or Printer</h3></div></div></div><a id="idm58922832" 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 hostname 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>図16.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. Refer to <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">16.3.7. Adding a Samba (SMB) printer</h3></div></div></div><a id="idm119440928" class="indexterm"></a><a id="idm134700304" 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">yum install samba-client</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は <a class="xref" href="#sec-Installing">「パッケージのインストール」</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">図16.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>図16.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>: username 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 username 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 プリンタのユーザー名とパスワードは root 及び lpd によって読み取り可能な暗号化されていないファイルとしてプリンタサーバーに格納されます。したがって、プリンタサーバーに root アクセスを有するユーザーであれば他のユーザーが Samba プリンタへのアクセスに使用するユーザー名とパスワードを閲覧することができます。
+ </div><div class="para">
+ As such, when you choose a username 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. Refer to <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">16.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 PostScript Printer Description (PPD) 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>図16.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">図16.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 printed 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>図16.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>図16.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 also later, refer to <a class="xref" href="#s1-printing-test-page">「Printing a test page」</a> for details.
+ </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">16.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">16.3.10. 既存プリンタの変更</h3></div></div></div><div class="para">
+ To delete an existing printer, in the <span class="guilabel"><strong>Printer Configuration</strong></span> 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="idm104518544"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm104518544">16.3.10.1. The Settings Page</h4></div></div></div><a id="idm18546112" 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>図16.11 Settings page</h6></div><br class="figure-break" /></div><div class="section" id="idm103987664"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm103987664">16.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 username 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-menu and choose the option that best describes the nature of the print jobs (such as <span class="guilabel"><strong>topsecret</strong></span>, <span class="guilabel"><strong>classified</strong></span>, or <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">16.3.10.2.1. Sharing Printers</h5></div></div></div><a id="idm113049984" 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="para">
+ Finally, ensure that the firewall allows incoming TCP connections to port 631, which is Network Printing Server (IPP) in system-config-firewall.
+ </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>図16.12 Policies page</h6></div><br class="figure-break" /></div><div class="section" id="sec-The_Access_Control_Page"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">16.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>図16.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">16.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>図16.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">16.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>図16.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">16.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>図16.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">16.3.10.3. 印刷ジョブの管理</h4></div></div></div><a id="idm17812368" 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>図16.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>例16.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">例16.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 root 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">16.3.11. その他のリソース</h3></div></div></div><div class="para">
+ To learn more about printing on Fedora, refer to 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">16.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">16.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.linuxprinting.org/</a></span></dt><dd><div 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></span></dt><dd><div class="para">
+ Documentation, FAQs, and newsgroups about CUPS.
+ </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">パート VI. 監視および自動化</h1></div></div></div><div class="partintro" id="idm110126880"><div></div><div class="para">
+ このパートは、システム管理者がシステムのパフォーマンスを監視する、システムタスクを自動化する、およびバグを報告することができる、さまざまなツールを説明しています。
+ </div><div class="toc"><p><strong>目次</strong></p><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 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 Syste
m 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_Monitoring_To
ols-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-configuring-rsyslog">18.1. rsyslog ã®è¨å®šæ³•</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-global-directives">18.1.1. 全体ディレクティブ</a></span></dt><dt><span class="section"><a href="#s2-modules">18.1.2. モジュール</a></span></dt><dt><span class="section"><a href="#s2-rules">18.1.3. ルール</a></span></dt><dt><span class="section"><a href="#s2-rsyslog-cmd-options">18.1.4. <span class="application"><strong>rsyslog</strong></span> コマンドラインè¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-logfiles-locating">18.2. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’探ã™</a></span></dt><dd><dl><dt><span class="section"><a href="#configuring-logrotate">18.2.1. logrotate ã®è¨å®šæ³•</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-logfiles-viewing">18.3. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º</a></span></dt><dt><span class="section"><a href="#s1-
logfiles-adding">18.4. ログファイルの追加</a></span></dt><dt><span class="section"><a href="#s1-logfiles-examining">18.5. ログファイルを監視する</a></span></dt><dt><span class="section"><a href="#s1-log-files-additional-resources">18.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-log-files-installed-docs">18.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-log-files-useful-websites">18.6.2. 役に立つ Web サイト</a></span></dt></dl></dd></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="#s2-autotasks-cron-service">19.1.1. サービスの起動と停止</a></span></dt><dt><span class="section"><a href="#s2-configuring-
anacron-jobs">19.1.2. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="#s2-configuring-cron-jobs">19.1.3. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">19.1.4. Cron へのアクセスの制御</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-cron-jobs">19.1.5. Black/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="#s2-autotasks-at-configuring">19.2.1. At ジョブの設定</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">19.2.2. batch ジョブの設定</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">19.2.3. 保留ジョブの表示</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">19.2.4. その他のコマ
ンドラインオプション</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">19.2.5. at と batch へのアクセスの制御</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-service">19.2.6. サービスの起動と停止</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">19.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-installed-docs">19.3.1. インストールされているドキュメント</a></span></dt></dl></dd></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><dt><span class="section"><a href="#s1-oprofile-configuring">20.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">20.2.1. Specifying the Kernel<
/a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">20.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">20.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">20.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">20.4. Saving Data</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">20.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">20.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">20.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">20.5.3. Getting more detailed output on the modules</a></span></dt><dt><span cla
ss="section"><a href="#s2-oprofile-reading-opannotate">20.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">20.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">20.7. 使用法の例</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">20.8. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">20.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">20.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-and-systemtap">20.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">20.11. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-insta
lled-docs">20.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="#s2-oprofile-useful-websites">20.11.2. 役に立つ Web サイト</a></span></dt></dl></dd></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><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 Us
age</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-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 lsc
pu 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 c
lass="section"><a href="#s2-sysinfo-installed-docs">17.7.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a id="idm110466240" class="indexterm"></a><a id="idm122178720" 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="idm130558416" class="indexterm"></a><a id="idm86076160" 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="idm125046448" 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="idm52431248" class="indexterm"></a><a id="idm127963392" 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="idm126118240" class="indexterm"></a><a id="idm126117120" 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="idm134689424" class="indexterm"></a><a id="idm134687984" class="indexterm"></a><a id="idm48012864" 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="idm136979584" 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="idm118888864" class="indexterm"></a><a id="idm117306416" 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="idm52423520" class="indexterm"></a><a id="idm69489744" 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="idm97181184" class="indexterm"></a><a id="idm97180064" 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="idm107332288" class="indexterm"></a><a id="idm107330880" 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="idm89922400" 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="idm124254688" 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="idm119688928" 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="idm67904480" 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="idm122116464" 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="idm90145168" class="indexterm"></a><a id="idm80339856" class="indexterm"></a><a id="idm69282944" class="indexterm"></a><a id="idm137445792" class="indexterm"></a><a id="idm137444672" class="indexterm"></a><a id="idm88705216" 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="idm121574480" 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="idm109346800" class="indexterm"></a><a id="idm119004224" 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="idm110291520" class="indexterm"></a><a id="idm128125680" 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="idm138480816" 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="idm126473424" 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="idm67873200" 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="idm112675040" 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 17 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">yum</code> command in the following form:
+ </div><pre class="synopsis"><code class="command">yum</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">yum 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">「パッケージのインストール」</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">8章<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 17 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 at 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 <admin at example.com></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 <admin at example.com>
+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 <admin at example.com>
+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. Refer to 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><dt><span class="section"><a href="#s1-configuring-rsyslog">18.1. rsyslog の設定法</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-global-directives">18.1.1. 全体ディレクティブ</a></span></dt><dt><span class="section"><a href="#s2-modules">18.1.2. モジュール</a></span></dt><dt><span class="section"><a href="#s2-rules">18.1.3. ルール</a></span></dt><dt><span class="section"><a href="#s2-rsyslog-cmd-options">18.1.4. <span class="application"><strong>rsyslog</strong></span> コマンドライン設定</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-logfiles-locating">18.2. ログファイルを探す</a></span></dt><dd><dl><dt><span class="section"><a
href="#configuring-logrotate">18.2.1. logrotate の設定法</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-logfiles-viewing">18.3. ログファイルの表示</a></span></dt><dt><span class="section"><a href="#s1-logfiles-adding">18.4. ログファイルの追加</a></span></dt><dt><span class="section"><a href="#s1-logfiles-examining">18.5. ログファイルを監視する</a></span></dt><dt><span class="section"><a href="#s1-log-files-additional-resources">18.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-log-files-installed-docs">18.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-log-files-useful-websites">18.6.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></div><a id="idm87905024" class="indexterm"></a><a id="idm82962400" class="indexterm"></a><div class="para">
+ <em class="firstterm">ログファイル</em> は、システム上で動作しているカーネル、サービス、アプリケーションなどのシステムに関するメッセージが入っているファイルです。情報ごとに異なるログファイルがあります。例えば、デフォルトシステムログファイル、セキュリティメッセージだけのログファイル、 cron タスク用のログファイルなどがあります。
+ </div><div class="para">
+ Log files can be very useful when trying to troubleshoot a problem with the system such as trying to load a kernel driver or when looking for unauthorized login attempts to the system. This chapter discusses where to find log files, how to view log files, and what to look for in log files.
+ </div><a id="idm94389728" class="indexterm"></a><a id="idm135145472" class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code class="systemitem">rsyslogd</code>. 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.
+ </div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> is an enhanced, multi-threaded syslog daemon which replaced the <code class="command">sysklogd</code> daemon. <span class="application"><strong>rsyslog</strong></span> supports the same functionality as <span class="application"><strong>sysklogd</strong></span> and extends it with enhanced filtering, encryption protected relaying of messages, various configuration options, or support for transportation via the <code class="systemitem">TCP</code> or <code class="systemitem">UDP</code> protocols. Note that <span class="application"><strong>rsyslog</strong></span> is compatible with <span class="application"><strong>sysklogd</strong></span>.
+ </div><div class="section" id="s1-configuring-rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.1. 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>. It consists of <em class="firstterm">global directives</em>, <em class="firstterm">rules</em> or comments (any empty lines or any text following a hash sign (<code class="literal">#</code>)). Both, global directives and rules are extensively described in the sections below.
+ </div><div class="section" id="s2-global-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.1. 全体ディレクティブ</h3></div></div></div><div class="para">
+ Global directives specify configuration options that apply to the <code class="systemitem">rsyslogd</code> daemon. They usually specify a value for a specific pre-defined 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.
+ </div><div class="para">
+ A comprehensive list of all available configuration directives and their detailed description can be found in <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/rsyslog_conf_global.html</code>.
+ </div></div><div class="section" id="s2-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.2. モジュール</h3></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 dynamic 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 <code class="literal">Text File Input Module</code> (<code class="command">imfile</code> — enables <span class="application"><strong>rsyslog</strong></span> to convert any standard text files into syslog messages), specify the following line in your <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 these 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">imrelp</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Output Modules — Output modules provide a facility to store messages into various targets such as sending them across network, storing them in a database or encrypting them. 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">
+ Filter Modules — Filter modules provide the ability to filter messages according to specified rules. The name of a filter module always starts with the <code class="literal">fm</code> prefix.
+ </div></li><li class="listitem"><div class="para">
+ Parser Modules — Parser modules use the message parsers to parse message content of any received messages. 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>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Message Modification Modules — Message modification modules change the content of a syslog message. The message modification modules only differ in their implementation from the output and filter modules but share the same interface.
+ </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, refer to <a class="xref" href="#s3-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>, <code class="command">smtradfile</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Library Modules — Library modules generally 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/">http://www.rsyslog.com/doc/rsyslog_conf_modules.html</a>
+ </div><div class="warning"><div class="admonition_header"><h2>Make sure you use trustworthy modules only</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><div class="section" id="s2-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.3. ルール</h3></div></div></div><div class="para">
+ A rule is specified by a <em class="firstterm">filter</em> part, which selects a subset of syslog messages, and an <em class="firstterm">action</em> 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. For more information on filters, refer to <a class="xref" href="#s3-filter-conditions">「フィルター条件」</a> and for information on actions, refer to <a class="xref" href="#s3-actions">「アクション」</a>.
+ </div><div class="section" id="s3-filter-conditions"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">18.1.3.1. フィルター条件</h4></div></div></div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> offers various ways how to filter syslog messages according to various properties. This sections sums up the most used filter conditions.
+ </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>. 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 these keywords: <code class="command">auth</code>, <code class="command">authpriv</code>, <code class="command">cron</code>, <code class="command">daemon</code>, <code class="command">kern</code>, <code class="command">lpr</code>, <code class="command">mail</code>, <code class="command">news</code>, <code class="command">syslog</code>, <code class="command">user</code>, <code class="command">uucp</code>, and <code class="command">local0</code> through <code class="command">local7</code>.
+ </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 these keywords (listed in an ascending order): <code class="command">debug</code>, <code class="command">info</code>, <code class="command">notice</code>, <code class="command">warning</code>, <code class="command">err</code>, <code class="command">crit</code>, <code class="command">alert</code>, and <code class="command">emerg</code>.
+ </div><div class="para">
+ By preceding any priority with an equal sign (<code class="literal">=</code>), you specify that only syslog messages with that priority will be selected. All other priorities will be ignored. Conversely, preceding a priority with an exclamation mark (<code class="literal">!</code>) selects all syslog messages but those with the defined priority. By not using either of these two extensions, you specify a selection of syslog messages with the defined or higher 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 dot). Specifying the keyword <code class="literal">none</code> serves for facilities with no given priorities.
+ </div><div class="para">
+ To define multiple facilities and priorities, simply separate them with a comma (<code class="literal">,</code>). To define multiple filters on one line, separate them with a semi-colon (<code class="literal">;</code>).
+ </div><div class="para">
+ 以下は、ファシリティとプライオリティによる簡単なフィルターのいくつかの例です:
+ </div><pre class="screen">
+kern.* # すべてのプライオリティを持つすべての kernel syslog メッセージを選択します
+</pre><pre class="screen">
+mail.crit # プライオリティ <code class="command">crit</code> 以上を持つすべての mail syslog メッセージを選択します。
+</pre><pre class="screen">
+cron.!info,!debug # Selects all cron syslog messages except those with the <code class="command">info</code> or <code class="command">debug</code> priority.
+</pre></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, refer to <a class="xref" href="#s4-properties">「プロパティ」</a>. Each of the properties specified in the filters lets you compare it to a specific value using one of the compare-operations listed in <a class="xref" href="#table-compare-operations">表18.1「プロパティによる比較演算」</a>.
+ </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.
+ </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.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>startswith</code></em>
+ </td><td class="">
+ Checks whether the provided string matches a prefix of the text provided by the property.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>regex</code></em>
+ </td><td class="">
+ Compares the provided POSIX BRE (Basic Regular Expression) 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></tbody></table></div></div><br class="table-break" /><div class="para">
+ プロパティによるフィルターを定義するには、以下の構文を使用します:
+ </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 (for example, <em class="parameter"><code>timegenerated</code></em>, <em class="parameter"><code>hostname</code></em>, etc.).
+ </div></li><li class="listitem"><div class="para">
+ The optional exclamation point (<code class="literal">!</code>) negates the output of the compare-operation (if prefixing the compare-operation).
+ </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. To escape certain character (for example a quotation mark (<code class="literal">"</code>)), use the backslash character (<code class="literal">\</code>).
+ </div></li></ul></div><div class="para">
+ 以下は、プロパティによるフィルターのいくつかの例です:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 以下のフィルターは、メッセージテキストに文字列 <code class="literal">error</code> を含む syslog メッセージを選択します:
+ </div><pre class="screen">:msg, contains, "error"</pre></li><li class="listitem"><div class="para">
+ 以下のフィルターは、ホスト名 <code class="literal">host1</code> から受信した syslog メッセージを選択します:
+ </div><pre class="screen">:hostname, isequal, "host1"</pre></li><li class="listitem"><div class="para">
+ The following filter selects 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>):
+ </div><pre class="screen">:msg, !regex, "fatal .* error"</pre></li></ul></div></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. The syntax of this language is defined in <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/rscript_abnf.html</code> along with examples of various expression-based filters.
+ </div><div class="para">
+ 表現によるフィルターを定義するには、以下の構文を使用します:
+ </div><pre class="screen">if <em class="replaceable"><code><EXPRESSION></code></em> then <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>.
+ </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>.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Define an expression-based filter on a single line</h2></div><div class="admonition"><div class="para">
+ When defining an expression-based filter, it must be defined on a single line.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>正規表現を使用しないでください</h2></div><div class="admonition"><div class="para">
+ 正規表現は今のところ表現によるフィルターにおいてサポートされていません。
+ </div></div></div></dd><dt class="varlistentry"><span class="term">BSD 形式のブロック</span></dt><dd><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> supports BSD-style blocks inside the <code class="filename">/etc/rsyslog.conf</code> configuration file. Each block consists of rules which are preceded with a program or hostname label. Use the '!<em class="replaceable"><code><PROGRAM></code></em>' or '-<em class="replaceable"><code><PROGRAM></code></em>' labels to include or exclude programs, respectively. Use the '+<em class="replaceable"><code><HOSTNAME></code></em> ' or '-<em class="replaceable"><code><HOSTNAME></code></em> ' labels include or exclude hostnames, respectively.
+ </div><div class="para">
+ <a class="xref" href="#example-bsd-block1">例18.1「BSD 形式のブロック」</a> shows a BSD-style block that saves all messages generated by <span class="application"><strong>yum</strong></span> to a file.
+ </div><div class="example" id="example-bsd-block1"><h6>例18.1 BSD 形式のブロック</h6><div class="example-contents"><pre class="screen">
+!yum
+*.* /var/log/named.log
+</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s3-actions"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">18.1.3.2. アクション</h4></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. The following is a rule 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="screen">cron.* /var/log/cron.log
+</pre><div class="para">
+ Use a dash mark (<code class="literal">-</code>) as a prefix of the file path you specified if you want to omit syncing the desired log file after every syslog message is generated.
+ </div><div class="para">
+ Your specified file path can be either static or dynamic. Static files are represented by a simple file path as was shown in the example above. Dynamic files are represented by a template and a question mark (<code class="literal">?</code>) prefix. For more information on templates, refer to <a class="xref" href="#s4-generating-dynamic-fnames">「動的なファイル名の収集」</a>.
+ </div><div class="para">
+ If the file you specified is an existing <span class="application"><strong>tty</strong></span> or <code class="filename">/dev/console</code> device, syslog messages are sent to standard output (using special <span class="application"><strong>tty</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 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">(<em class="replaceable"><code><OPTION></code></em>)</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 <em class="replaceable"><code><OPTION></code></em> attribute can be replaced with an option such as <code class="command">z<em class="replaceable"><code><NUMBER></code></em> </code>. This option 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. To define multiple options, simply separate each one of them with a comma (<code class="literal">,</code>).
+ </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="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):
+ </div><pre class="screen">*.* @192.168.0.1 # <code class="systemitem">UDP</code> プロトコル経由で 192.168.0.1 にメッセージを転送します</pre><pre class="screen">*.* @@example.com:18 # ポート 18 の <code class="systemitem">TCP</code> プロトコルを使用して "example.com" にメッセージを転送します</pre><pre class="screen">
+*.* @(z9)[2001::1] # Compresses messages with <span class="application"><strong>zlib</strong></span> (level 9 compression)
+ # and forwards them to 2001::1 using the <code class="systemitem">UDP</code> protocol</pre></dd><dt class="varlistentry"><span class="term">出力チャネル</span></dt><dd><div class="para">
+ Output channels are primarily used for log file rotation (for more info on log file rotation, refer to <a class="xref" href="#configuring-logrotate">「logrotate の設定法」</a>), that is, to specify the maximum size a log file can grow to. To define an output channel, 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.
+ </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">
+ <a class="xref" href="#example-log-rotation">例18.2「Output channel log rotation」</a> 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 and then used in a rule which selects every syslog message with any priority and executes the previously-defined output channel on the acquired syslog messages. 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 class="example" id="example-log-rotation"><h6>例18.2 Output channel log rotation</h6><div class="example-contents"><pre class="screen">
+$outchannel log_rotation,/var/log/test_log.log, 104857600, /home/joe/log_rotation_script
+
+*.* $log_rotation
+</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Support for output channels is to be removed in the future</h2></div><div class="admonition"><div class="para">
+ Output channels are currently supported by <span class="application"><strong>rsyslog</strong></span>, however, they are planned to be removed in the nearby future.
+ </div></div></div></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 simply specifying a username of the user you wish to send the messages to. To specify more than one user, separate each username 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, refer to <a class="xref" href="#s3-templates">「テンプレート」</a>). 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 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 specified by the attacker in the program you specified (in your action) to be executed. 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">Inputting 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">
+ <em class="replaceable"><code><DB_HOST></code></em> 属性はデータベースのホスト名を指定します。
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code><DB_NAME></code></em> 属性はデータベースの名前を指定します。
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code><DB_USER></code></em> 属性はデータベースのユーザーを指定します。
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code><DB_PASSWORD></code></em> 属性は前述のデータベースのユーザーに使用するパスワードを指定します。
+ </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, refer to <a class="xref" href="#s3-templates">「テンプレート」</a>.
+ </div></li></ul></div><div class="important"><div class="admonition_header"><h2>MySQL および PostgreSQL の使用法</h2></div><div class="admonition"><div class="para">
+
+ </div><pre class="screen">
+$ModLoad ommysql # MySQL サポートの出力モジュール
+$ModLoad ompgsql # PostgreSQL サポートの出力モジュール
+</pre><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> モジュールの詳細は <a class="xref" href="#s2-modules">「モジュール」</a> を参照してください。
+ </div><div class="para">
+ Alternatively, you may use a generic database interface provided by the <code class="systemitem">omlibdb</code> module. However, this module is currently not compiled.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">syslog メッセージの破棄</span></dt><dd><div class="para">
+ 選択されたメッセージを破棄するには、チルダ記号 (<code class="literal">~</code>) を使用します。以下のルールはすべての cron syslog メッセージを破棄します:
+ </div><pre class="screen">cron.* ~</pre></dd></dl></div><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 (&). Only the first action is allowed to have a selector specified on its line. The following is an example of a rule with multiple actions:
+ </div><pre class="screen">
+kern.=crit joe
+& ^test-program;temp
+& @192.168.0.1
+</pre><div class="para">
+ In the example above, all kernel syslog messages with the critical priority (<em class="parameter"><code>crit</code></em>) are send to user <code class="systemitem">joe</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><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="para">
+ Note that 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.
+ </div><div class="warning"><div class="admonition_header"><h2>テンプレートの使用法</h2></div><div class="admonition"><div class="para">
+ テンプレートはアクションにおいて使用する前に定義されている必要があります。そうでなければ、無視されます。
+ </div></div></div><div class="para">
+ テンプレートの詳細は <a class="xref" href="#s3-templates">「テンプレート」</a> を参照してください。
+ </div></div><div class="section" id="s3-templates"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">18.1.3.3. テンプレート</h4></div></div></div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> により生成されたすべての出力は、テンプレートの使用を通して、必要に応じて変更および整形できます。テンプレートを作成するには、以下の構文を使用します:
+ </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> はテンプレートの名前です。テンプレートを参照するには、この名前を使用します。
+ </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, you are allowed to escape characters in order to use their functionality, such as <code class="literal">\n</code> for new line or <code class="literal">\r</code> for carriage return. Other characters, such as <code class="literal">%</code> or <code class="literal">"</code>, have to be escaped in case you want to those characters literally.
+ </div><div class="para">
+ The text specified within two percent signs (<code class="literal">%</code>) specifies a <em class="firstterm">property</em> that is consequently replaced with the property's actual value. For more information on properties, refer to <a class="xref" href="#s4-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. Do not mistake these for property options, which are defined inside the template text (between <code class="literal">"</code>…<code class="literal">"</code>). The currently supported template options are <em class="parameter"><code>sql</code></em> and <em class="parameter"><code>stdsql</code></em> 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 (for more information, refer to section <em class="citetitle">Inputting syslog messages in a database</em> in <a class="xref" href="#s3-actions">「アクション」</a>) checks whether the <em class="parameter"><code>sql</code></em> and <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></div></li></ul></div><div class="section" id="s4-generating-dynamic-fnames"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">18.1.3.3.1. 動的なファイル名の収集</h5></div></div></div><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. For example, use the <em class="parameter"><code>timegenerated</code></em> property 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:
+ </div><pre class="screen">*.* ?DynamicFile</pre></div><div class="section" id="s4-properties"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">18.1.3.3.2. プロパティ</h5></div></div></div><div class="para">
+ Properties defined inside a template (within two percent signs (<code class="literal">%</code>)) allow you to 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 comprehensible list of all available properties and their detailed description can be found in <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/property_replacer.html</code> 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, specify 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. A comprehensible list of all available properties and their detailed description can be found in <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/property_replacer.html</code> 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">
+ 以下のプロパティは単に syslog メッセージのテキスト全体を取得します:
+ </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 timestamp that is generated when the syslog message is received and formats it according to the RFC 3999 date standard.
+ </div><pre class="screen">%timegenerated:1:10:date-rfc3339%</pre></li></ul></div></div><div class="section" id="s4-template-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">18.1.3.3.3. テンプレート例</h5></div></div></div><div class="para">
+ このセクションは <span class="application"><strong>rsyslog</strong></span> のテンプレートの例をいくつか説明します。
+ </div><div class="para">
+ <a class="xref" href="#example-temp1">例18.3「冗長な syslog メッセージのテンプレート」</a> shows a template that formats a syslog message so that it outputs the message's severity, facility, the timestamp of when the message was received, the hostname, the message tag, the message text, and ends with a new line.
+ </div><div class="example" id="example-temp1"><h6>例18.3 冗長な syslog メッセージのテンプレート</h6><div class="example-contents"><pre class="screen">$template verbose,"%syslogseverity%,%syslogfacility%,%timegenerated%,%HOSTNAME%,%syslogtag%,%msg%
+"</pre></div></div><br class="example-break" /><div class="para">
+ <a class="xref" href="#example-temp2">例18.4「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 hostname, message tag and a timestamp, 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.4 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.5「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.5 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. It is advisable to not create a template using this prefix to avoid any 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><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><pre class="screen">"<%PRI%>1 %TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA% %msg%
+\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_FileFormat</code></em></span></dt><dd><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><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><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><pre class="screen">"<%PRI%>%TIMESTAMP% %HOSTNAME% %syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd></dl></div></div></div></div><div class="section" id="s2-rsyslog-cmd-options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.4. <span class="application"><strong>rsyslog</strong></span> コマンドライン設定</h3></div></div></div><div class="para">
+ Some of <span class="application"><strong>rsyslog</strong></span>'s functionality can be configured through the command line options, as <span class="application"><strong>sysklogd</strong></span>'s can. Note that as of version 3 of <span class="application"><strong>rsyslog</strong></span>, this method was deprecated. To enable some of these option, you must specify the compatibility mode <span class="application"><strong>rsyslog</strong></span> should run in. However, configuring <span class="application"><strong>rsyslog</strong></span> through the command line options should be avoided.
+ </div><div class="para">
+ To specify the compatibility mode <span class="application"><strong>rsyslog</strong></span> should run in, use the <code class="option">-c</code> option. When no parameter is specified, <span class="application"><strong>rsyslog</strong></span> tries to be compatible with <span class="application"><strong>sysklogd</strong></span>. This is partially achieved by activating configuration directives that modify your configuration accordingly. Therefore, it is advisable to supply this option with a number that matches the major version of <span class="application"><strong>rsyslog</strong></span> that is in use and update your <code class="filename">/etc/rsyslog.conf</code> configuration file accordingly. If you want to, for example, use <span class="application"><strong>sysklogd</strong></span> options (which were deprecated in version 3 of <span class="application"><strong>rsyslog</strong></span>), you can specify so by executing the following command:
+ </div><pre class="screen">~]# rsyslogd -c 2</pre><div class="para">
+ Options that are passed to the <code class="systemitem">rsyslogd</code> daemon, including the backward compatibility mode, can be specified in the <code class="filename">/etc/sysconfig/rsyslog</code> configuration file.
+ </div><div class="para">
+ さまざまな <code class="command">rsyslogd</code> オプションの詳細は <code class="command">man rsyslogd</code> を参照してください。
+ </div></div></div><div class="section" id="s1-logfiles-locating"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.2. ログファイルを探す</h2></div></div></div><a id="idm95089232" 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="idm124467952" class="indexterm"></a><a id="idm115677712" 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 timestamp 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 class="section" id="configuring-logrotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.2.1. logrotate の設定法</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 the duration of 4 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 on a weekly basis. 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 just-rotated log files are to be mailed, instead of the about-to-expire 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, refer to the <code class="command">logrotate</code> man page (<code class="command">man logrotate</code>).
+ </div></div></div><div class="section" id="s1-logfiles-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.3. ログファイルの表示</h2></div></div></div><a id="idm120278864" class="indexterm"></a><div class="para">
+ Most log files are 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, <code class="systemitem">root</code> privileges are required to read most log files.
+ </div><a id="idm101951456" class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span class="application"><strong>Log File Viewer</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>Log File Viewer</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">yum install gnome-system-log</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は <a class="xref" href="#sec-Installing">「パッケージのインストール」</a> を参照してください。
+ </div></div></div><div class="para">
+ After you have installed the <span class="package">gnome-system-log</span> package, you can open the <span class="application"><strong>Log File Viewer</strong></span> by selecting <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Log File Viewer</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, 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.1「ログファイルビューアー」</a>.
+ </div><a id="idm140003680" class="indexterm"></a><a id="idm81318032" class="indexterm"></a><div class="figure" id="fig-redhat-logviewer"><div class="figure-contents"><div class="mediaobject"><img src="images/system-log-viewer.png" alt="ログファイルビューアー" /><div class="longdesc"><div class="para">
+ ログファイルビューアー
+ </div></div></div></div><h6>図18.1 ログファイルビューアー</h6></div><br class="figure-break" /><a id="idm133495392" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Log File Viewer</strong></span> application lets you filter any existing log file. Click on <span class="guimenuitem"><strong>Filters</strong></span> from the menu and select <span class="guimenuitem"><strong>Manage Filters</strong></span> to define or edit your desired filter.
+ </div><div class="figure" id="fig-redhat-filters"><div class="figure-contents"><div class="mediaobject"><img src="images/system-log-viewer-filters-manage.png" alt="ログファイルビューアー — フィルター" /><div class="longdesc"><div class="para">
+ ログファイルビューアー — フィルター
+ </div></div></div></div><h6>図18.2 ログファイルビューアー — フィルター</h6></div><br class="figure-break" /><div class="para">
+ フィルターを追加または編集することにより、<a class="xref" href="#fig-redhat-filter-sample">図18.3「ログファイルビューアー — フィルターの定義」</a>に示されたとおり、そのパラメーターを定義できます。
+ </div><div class="figure" id="fig-redhat-filter-sample"><div class="figure-contents"><div class="mediaobject"><img src="images/system-log-viewer-filters-define.png" alt="ログファイルビューアー — フィルターの定義" /><div class="longdesc"><div class="para">
+ ログファイルビューアー — フィルターの定義
+ </div></div></div></div><h6>図18.3 ログファイルビューアー — フィルターの定義</h6></div><br class="figure-break" /><div class="para">
+ フィルターを定義するとき、以下のパラメーターを編集できます:
+ </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, you may select it 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/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/system-log-viewer-filters-enable.png" alt="Log File Viewer — enabling a filter" /><div class="longdesc"><div class="para">
+ Log File Viewer — enabling a filter
+ </div></div></div></div><h6>図18.4 Log File Viewer — enabling a filter </h6></div><br class="figure-break" /><div class="para">
+ When you check 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="s1-logfiles-adding"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.4. ログファイルの追加</h2></div></div></div><div class="para">
+ To add a log file you wish 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 wish to view.<a class="xref" href="#fig-redhat-logviewer-add">図18.5「Log File Viewer — 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/system-log-viewer-add.png" alt="Log File Viewer — adding a log file" /><div class="longdesc"><div class="para">
+ Log File Viewer — adding a log file
+ </div></div></div></div><h6>図18.5 Log File Viewer — 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>Log File Viewer</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="s1-logfiles-examining"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.5. ログファイルを監視する</h2></div></div></div><a id="idm114322608" class="indexterm"></a><a id="idm95155888" class="indexterm"></a><div class="para">
+ <span class="application"><strong>Log File Viewer</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.6「Log File Viewer — new log alert」</a> illustrates a new alert in the <span class="guilabel"><strong>yum.log</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/system-log-viewer-alerts.png" alt="Log File Viewer — new log alert" /><div class="longdesc"><div class="para">
+ Log File Viewer — new log alert
+ </div></div></div></div><h6>図18.6 Log File Viewer — new log alert</h6></div><br class="figure-break" /></div><div class="section" id="s1-log-files-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.6. その他のリソース</h2></div></div></div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span>, <span class="application"><strong>logrotate</strong></span> および一般的なログファイルに関する詳細を知るには、以下のリソースを参照してください。
+ </div><div class="section" id="s2-log-files-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.6.1. インストールされているドキュメント</h3></div></div></div><a id="idm112568128" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rsyslogd</code> manual page — <code class="command">rsyslogd</code> およびその多くのオプションに関する詳細を知るには <code class="command">man rsyslogd</code> を入力してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">rsyslog.conf</code> manual page — <code class="command">/etc/rsyslog.conf</code> 設定ファイルおよびその多くのオプションに関する詳細を知るには <code class="command">man rsyslog.conf</code> と入力してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/ </code> — <span class="package">rsyslog</span> パッケージのインストール後、このディレクトリーに <code class="systemitem">html</code> 形式の広範囲なドキュメントがあります。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">logrotate</code> マニュアルページ — <code class="command">logrotate</code> および多くのオプションに関する詳細を知るには <code class="command">man logrotate</code> と入力してください。
+ </div></li></ul></div></div><div class="section" id="s2-log-files-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.6.2. 役に立つ Web サイト</h3></div></div></div><a id="idm108760176" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/">http://www.rsyslog.com/</a> — <span class="package">rsyslog</span> の機能、ドキュメント、設定例、およびビデオチュートリアルの包括的な技術詳細を提供します。
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://wiki.rsyslog.com/index.php/Main_Page">http://wiki.rsyslog.com/index.php/Main_Page</a> — 有用な <code class="filename">/etc/rsyslog.conf</code> 設定例があります。
+ </div></li></ul></div></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><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="#s2-autotasks-cron-service">19.1.1. サービスの起動と停止</a></span></dt><dt><span class="section"><a href="#s2-configuring-anacron-jobs">19.1.2. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="#s2-configuring-cron-jobs">19.1.3. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">19.1.4. Cron へのアクセスの制御</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-cron-jobs">19.1.5. Black/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="#s2-autotasks-at-configuring">19.2.1. At ジョブの設定</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">19.2.2. batch ジョブの設定</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">19.2.3. 保留ジョブの表示</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">19.2.4. その他のコマンドラインオプション</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">19.2.5. at と batch へのアクセスの制御</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-service">19.2.6. サービスの起動と停止</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">19.3. その他のリソース</a></span></dt><dd><
dl><dt><span class="section"><a href="#s2-autotasks-installed-docs">19.3.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a id="idm71475632" class="indexterm"></a><div class="para">
+ In Linux, tasks, which are 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 is below a specified number. Fedora is pre-configured to run important system tasks to keep the system updated. For example, the slocate 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 more.
+ </div><div class="para">
+ Fedora comes with several automated tasks utilities: <code class="command">cron</code>, <code class="command">at</code>, and <code class="command">batch</code>.
+ </div><a id="idm110026800" class="indexterm"></a><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="idm128028544" class="indexterm"></a><a id="idm134238784" class="indexterm"></a><div class="para">
+ Both, Cron and Anacron, are daemons that can be used to schedule the execution of recurring tasks according to a combination of the time, day of the month, month, day of the week, and week.
+ </div><div class="para">
+ Cron assumes that the system is on continuously. If the system is not on when a job is scheduled, it is not executed. Cron allows jobs to be run as often as every minute. Anacron does not assume the system is always on, remembers every scheduled job, and executes it the next time the system is up. However, Anacron can only run a job once a day. To schedule recurring jobs, refer to <a class="xref" href="#s2-configuring-anacron-jobs">「Configuring Anacron Jobs」</a> or <a class="xref" href="#s2-configuring-cron-jobs">「Configuring Cron Jobs」</a>. To schedule one-time jobs, refer to <a class="xref" href="#s1-autotasks-at-batch">「at コマンドと batch コマンド」</a>.
+ </div><div class="para">
+ To use the cron service, the <code class="filename">cronie</code> RPM package must be installed and the <code class="command">crond</code> service must be running. <code class="filename">anacron</code> is a sub-package of <code class="filename">cronie</code>. To determine if these packages are installed, use the <code class="command">rpm -q cronie cronie-anacron</code> command.
+ </div><div class="section" id="s2-autotasks-cron-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.1.1. サービスの起動と停止</h3></div></div></div><div class="para">
+ To determine if the service is running, use the following command:
+ </div><pre class="screen"><code class="command">systemctl is-active crond.service</code></pre><div class="para">
+ To start the cron service, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl start crond.service</code></pre><div class="para">
+ To stop the service, run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl stop crond.service</code></pre><div class="para">
+ It is recommended that you start the service at boot time. To do so, use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl enable crond.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </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.2. Configuring Anacron Jobs</h3></div></div></div><a id="idm91169440" class="indexterm"></a><a id="idm112320672" class="indexterm"></a><a id="idm112319040" class="indexterm"></a><a id="idm138443072" class="indexterm"></a><div class="para">
+ The main configuration file to schedule jobs is <code class="filename">/etc/anacrontab</code> (only <code class="systemitem">root</code> is allowed to modify this file), which contains the following lines:
+ </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
+ at monthly 45 cron.monthly nice run-parts /etc/cron.monthly</pre><div class="para">
+ The first three lines are variables used to configure the environment in which the anacron tasks are run. The <code class="computeroutput">SHELL</code> variable tells the system which shell environment to use (in this example the bash shell). The <code class="computeroutput">PATH</code> variable defines the path used to execute commands. The output of the anacron jobs are emailed to the username defined with the <code class="computeroutput">MAILTO</code> variable. If the <code class="computeroutput">MAILTO</code> variable is not defined, (i.e. is empty, <code class="computeroutput">MAILTO=</code>), email is not sent.
+ </div><div class="para">
+ The next two lines are variables that modify the time for each scheduled job. The <code class="computeroutput">RANDOM_DELAY</code> variable denotes the maximum number of minutes that will be added to the <code class="filename">delay in minutes</code> variable which is specified for each job. The minimum delay value is set, by default, to 6 minutes. A <code class="computeroutput">RANDOM_DELAY</code> set to 12 would therefore add, randomly, between 6 and 12 minutes to the <code class="filename">delay in minutes</code> for each job in that particular anacrontab. <code class="computeroutput">RANDOM_DELAY</code> can also be set to a value below 6, or even 0. When set to 0, 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. The <code class="computeroutput">START_HOURS_RANGE</code> variable defines an interval (in hours) when scheduled jobs can be run. In case this time
interval is missed, for example, due to a power down, then scheduled jobs are not executed that day.
+ </div><div class="para">
+ The rest of the lines in the <code class="filename">/etc/anacrontab</code> file represent scheduled jobs and have the following format:
+ </div><pre class="programlisting">period in days delay in minutes job-identifier command</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">period in days</code> — specifies the frequency of execution of a job in days. This variable can be represented by an integer or a macro (<code class="computeroutput">@daily</code>, <code class="computeroutput">@weekly</code>, <code class="computeroutput">@monthly</code>), where <code class="computeroutput">@daily</code> denotes the same value as the integer 1, <code class="computeroutput">@weekly</code> the same as 7, and <code class="computeroutput">@monthly</code> specifies that the job is run once a month, independent on the length of the month.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">delay in minutes</code> — specifies the number of minutes anacron waits, if necessary, before executing a job. This variable is represented by an integer where 0 means no delay.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">job-identifier</code> — specifies a unique name of a job which is used in the log files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">command</code> — specifies the command to execute. The command can either be a command such as <code class="computeroutput">ls /proc >> /tmp/proc</code> or a command to execute 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.2.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
+ at 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. Thus, the first defined job will run anywhere between 16:26 and 16:50 every day. The command specified for this job will execute all present programs in the <code class="filename">/etc/cron.daily</code> directory (using the <code class="command">run-parts</code> script which takes a directory as a command-line argument and sequentially executes every program within that directory). The second specified job will be executed once a week and will execute the <code class="filename">weeklyjob.bash</code> script in the <code class="filename">/etc</code> directory. The third job is executed once a month and runs a command to write the contents of the <code class="filename">/proc</code> to the <code class="filename">/tmp/proc</code> file (e.g. <code class="computeroutput">ls /proc >> /tmp/proc</code>).
+ </div><div class="section" id="s3-disabling-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">19.1.2.1.1. Disabling Anacron</h5></div></div></div><div class="para">
+ In case your system is continuously on and you do not require anacron to run your scheduled jobs, you may uninstall the <code class="filename">cronie-anacron</code> package. Thus, you will be able to define jobs using crontabs only.
+ </div></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.3. Configuring Cron Jobs</h3></div></div></div><a id="idm105668400" class="indexterm"></a><a id="idm134138704" class="indexterm"></a><a id="idm134137072" class="indexterm"></a><a id="idm18497520" class="indexterm"></a><div class="para">
+ The configuration file to configure cron jobs, <code class="filename">/etc/crontab</code> (only <code class="systemitem">root</code> is allowed to modify this file), contains the following lines:
+ </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 command to be executed</pre><div class="para">
+ The first three lines contain the same variables as an <code class="filename">anacrontab</code> file, <code class="computeroutput">SHELL</code>, <code class="computeroutput">PATH</code> and <code class="computeroutput">MAILTO</code>. For more information about these variables, refer to <a class="xref" href="#s2-configuring-anacron-jobs">「Configuring Anacron Jobs」</a>. The fourth line contains the <code class="computeroutput">HOME</code> variable. The <code class="computeroutput">HOME</code> variable can be used to set the home directory to use when executing commands or scripts.
+ </div><div class="para">
+ The rest of the lines in the <code class="filename">/etc/crontab</code> file represent scheduled jobs and have the following format:
+ </div><pre class="programlisting">minute hour day month day of week user command</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">minute</code> — any integer from 0 to 59
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">hour</code> — any integer from 0 to 23
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">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="computeroutput">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="computeroutput">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><li class="listitem"><div class="para">
+ <code class="computeroutput">user</code> — specifies the user under which the jobs are run
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">command</code> — the command to execute (the command can either be a command such as <code class="command">ls /proc >> /tmp/proc</code> or the command to execute a custom script)
+ </div></li></ul></div><div class="para">
+ 上記のいずれの値にも、アスタリスク （*） を使用すると、すべての有効な値が指定されます。たとえば、月の値にアスタリスクを使用すると、コマンドはその他の値による制約の範囲内で毎月実行されます。
+ </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 those four specific integers.
+ </div><div class="para">
+ The forward slash (/) can be used to specify step values. The value of an integer can be skipped within a range by following the range with <strong class="userinput"><code>/<em class="replaceable"><code>integer</code></em></code></strong>. For example, <strong class="userinput"><code>0-59/2</code></strong> can be used to define every other minute in the minute field. Step values can also be used with an asterisk. For instance, the value <strong class="userinput"><code>*/3</code></strong> can be used in the month field to run the task 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 by using the <code class="command">crontab</code> utility. All user-defined crontabs are stored in the <code class="filename">/var/spool/cron/</code> directory and are executed using the usernames of the users that created them. To create a crontab as a user, login as that user and type the command <code class="command">crontab -e</code> to edit the user's crontab using the editor specified by 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 username and written to the file <code class="filename">/var/spool/cron/<em class="replaceable"><code>username</code></em> </code>. To list the contents of your own personal crontab file, use the <code class="command">crontab -l</code> com
mand.
+ </div><div class="note"><div class="admonition_header"><h2>Do not specify a user</h2></div><div class="admonition"><div class="para">
+ When using the <code class="command">crontab</code> utility, there is no need to specify a user when defining a job.
+ </div></div></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 any changes. If any changes are found, they are loaded into memory. Thus, the daemon does not need to be restarted if an anacrontab or a crontab file is 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.4. Cron へのアクセスの制御</h3></div></div></div><div class="para">
+ The <code class="filename">/etc/cron.allow</code> and <code class="filename">/etc/cron.deny</code> files are used to restrict access to cron. The format of both access control files is one username on each line. Whitespace is not permitted in either file. The cron daemon (<code class="command">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 usernames listed in the access control files.
+ </div><div class="para">
+ If the file <code class="filename">cron.allow</code> exists, only users listed in it are allowed to use cron, and the <code class="filename">cron.deny</code> file is ignored.
+ </div><div class="para">
+ If <code class="filename">cron.allow</code> does not exist, users listed in <code class="filename">cron.deny</code> are not allowed to use cron.
+ </div><div class="para">
+ Access can also be controlled through Pluggable Authentication Modules (PAM). These settings are stored in <code class="filename">/etc/security/access.conf</code>. For example, adding the following line in this file forbids creating crontabs for all users except the <code class="systemitem">root</code> user:
+ </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 “crontab -e”, returned to the standard output. For more information, refer to <code class="filename">access.conf.5</code> (i.e. <code class="command">man 5 access.conf</code>).
+ </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.5. Black/White Listing of Cron Jobs</h3></div></div></div><div class="para">
+ Black/White listing of jobs is used to omit parts of the defined jobs that do not need to be executed. When calling the <code class="command">run-parts</code> script on a cron folder, such as <code class="filename">/etc/cron.daily</code>, we can define which of the programs in this folder will not be executed by <code class="command">run-parts</code>.
+ </div><div class="para">
+ To define a black list, create a <code class="filename">jobs.deny</code> file in the folder that <code class="command">run-parts</code> will be executing from. For example, if we need to omit a particular program from /etc/cron.daily, then, a file <code class="filename">/etc/cron.daily/jobs.deny</code> has to be created. In this file, specify the names of the omitted programs from the same directory. These will not be executed when a command, such as <code class="computeroutput">run-parts /etc/cron.daily</code>, is executed by a specific job.
+ </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="idm132708880" class="indexterm"></a><a id="idm107385696" class="indexterm"></a><div class="para">
+ While cron is used to schedule recurring tasks, the <code class="command">at</code> command is used to schedule a one-time task at a specific time and the <code class="command">batch</code> command is used to schedule a one-time task to be executed when the systems load average drops below 0.8.
+ </div><div class="para">
+ To use <code class="command">at</code> or <code class="command">batch</code>, the <code class="filename">at</code> RPM package must be installed, and the <code class="command">atd</code> service must be running. To determine if the package is installed, use the <code class="command">rpm -q at</code> command. To determine if the service is running, use the following command:
+ </div><pre class="screen"><code class="command">systemctl is-active atd.service</code></pre><div class="section" id="s2-autotasks-at-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.1. At ジョブの設定</h3></div></div></div><div class="para">
+ To schedule a one-time job at a specific time, 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 to execute the command.
+ </div><div class="para">
+ 引数 <em class="replaceable"><code>time</code></em> は次のいずれかを指定できます。
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ HH:MM format — For example, 04:00 specifies 4:00 a.m. If the time is already past, it is executed at the specified time the next day.
+ </div></li><li class="listitem"><div class="para">
+ midnight — 12:00 a.m. を指定します
+ </div></li><li class="listitem"><div class="para">
+ noon — 12:00 p.m. を指定します
+ </div></li><li class="listitem"><div class="para">
+ teatime — 4:00 p.m. を指定します
+ </div></li><li class="listitem"><div class="para">
+ month-name day year 形式 — たとえば、January 15 2002 は 2002 年 1 月 15 日を指定します。年はオプションです。
+ </div></li><li class="listitem"><div class="para">
+ MMDDYY, MM/DD/YY, または MM.DD.YY 形式 — たとえば、2002 年の 1 月 15 日は 011502 です。
+ </div></li><li class="listitem"><div class="para">
+ now + time — time is in minutes, hours, days, or weeks. For example, now + 5 days specifies that the command should be executed at the same time five days from now.
+ </div></li></ul></div><div class="para">
+ The time must be specified first, followed by the optional date. For more information about the time format, read the <code class="filename">/usr/share/doc/at-<em class="replaceable"><code>version</code></em>/timespec</code> text file.
+ </div><div class="para">
+ After typing the <code class="command">at</code> command with the time argument, the <code class="prompt">at></code> prompt is displayed. Type the command to execute, press <span class="keycap"><strong>Enter</strong></span>, and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Multiple commands can be specified by typing each command followed by the <span class="keycap"><strong>Enter</strong></span> key. After typing all the commands, press <span class="keycap"><strong>Enter</strong></span> to go to a blank line and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Alternatively, a shell script can be entered at the prompt, pressing <span class="keycap"><strong>Enter</strong></span> after each line in the script, and pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script i
s entered, the shell used is 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><div class="para">
+ If the set of commands or script tries to display information to standard output, the output is emailed to the user.
+ </div><div class="para">
+ Use the command <code class="command">atq</code> to view pending jobs. Refer to <a class="xref" href="#s2-autotasks-at-batch-viewing">「保留ジョブの表示」</a> for more information.
+ </div><div class="para">
+ Usage of the <code class="command">at</code> command can be restricted. For more information, refer to <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.2. batch ジョブの設定</h3></div></div></div><div class="para">
+ To execute a one-time task when the load average is below 0.8, use the <code class="command">batch</code> command.
+ </div><div class="para">
+ After typing the <code class="command">batch</code> command, the <code class="prompt">at></code> prompt is displayed. Type the command to execute, press <span class="keycap"><strong>Enter</strong></span>, and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Multiple commands can be specified by typing each command followed by the <span class="keycap"><strong>Enter</strong></span> key. After typing all the commands, press <span class="keycap"><strong>Enter</strong></span> to go to a blank line and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Alternatively, a shell script can be entered at the prompt, pressing <span class="keycap"><strong>Enter</strong></span> after each line in the script, and pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script is entered, the shell
used is 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). As soon as the load average is below 0.8, the set of commands or script is executed.
+ </div><div class="para">
+ 標準出力に情報を表示するコマンドやスクリプトを入力した場合、この出力はユーザーに電子メールで送信されます。
+ </div><div class="para">
+ Use the command <code class="command">atq</code> to view pending jobs. Refer to <a class="xref" href="#s2-autotasks-at-batch-viewing">「保留ジョブの表示」</a> for more information.
+ </div><div class="para">
+ Usage of the <code class="command">batch</code> command can be restricted. For more information, refer to <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.3. 保留ジョブの表示</h3></div></div></div><div class="para">
+ To view pending <code class="command">at</code> and <code class="command">batch</code> jobs, use 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 line. Each line follows the job number, date, hour, job class, and username 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.4. その他のコマンドラインオプション</h3></div></div></div><div class="para">
+ Additional command line options for <code class="command">at</code> and <code class="command">batch</code> include:
+ </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.5. at と batch へのアクセスの制御</h3></div></div></div><div class="para">
+ The <code class="filename">/etc/at.allow</code> and <code class="filename">/etc/at.deny</code> files can be used to restrict access to the <code class="command">at</code> and <code class="command">batch</code> commands. The format of both access control files is one username on each line. Whitespace is not permitted in either file. 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 access control files.
+ </div><div class="para">
+ If the file <code class="filename">at.allow</code> exists, only users listed in it 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><div class="section" id="s2-autotasks-at-batch-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.6. サービスの起動と停止</h3></div></div></div><div class="para">
+ To start the <code class="command">at</code> service, use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl start atd.service</code></pre><div class="para">
+ To stop the service, as <code class="systemitem">root</code>, type the following at a shell prompt:
+ </div><pre class="screen"><code class="command">systemctl stop atd.service</code></pre><div class="para">
+ It is recommended that you start the service at boot time. To do so, run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl enable atd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </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="idm80172384" class="indexterm"></a><a id="idm111088144" class="indexterm"></a><a id="idm106802144" class="indexterm"></a><div class="para">
+ 自動化タスクに関する詳細は、次のリソースを参照してください。
+ </div><div class="section" id="s2-autotasks-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.3.1. インストールされているドキュメント</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">cron</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 — The man page in section 1 contains an overview of the <code class="filename">crontab</code> file. The man page in section 5 contains the format for the file and some example entries.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">anacron</code> man page — contains an overview of anacron.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">anacrontab</code> man page — contains an overview of the <code class="filename">anacrontab</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/at-<em class="replaceable"><code>version</code></em>/timespec</code> contains more detailed information about the times that can be specified for cron jobs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">at</code> man page — description of <code class="command">at</code> and <code class="command">batch</code> and their command line options.
+ </div></li></ul></div></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><dt><span class="section"><a href="#s1-oprofile-overview-tools">20.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="#s1-oprofile-configuring">20.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">20.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">20.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">20.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">20.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">20.4. Saving Data</a></span></d
t><dt><span class="section"><a href="#s1-oprofile-analyzing-data">20.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">20.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">20.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">20.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">20.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">20.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">20.7. 使用法の例</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">20.8. OProfile Support f
or Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">20.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">20.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-and-systemtap">20.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">20.11. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-installed-docs">20.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="#s2-oprofile-useful-websites">20.11.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></div><a id="idm89626000" class="indexterm"></a><a id="idm18525216" 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, essentially rolls over, 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">
+ OProfile is a useful tool, but be aware of some limitations when using it:
+ </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. Run 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="idm106218688" class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-oprofile-tools">表20.1「OProfile Commands」</a> provides a brief overview of the 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. Refer to <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. Refer to <a class="xref" href="#s1-oprofile-configuring">「Configuring OProfile」</a> for details.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">opreport</code>
+ </td><td class="">
+ <div class="para">
+ Retrieves profile data. Refer to <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><div class="section" id="s1-oprofile-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.2. Configuring OProfile</h2></div></div></div><a id="idm111485104" class="indexterm"></a><a id="idm111483472" class="indexterm"></a><a id="idm106428752" class="indexterm"></a><div class="para">
+ Before OProfile can be run, 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.2.1. Specifying the Kernel</h3></div></div></div><a id="idm108470928" 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 root:
+ </div><a id="idm123962096" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux</code></pre><div class="note"><div class="admonition_header"><h2>Install the debuginfo package</h2></div><div class="admonition"><div class="para">
+ The <span class="package">debuginfo</span> package for the kernel must be installed (which contains the uncompressed kernel) in order to monitor the kernel.
+ </div></div></div><div class="para">
+ To configure OProfile not to monitor the kernel, execute the following command as root:
+ </div><a id="idm114709616" 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. Refer to <a class="xref" href="#s1-oprofile-dev-oprofile">「Understanding <code class="filename">/dev/oprofile/</code> 」</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, refer to <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.2.2. Setting Events to Monitor</h3></div></div></div><a id="idm120428000" 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.2「OProfile Processors and Counters」</a>, the number of counters available depends on the processor.
+ </div><div class="table" id="tb-oprofile-processors"><h6>表20.2 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 Athlon
+ </td><td class="">
+ i386/athlon
+ </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="">
+ 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 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 Pentium 4 (non-hyper-threaded)
+ </td><td class="">
+ i386/p4
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Pentium 4 (hyper-threaded)
+ </td><td class="">
+ i386/p4-ht
+ </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="">
+ 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.2「OProfile Processors and Counters」</a> to verify that the correct processor type was detected and to determine the number of events that can be monitored simultaneously. <code class="computeroutput">timer</code> is used as the processor type if the processor does not have supported performance monitoring hardware.
+ </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 counter 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.3「Default Events」</a>.
+ </div><div class="table" id="tb-oprofile-default-events"><h6>表20.3 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="">
+ 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 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="">
+ 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="idm98073536" class="indexterm"></a><a id="idm85788240" class="indexterm"></a><pre class="screen">~]# <code class="command">ophelp</code></pre><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, refer to <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.2.2.1. Sampling Rate</h4></div></div></div><a id="idm99220576" 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 whatever the jiffy rate is 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 as if it is 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.2.2.2. Unit Masks</h4></div></div></div><a id="idm131039696" 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></div><div class="section" id="s2-oprofile-starting-separate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.3. Separating Kernel and User-space Profiles</h3></div></div></div><a id="idm89405232" 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>:<em class="replaceable"><code>kernel</code></em>: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>:<em class="replaceable"><code>kernel</code></em>: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">
+ <em class="replaceable"><code>choice</code></em> 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.3. Starting and Stopping OProfile</h2></div></div></div><a id="idm137847200" class="indexterm"></a><div class="para">
+ To start monitoring the system with OProfile, execute the following command as root:
+ </div><a id="idm137844896" 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="idm133002400" class="indexterm"></a><a id="idm99551072" class="indexterm"></a><a id="idm99548848" 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 17 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 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:
+ </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.4. Saving Data</h2></div></div></div><a id="idp1760112" 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 directory <code class="filename">/var/lib/oprofile/samples/<em class="replaceable"><code>name</code></em>/</code> is created and the current sample files are copied to it.
+ </div></div><div class="section" id="s1-oprofile-analyzing-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.5. Analyzing the Data</h2></div></div></div><a id="idm139544416" class="indexterm"></a><div class="para">
+ Periodically, the OProfile daemon, <code class="command">oprofiled</code>, 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. Please note that the sample file and the binary have to agree. Making a backup is not going to work if they do not match. <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. Refer to <a class="xref" href="#s1-oprofile-saving-data">「Saving Data」</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.5.1. Using <code class="command">opreport</code> </h3></div></div></div><a id="idm132446288" class="indexterm"></a><a id="idm132338336" class="indexterm"></a><div class="para">
+ The <code class="command">opreport</code> tool provides an overview of all the executables being profiled.
+ </div><div class="para">
+ The following is part of a sample output:
+ </div><pre class="screen">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">
+ Refer to the <code class="command">opreport</code> man 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.
+ </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.5.2. Using opreport on a Single Executable</h3></div></div></div><a id="idm82444272" class="indexterm"></a><a id="idm75167488" class="indexterm"></a><div class="para">
+ To retrieve more detailed profiled information about a specific executable, use <code class="command">opreport</code>:
+ </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">
+ <em class="replaceable"><code>executable</code></em> must be the full path to the executable to be analyzed. <em class="replaceable"><code>mode</code></em> must be one of the following:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">-l</code></span></dt><dd><div class="para">
+ List sample data by symbols. For example, the following is part of the output from running the command <code class="command">opreport -l /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ </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@@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, the following output is from the command <code class="command">opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ </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">
+ List sample data by symbols with more detail than <code class="option">-l</code>. For example, the following output is from the command <code class="command">opreport -l -d __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ </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">-x</code> <em class="replaceable"><code>symbol-name</code></em> </span></dt><dd><div class="para">
+ Exclude the comma-separated list of symbols from the output.
+ </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">
+ Specify the full path to the session or a directory relative to the <code class="filename">/var/lib/oprofile/samples/</code> directory.
+ </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.5.3. Getting more detailed output on the modules</h3></div></div></div><a id="idm91254144" class="indexterm"></a><a id="idm91251920" 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 have 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 sample 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 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.5.4. Using <code class="command">opannotate</code> </h3></div></div></div><a id="idp1602880" class="indexterm"></a><a id="idm18504112" 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 files generated 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. By default, Fedora <span class="package">debuginfo</span> packages are not installed together with their corresponding packages, which contain the executable, so that you have to obtain and install the <span class="package">debuginfo</span> packages 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">
+ The directory containing the source code and the executable to be analyzed must be specified. Refer to the <code class="command">opannotate</code> man 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.6. Understanding <code class="filename">/dev/oprofile/</code> </h2></div></div></div><a id="idm122568112" class="indexterm"></a><a id="idm133080224" class="indexterm"></a><div class="para">
+ The <code class="filename">/dev/oprofile/</code> directory contains the file system for OProfile. 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.7. 使用法の例</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 under performing, 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.8. OProfile Support for Java</h2></div></div></div><a id="idm101028464" 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 17 includes build-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.8.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:jvmti_oprofile</code></pre><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.
+ </div></div></div><div class="para">
+ To learn more about Java support in OProfile, refer to 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.9. Graphical Interface</h2></div></div></div><a id="idm104521264" class="indexterm"></a><div class="para">
+ Some OProfile preferences can be set with a graphical interface. To start it, execute the <code class="command">oprof_start</code> command as root at a shell prompt. To use the graphical interface, you will need to have the <code class="filename">oprofile-gui</code> package installed.
+ </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 unselected, 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 unselected, 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 checkbox 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 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.10. OProfile and SystemTap</h2></div></div></div><a id="idm118101648" 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 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 instrumentation, it is particularly useful for instrumenting the kernel and daemons.
+ </div><div class="para">
+ For more information on SystemTap, refer to <a class="xref" href="#s2-oprofile-useful-websites">「役に立つ Web サイト」</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.11. 追加のリソース</h2></div></div></div><a id="idm85841312" class="indexterm"></a><div class="para">
+ This chapter only highlights OProfile and how to configure and use it. To learn more, refer to the following resources.
+ </div><div class="section" id="s1-oprofile-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.11.1. Installed Docs</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/oprofile-<em class="replaceable"><code>version</code></em>/oprofile.html</code> — <em class="citetitle">OProfile Manual</em>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">oprofile</code> man 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></ul></div></div><div class="section" id="s2-oprofile-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.11.2. 役に立つ Web サイト</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://oprofile.sourceforge.net/">http://oprofile.sourceforge.net/</a> — Contains the latest documentation, mailing lists, IRC channels, and more.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/SystemTap_Beginners_Guide/index.html">SystemTap 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><div class="part" id="part-Kernel_Module_and_Driver_Configuration"><div class="titlepage"><div><div text-align="center"><h1 class="title">パート VII. カーネル、モジュールおよびドライバーの設定</h1></div></div></div><div class="partintro" id="idm127898896"><div></div><div class="para">
+ このパートは管理者にカーネルのカスタマイズを支援するさまざまなツールを取り扱います。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="#ch-Manually_Upgrading_the_Kernel">21. カーネルをアップグレードする</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-packages">21.1. カーネルパッケージの概要</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">21.2. アップグレードの準備</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">21.3. アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">21.4. アップグレードの実行</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">21.5. 初期RAMディスクイメージの確認</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">21.6. ブートローダの確認</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-kernel-
boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-iseries">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">21.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">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="#sec-Loading_a_Module">22.3. モジュールの読み込み方法</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#se
c-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#sec-Specific_Kernel_Module_Capabilities">22.7. Specific Kernel Module Capabilities</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Using_Multiple_Ethernet_Cards">22.7.1. 複数のイーサネットカードの使用</a></span></dt><dt><span class="section"><a href="#sec-Using_Channel_Bonding">22.7.2. Using Channel Bonding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kernel-modules-additional-resources-installed">22.8.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-kernel-modules-additional-resources-websites">22.8.2. 役に立つ We
b サイト</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-kdump">23. The kdump Crash Recovery Service</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kdump-installation">23.1. Installing the kdump Service</a></span></dt><dt><span class="section"><a href="#s1-kdump-configuration">23.2. Configuring the kdump Service</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kdump-configuration-firstboot">23.2.1. Configuring the kdump at First Boot</a></span></dt><dt><span class="section"><a href="#s2-kdump-configuration-gui">23.2.2. Using the Kernel Dump Configuration Utility</a></span></dt><dt><span class="section"><a href="#s2-kdump-configuration-cli">23.2.3. Configuring kdump on the Command Line</a></span></dt><dt><span class="section"><a href="#s2-kdump-configuration-testing">23.2.4. Testing the Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kdump-crash">23.3. Analyzing the Core Dump</a></span></dt
><dd><dl><dt><span class="section"><a href="#s2-kdump-crash-running">23.3.1. Running the crash Utility</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-log">23.3.2. Displaying the Message Buffer</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-backtrace">23.3.3. Displaying a Backtrace</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-processes">23.3.4. Displaying a Process Status</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-memory">23.3.5. Displaying Virtual Memory Information</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-files">23.3.6. Displaying Open Files</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-exit">23.3.7. Exiting the Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kdump-resources">23.4. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kdump-resources-installed">23.4.1. インストールされ
ているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-kdump-resources-online">23.4.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></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">第21章 カーネルをアップグレードする</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-kernel-packages">21.1. カーネルパッケージの概要</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">21.2. アップグレードの準備</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">21.3. アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">21.4. アップグレードの実行</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image
">21.5. 初期RAMディスクイメージの確認</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">21.6. ブートローダの確認</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-kernel-boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-iseries">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">21.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></div><a id="idm101543984" class="indexterm"></a><a id="idm190599392" class="indexterm"></a><a id="idm90788000" class="indexterm"></a><a id="idm81465680" 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>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span> package managers. <span class="application"><strong>PackageKit</strong></span> automatically queries the Yum repositories and informs you of packages with available updates, including kernel packages.
+ </div><div class="para">
+ そのため、本章は <code class="command">yum</code> の代わりに <code class="command">rpm</code> コマンドを使用してカーネルパッケージを手動で更新する必要があるユーザーの対して<span class="emphasis"><em>のみ</em></span>有用です。
+ </div><a id="idm88540816" class="indexterm"></a><a id="idm86174512" class="indexterm"></a><div class="warning"><div class="admonition_header"><h2>Use Yum to install kernels whenever possible</h2></div><div class="admonition"><div class="para">
+ Whenever possible, use either the <span class="application"><strong>Yum</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="idm106948576" class="indexterm"></a><div class="para">
+ For more information on installing kernel packages with <span class="application"><strong>Yum</strong></span>, refer to <a class="xref" href="#sec-Updating_Packages">「パッケージの更新」</a>.
+ </div><div class="section" id="s1-kernel-packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.1. カーネルパッケージの概要</h2></div></div></div><a id="idm88626560" class="indexterm"></a><a id="idm88625152" class="indexterm"></a><a id="idm137478032" class="indexterm"></a><a id="idm106737696" class="indexterm"></a><a id="idm106735840" class="indexterm"></a><a id="idm84969664" class="indexterm"></a><a id="idm120218112" class="indexterm"></a><a id="idm120216192" class="indexterm"></a><a id="idm85255120" class="indexterm"></a><a id="idm85253200" class="indexterm"></a><a id="idm119568560" class="indexterm"></a><a id="idm125554928" class="indexterm"></a><a id="idm125553008" 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-doc</span> — Documentation files from the kernel source. Various portions of the Linux kernel and the device drivers shipped with it are documented in these files. Installation of this package provides a reference to the options that can be passed to Linux kernel modules at load time.
+ </div><div class="para">
+ By default, these files are placed in the <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/</code> directory.
+ </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></ul></div></div><div class="section" id="s1-kernel-preparing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.2. アップグレードの準備</h2></div></div></div><a id="idm134872960" class="indexterm"></a><a id="idm62058736" class="indexterm"></a><a id="idm62056816" class="indexterm"></a><a id="idm109993024" 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, the system cannot be booted into Fedora without working boot media.
+ </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>. Refer to <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">yum 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 may differ:
+ </div><pre class="screen">~]# <code class="command">yum list installed "kernel-*"</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+kernel.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
+kernel.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing
+kernel-doc.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
+kernel-doc.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing
+kernel-headers.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
+kernel-headers.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing</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. Refer to <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">21.3. アップグレードされたカーネルをダウンロードする</h2></div></div></div><a id="idm116707440" class="indexterm"></a><a id="idm116706000" class="indexterm"></a><a id="idm120801632" class="indexterm"></a><a id="idm120799776" class="indexterm"></a><div class="para">
+ システムに対して更新されたカーネルがあるかどうかを確認するには、いくつかの方法があります。
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Security Advisories — Refer to <a href="http://fedoraproject.org/wiki/FSA">http://fedoraproject.org/wiki/FSA</a> 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.fedoraproject.org/updates/</a>.
+ </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">21.4. アップグレードの実行</h2></div></div></div><a id="idm113174416" 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. Refer to <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">21.5. 初期RAMディスクイメージの確認</h2></div></div></div><a id="idm108563744" 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 17 systems, whenever a new kernel is installed using either the <span class="application"><strong>Yum</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">21.5項「 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>手順21.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><pre class="screen">~]# <code class="command">ls /boot</code>
+config-3.1.0-0.rc6.git0.3.fc16.x86_64
+config-3.1.0-0.rc9.git0.0.fc16.x86_64
+elf-memtest86+-4.20
+grub
+grub2
+initramfs-3.1.0-0.rc6.git0.3.fc16.x86_64.img
+initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img
+initrd-plymouth.img
+memtest86+-4.20
+System.map-3.1.0-0.rc6.git0.3.fc16.x86_64
+System.map-3.1.0-0.rc9.git0.0.fc16.x86_64
+vmlinuz-3.1.0-0.rc6.git0.3.fc16.x86_64
+vmlinuz-3.1.0-0.rc9.git0.0.fc16.x86_64</pre><div class="para">
+ The example above shows that:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ we have two kernels installed (or, more correctly, two 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-vmlinuz-3.1.0-0.rc9.git0.0.fc16.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.1.0-0.rc9.git0.0.fc16.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 may 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>, refer to <a class="xref" href="#ch-kdump">23章<em>The kdump Crash Recovery Service</em></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 may 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.1.0-0.rc9.git0.0.fc16.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.1.0-0.rc9.git0.0.fc16.x86_64.img</code>
+/boot/initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img: 16M
+========================================================================
+dracut-013-15.fc16
+========================================================================
+drwxr-xr-x 8 root root 0 Oct 11 20:36 .
+lrwxrwxrwx 1 root root 17 Oct 11 20:36 lib -> run/initramfs/lib
+drwxr-xr-x 2 root root 0 Oct 11 20:36 sys
+drwxr-xr-x 2 root root 0 Oct 11 20:36 proc
+lrwxrwxrwx 1 root root 17 Oct 11 20:36 etc -> run/initramfs/etc
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre><div class="para">
+ Refer to <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">initrd <code class="filename">/<em class="replaceable"><code>path</code></em>/initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code></code> exists for the kernel version you are booting. For example:
+ </div><pre class="screen">~]# <code class="command">grep initrd /boot/grub2/grub.cfg</code>
+ initrd /initramfs-3.1.0-0.rc6.git0.3.fc16.x86_64.img
+ initrd /initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img</pre><div class="para">
+ Refer to <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="idm120723600" 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">21.6. ブートローダの確認</h2></div></div></div><a id="idm92023968" 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 may 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 "Refer to" link to jump to the correct instructions for your system.
+ </div><div class="table" id="tb-grub-arch-loaders"><h6>表21.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="">
+ Refer to
+ </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">21.6.1. Configuring the GRUB 2 Boot Loader</h3></div></div></div><a id="idm17311216" class="indexterm"></a><a id="idm123561136" class="indexterm"></a><div class="para">
+ Fedora 17 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 17 with Linux kernel 3.4.0-1.fc17.x86_64:
+ </div><pre class="programlisting">menuentry 'Fedora (3.4.0-1.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-77ba9149-751a-48e0-974f-ad94911734b9' {
+ 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' 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ else
+ search --no-floppy --fs-uuid --set=root 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ fi
+ echo 'Loading Fedora (3.4.0-1.fc17.x86_64)'
+ linux /vmlinuz-3.4.0-1.fc17.x86_64 root=/dev/mapper/vg_fedora-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_fedora/lv_swap KEYTABLE=us rd.lvm.lv=vg_fedora/lv_root rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
+ echo 'Loading initial ramdisk ...'
+ initrd /initramfs-3.4.0-1.fc17.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">initrd /initramfs-3.4.0-1.fc17.x86_64.img</code> line means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-3.4.0-1.fc17.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">手順21.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">21.6.2. Configuring the OS/400 Boot Loader</h3></div></div></div><a id="idm133295216" class="indexterm"></a><a id="idm133293776" 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">21.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">第22章 Working with Kernel Modules</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="#sec-Loading_a_Module">22.3. モジュールの読み込み方法</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#sec-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href=
"#sec-Specific_Kernel_Module_Capabilities">22.7. Specific Kernel Module Capabilities</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Using_Multiple_Ethernet_Cards">22.7.1. 複数のイーサネットカードの使用</a></span></dt><dt><span class="section"><a href="#sec-Using_Channel_Bonding">22.7.2. Using Channel Bonding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kernel-modules-additional-resources-installed">22.8.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-kernel-modules-additional-resources-websites">22.8.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></div><a id="idm100561584" class="indexterm"></a><a id="idm137421760" class="indexterm"></a><a id="idm86073712" 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">module-init-tools</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 and/or unload modules manually, such as when a module provides optional functionality, one module should be preferred over another although either could provide basic functionality, or when a module is misbehaving, among other situations.
+ </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="package">module-init-tools</span> package 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 module-init-tools package</h2></div><div class="admonition"><div class="para">
+ In order to use the kernel module utilities described in this chapter, first ensure the module-init-tools package is installed on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install module-init-tools</code>
+</pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は <a class="xref" href="#sec-Installing">「パッケージのインストール」</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">22.1. Listing Currently-Loaded Modules</h2></div></div></div><a id="idm114528176" class="indexterm"></a><a id="idm100329760" class="indexterm"></a><a id="idm18515808" 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
+xfs 803635 1
+exportfs 3424 1 xfs
+vfat 8216 1
+fat 43410 1 vfat
+tun 13014 2
+fuse 54749 2
+ip6table_filter 2743 0
+ip6_tables 16558 1 ip6table_filter
+ebtable_nat 1895 0
+ebtables 15186 1 ebtable_nat
+ipt_MASQUERADE 2208 6
+iptable_nat 5420 1
+nf_nat 19059 2 ipt_MASQUERADE,iptable_nat
+rfcomm 65122 4
+ipv6 267017 33
+sco 16204 2
+bridge 45753 0
+stp 1887 1 bridge
+llc 4557 2 bridge,stp
+bnep 15121 2
+l2cap 45185 16 rfcomm,bnep
+cpufreq_ondemand 8420 2
+acpi_cpufreq 7493 1
+freq_table 3851 2 cpufreq_ondemand,acpi_cpufreq
+usb_storage 44536 1
+sha256_generic 10023 2
+aes_x86_64 7654 5
+aes_generic 27012 1 aes_x86_64
+cbc 2793 1
+dm_crypt 10930 1
+kvm_intel 40311 0
+kvm 253162 1 kvm_intel
+<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, refer to <a class="xref" href="#sec-Unloading_a_Module">「Unloading a Module」</a>.
+ </div></li></ul></div><a id="idm123413280" 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">22.2. Displaying Information About a Module</h2></div></div></div><a id="idm130271920" class="indexterm"></a><a id="idm123265376" class="indexterm"></a><a id="idm123262976" 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="package">module-init-tools</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>例22.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/2.6.32-71.el6.x86_64/kernel/drivers/net/e1000e/e1000e.ko
+version: 1.2.7-k2
+license: GPL
+description: Intel(R) PRO/1000 Network Driver
+author: Intel Corporation, <linux.nics at intel.com>
+srcversion: 93CB73D3995B501872B2982
+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:
+vermagic: 2.6.32-71.el6.x86_64 SMP mod_unload modversions
+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)
+parm: EEE:Enable/disable on parts that support the feature (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>例22.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: EEE:Enable/disable on parts that support the feature (array of 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">22.3. モジュールの読み込み方法</h2></div></div></div><a id="idm47751328" class="indexterm"></a><a id="idm137801520" class="indexterm"></a><a id="idm138246336" 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="idm133633040" 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 may include loading module dependencies.
+ </div><div class="example" id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>例22.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/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_tgt.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/libfc/libfc.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</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 <span class="quote">「<span class="quote">primitive</span>」</span> <code class="command">insmod</code> command to insert the modules into the running kernel.
+ </div></div></div><br class="example-break" /><a id="idm114040672" class="indexterm"></a><a id="idm99184080" 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">22.4. Unloading a Module</h2></div></div></div><a id="idm84750240" class="indexterm"></a><a id="idm84748800" class="indexterm"></a><a id="idm87798528" 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">
+ Refer to <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>例22.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 (because you believe there is a bug in it that is affecting system stability, for example), your terminal session might look similar to this:
+ </div><pre class="screen">~]# <code class="command">modinfo -F depends firewire_ohci</code>
+depends: firewire-core
+~]# <code class="command">modinfo -F depends firewire_core</code>
+depends: crc-itu-t
+~]# <code class="command">modinfo -F depends crc-itu-t</code>
+depends:</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 /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-ohci.ko
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-core.ko
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</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="idm75689168" class="indexterm"></a><a id="idm98142896" 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">22.5. Setting Module Parameters</h2></div></div></div><a id="idm89197968" class="indexterm"></a><a id="idm89196528" 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="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 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>手順22.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. For example:
+ </div><pre class="screen">~]# <code class="command">lsmod | grep e1000e</code>
+~]# </pre><div class="para">
+ Output indicates that the module is already loaded into the kernel, in which case you must first unload it before proceeding. Refer to <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 Energy Efficient Ethernet (EEE) turned on<a href="#ftn.footnote-Energy_Efficient_Ethernet" class="footnote"><sup class="footnote" id="footnote-Energy_Efficient_Ethernet">[3]</sup></a> , you would run, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">modprobe e1000e InterruptThrottleRate=3000,3000,3000 EEE=1</code></pre><div class="para">
+ This example illustrates passing multiple valued 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">22.6. Persistent Module Loading</h2></div></div></div><a id="idm85283296" class="indexterm"></a><a id="idm85281376" class="indexterm"></a><div class="para">
+ As shown in <a class="xref" href="#ex-Listing_information_about_a_kernel_module_with_lsmod">例22.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 creating a new <code class="filename"><em class="replaceable"><code>file_name</code></em>.modules</code> file in the <code class="filename">/etc/sysconfig/modules/</code> directory, where <em class="replaceable"><code>file_name</code></em> is any descriptive name of your choice. Your <code class="filename"><em class="replaceable"><code>file_name</code></em>.modules</code> files are treated by the system startup scripts as shell scripts, and as such should begin with an <em class="firstterm">interpreter directive</em> (also called a <span class="quote">「<span class="quote">bang line</span>」</span>) as their first line:
+ </div><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span></pre><div class="para">
+ Additionally, the <code class="filename"><em class="replaceable"><code>file_name</code></em>.modules</code> file should be executable. You can make it executable by running:
+ </div><pre class="screen">modules]# <code class="command">chmod +x <em class="replaceable"><code>file_name</code></em>.modules</code>
+</pre><div class="example" id="ex-bluez-uinput.modules"><h6>例22.5 /etc/sysconfig/modules/bluez-uinput.modules</h6><div class="example-contents"><div class="para">
+ The following <code class="filename">bluez-uinput.modules</code> script loads the <code class="systemitem">uinput</code> module:
+ </div><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+<span class="perl_Keyword">if</span><span class="perl_Reserved"> [</span> ! -c /dev/input/uinput<span class="perl_Reserved"> ]</span> ; <span class="perl_Keyword">then</span>
+ <span class="perl_Reserved">exec</span> /sbin/modprobe uinput <span class="perl_Operator">></span>/dev/null <span class="perl_Operator">2>&1</span>
+<span class="perl_Keyword">fi</span></pre><div class="para">
+ The <code class="literal">if</code>-conditional statement on the third line ensures that the <code class="filename">/dev/input/uinput</code> file does <span class="emphasis"><em>not</em></span> already exist (the <code class="literal">!</code> symbol negates the condition), and, if that is the case, loads the <code class="systemitem">uinput</code> module by calling <code class="command">exec /sbin/modprobe uinput</code>. Note that the <code class="systemitem">uinput</code> module creates the <code class="filename">/dev/input/uinput</code> file, so testing to see if that file exists serves as verification of whether the <code class="systemitem">uinput</code> module is loaded into the kernel.
+ </div><div class="para">
+ The following <code class="command">>/dev/null 2>&1</code> clause at the end of that line redirects any output to <code class="filename">/dev/null</code> so that the <code class="command">modprobe</code> command remains quiet.
+ </div></div></div><br class="example-break" /></div><div class="section" id="sec-Specific_Kernel_Module_Capabilities"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.7. Specific Kernel Module Capabilities</h2></div></div></div><div class="para">
+ This section explains how to enable specific kernel capabilities using various kernel modules.
+ </div><div class="section" id="sec-Using_Multiple_Ethernet_Cards"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.1. 複数のイーサネットカードの使用</h3></div></div></div><a id="idm118694032" class="indexterm"></a><div class="para">
+ It is possible to use multiple Ethernet cards on a single machine. For each card there must be an <code class="command">alias</code> and, possibly, <code class="command">options</code> lines for each card in a user-created <code class="filename"><em class="replaceable"><code>module_name</code></em>.conf</code> file in the <code class="filename">/etc/modprobe.d/</code> directory.
+ </div><div class="para">
+ For additional information about using multiple Ethernet cards, refer to the <em class="citetitle">Linux Ethernet-HOWTO</em> online at <a href="http://www.redhat.com/mirrors/LDP/HOWTO/Ethernet-HOWTO.html">http://www.redhat.com/mirrors/LDP/HOWTO/Ethernet-HOWTO.html</a>.
+ </div></div><div class="section" id="sec-Using_Channel_Bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.2. Using Channel Bonding</h3></div></div></div><a id="idm124359136" class="indexterm"></a><a id="idm124357216" class="indexterm"></a><a id="idm55145104" class="indexterm"></a><a id="idm55143664" class="indexterm"></a><a id="idp344352" class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind NICs together into a single channel using the <code class="filename">bonding</code> kernel module and a special network interface, called a <em class="firstterm">channel bonding interface</em>. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><a id="idp347344" class="indexterm"></a><a id="idm116049200" class="indexterm"></a><div class="para">
+ 管理者は次の手順にて 複数のネットワークインターフェースをチャネル ボンディングしてください。
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ As <code class="systemitem">root</code>, create a new file named <code class="filename"><em class="replaceable"><code>bonding</code></em>.conf</code> in the <code class="filename">/etc/modprobe.d/</code> directory. Note that you can name this file anything you like as long as it ends with a <code class="filename">.conf</code> extension. Insert the following line in this new file:
+ </div><pre class="screen">alias bond<em class="replaceable"><code>N</code></em> bonding</pre><div class="para">
+ Replace <em class="replaceable"><code>N</code></em> with the interface number, such as <code class="command">0</code>. For each configured channel bonding interface, there must be a corresponding entry in your new <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code> file.
+ </div></li><li class="listitem"><div class="para">
+ Configure a channel bonding interface as outlined in <a class="xref" href="#s2-networkscripts-interfaces-chan">「チャンネル・ボンディング・インターフェース」</a>.
+ </div></li><li class="listitem"><div class="para">
+ To enhance performance, adjust available module options to ascertain what combination works best. Pay particular attention to the <code class="command">miimon</code> or <code class="command">arp_interval</code> and the <code class="command">arp_ip_target</code> parameters. Refer to <a class="xref" href="#s3-modules-bonding-directives">「Bonding Module Directives」</a> for a list of available options and how to quickly determine the best ones for your bonded interface.
+ </div></li></ol></div><div class="section" id="s3-modules-bonding-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.2.1. Bonding Module Directives</h4></div></div></div><a id="idm47635904" class="indexterm"></a><a id="idm70964752" class="indexterm"></a><a id="idm84722784" class="indexterm"></a><div class="para">
+ It is a good idea to test which channel bonding module parameters work best for your bonded interfaces before adding them to the <em class="parameter"><code>BONDING_OPTS="<em class="replaceable"><code>bonding parameters</code></em>"</code></em> directive in your bonding interface configuration file (<code class="filename">ifcfg-bond0</code> for example). Parameters to bonded interfaces can be configured without unloading (and reloading) the bonding module by manipulating files in the <code class="systemitem">sysfs</code> file system.
+ </div><div class="para">
+ <code class="systemitem">sysfs</code> is a virtual file system that represents kernel objects as directories, files and symbolic links. <code class="systemitem">sysfs</code> can be used to query for information about kernel objects, and can also manipulate those objects through the use of normal file system commands. The <code class="systemitem">sysfs</code> virtual file system has a line in <code class="filename">/etc/fstab</code>, and is mounted under the <code class="filename">/sys/</code> directory. All bonding interfaces can be configured dynamically by interacting with and manipulating files under the <code class="filename">/sys/class/net/</code> directory.
+ </div><div class="para">
+ In order to determine the best parameters for your bonding interface, create a channel bonding interface file such as <code class="filename">ifcfg-bond0</code> by following the instructions in <a class="xref" href="#s2-networkscripts-interfaces-chan">「チャンネル・ボンディング・インターフェース」</a>. Insert the <em class="parameter"><code>SLAVE=yes</code></em> and <em class="parameter"><code>MASTER=bond0</code></em> directives in the configuration files for each interface bonded to bond0. Once this is completed, you can proceed to testing the parameters.
+ </div><div class="para">
+ First, bring up the bond you created by running <code class="command">ifconfig <code class="option">bond<em class="replaceable"><code>N</code></em></code> <code class="option">up</code></code> as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">ifconfig bond0 up</code>
+</pre><div class="para">
+ If you have correctly created the <code class="filename">ifcfg-bond0</code> bonding interface file, you will be able to see <code class="computeroutput">bond0</code> listed in the output of running <code class="command">ifconfig</code> (without any options):
+ </div><pre class="screen">~]# <code class="command">ifconfig</code>
+bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
+ UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
+ RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
+eth0 Link encap:Ethernet HWaddr 52:54:00:26:9E:F1
+ inet addr:192.168.122.251 Bcast:192.168.122.255 Mask:255.255.255.0
+ inet6 addr: fe80::5054:ff:fe26:9ef1/64 Scope:Link
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:207 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:205 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:1000
+ RX bytes:70374 (68.7 KiB) TX bytes:25298 (24.7 KiB)
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em>
+</pre><div class="para">
+ To view all existing bonds, even if they are not up, run:
+ </div><pre class="screen">~]# <code class="command">cat /sys/class/net/bonding_masters</code>
+bond0</pre><div class="para">
+ You can configure each bond individually by manipulating the files located in the <code class="filename">/sys/class/net/bond<em class="replaceable"><code>N</code></em>/bonding/</code> directory. First, the bond you are configuring must be taken down:
+ </div><pre class="screen">~]# <code class="command">ifconfig bond0 down</code>
+</pre><div class="para">
+ As an example, to enable MII monitoring on bond0 with a 1 second interval, you could run (as <code class="systemitem">root</code>):
+ </div><pre class="screen">~]# <code class="command">echo 1000 > /sys/class/net/bond0/bonding/miimon</code>
+</pre><div class="para">
+ To configure bond0 for <em class="parameter"><code>balance-alb</code></em> mode, you could run either:
+ </div><pre class="screen">~]# <code class="command">echo 6 > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ ...or, using the name of the mode:
+ </div><pre class="screen">~]# <code class="command">echo balance-alb > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ After configuring options for the bond in question, you can bring it up and test it by running <code class="command">ifconfig bond<em class="replaceable"><code>N</code></em> <code class="option">up</code> </code>. If you decide to change the options, take the interface down, modify its parameters using <code class="systemitem">sysfs</code>, bring it back up, and re-test.
+ </div><div class="para">
+ Once you have determined the best set of parameters for your bond, add those parameters as a space-separated list to the <em class="parameter"><code>BONDING_OPTS=</code></em> directive of the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code>N</code></em> </code> file for the bonding interface you are configuring. Whenever that bond is brought up (for example, by the system during the boot sequence if the <em class="parameter"><code>ONBOOT=yes</code></em> directive is set), the bonding options specified in the <em class="parameter"><code>BONDING_OPTS</code></em> will take effect for that bond. For more information on configuring bonding interfaces (and <em class="parameter"><code>BONDING_OPTS</code></em>), refer to <a class="xref" href="#s2-networkscripts-interfaces-chan">「チャンネル・ボンディング・インターフェース」</a>.
+ </div><div class="para">
+ The following list provides the names of many of the more common channel bonding parameters, along with a descriptions of what they do. For more information, refer to the brief descriptions for each <code class="computeroutput">parm</code> in <code class="command">modinfo bonding</code> output, or the exhaustive descriptions in the <code class="filename">bonding.txt</code> file in the <span class="package">kernel-doc</span> package (see <a class="xref" href="#s1-kernel-modules-additional-resources">「その他のリソース」</a>).
+ </div><div class="variablelist"><h6>Bonding Interface Parameters</h6><dl class="variablelist compact"><dt class="varlistentry"><span class="term"> <code class="literal">arp_interval=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often ARP monitoring occurs.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure you specify all required parameters</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div><div class="para">
+ If using this setting while in <code class="literal">mode=0</code> or <code class="literal">mode=1</code> (the two load-balancing modes), the network switch must be configured to distribute packets evenly across the NICs. For more information on how to accomplish this, refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/bonding.txt</code>
+ </div><div class="para">
+ The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_ip_target=<em class="replaceable"><code>ip_address</code></em>[<span class="optional">,<em class="replaceable"><code>ip_address_2</code></em>,…<em class="replaceable"><code>ip_address_16</code></em></span>] </code> </span></dt><dd><div class="para">
+ Specifies the target IP address of ARP requests when the <code class="literal">arp_interval</code> parameter is enabled. Up to 16 IP addresses can be specified in a comma separated list.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_validate=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Validate source/distribution of ARP probes; default is <strong class="userinput"><code>none</code></strong>. Other valid values are <strong class="userinput"><code>active</code></strong>, <strong class="userinput"><code>backup</code></strong>, and <strong class="userinput"><code>all</code></strong>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">debug=<em class="replaceable"><code>number</code></em> </code> </span></dt><dd><div class="para">
+ Enables debug messages. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Debug messages are disabled. This is the default.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Debug messages are enabled.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">downdelay=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait after link failure before disabling the link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term">lacp_rate=<em class="replaceable"><code>value</code></em> </span></dt><dd><div class="para">
+ Specifies the rate at which link partners should transmit LACPDU packets in 802.3ad mode. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>slow</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. This specifies that partners should transmit LACPDUs every 30 seconds.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>fast</code></strong> or <strong class="userinput"><code>1</code></strong> — Specifies that partners should transmit LACPDUs every 1 second.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">miimon=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often MII link monitoring occurs. This is useful if high availability is required because MII is used to verify that the NIC is active. To verify that the driver for a particular NIC supports the MII tool, type the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">ethtool <em class="replaceable"><code>interface_name</code></em> | grep "Link detected:"</code>
+</pre><div class="para">
+ In this command, replace <em class="replaceable"><code>interface_name</code></em> with the name of the device interface, such as <strong class="userinput"><code>eth0</code></strong>, not the bond interface. If MII is supported, the command returns:
+ </div><pre class="screen">Link detected: yes</pre><div class="para">
+ If using a bonded interface for high availability, the module for each NIC must support MII. Setting the value to <strong class="userinput"><code>0</code></strong> (the default), turns this feature off. When configuring this setting, a good starting point for this parameter is <strong class="userinput"><code>100</code></strong>.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure you specify all required parameters</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">mode=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Allows you to specify the bonding policy. The <em class="replaceable"><code>value</code></em> can be one of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-rr</code></strong> or <strong class="userinput"><code>0</code></strong> — Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>active-backup</code></strong> or <strong class="userinput"><code>1</code></strong> — Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-xor</code></strong> or <strong class="userinput"><code>2</code></strong> — Sets an XOR (exclusive-or) policy for fault tolerance and load balancing. Using this method, the interface matches up the incoming request's MAC address with the MAC address for one of the slave NICs. Once this link is established, transmissions are sent out sequentially beginning with the first available interface.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>broadcast</code></strong> or <strong class="userinput"><code>3</code></strong> — Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>802.3ad</code></strong> or <strong class="userinput"><code>4</code></strong> — Sets an IEEE 802.3ad dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a switch that is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-tlb</code></strong> or <strong class="userinput"><code>5</code></strong> — Sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-alb</code></strong> or <strong class="userinput"><code>6</code></strong> — Sets an Active Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for IPV4 traffic. Receive load balancing is achieved through ARP negotiation.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">num_unsol_na=<em class="replaceable"><code>number</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the number of unsolicited IPv6 Neighbor Advertisements to be issued after a failover event. One unsolicited NA is issued immediately after the failover.
+ </div><div class="para">
+ The valid range is <strong class="userinput"><code>0 - 255</code></strong>; the default value is <strong class="userinput"><code>1</code></strong>. This parameter affects only the active-backup mode.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary=<em class="replaceable"><code>interface_name</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the interface name, such as <strong class="userinput"><code>eth0</code></strong>, of the primary device. The <code class="literal">primary</code> device is the first of the bonding interfaces to be used and is not abandoned unless it fails. This setting is particularly useful when one NIC in the bonding interface is faster and, therefore, able to handle a bigger load.
+ </div><div class="para">
+ This setting is only valid when the bonding interface is in <strong class="userinput"><code>active-backup</code></strong> mode. Refer to <code class="filename"> /usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel-version</code></em>/Documentation/networking/bonding.txt</code> for more information.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary_reselect=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the reselection policy for the primary slave. This affects how the primary slave is chosen to become the active slave when failure of the active slave or recovery of the primary slave occurs. This parameter is designed to prevent flip-flopping between the primary slave and other slaves. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>always</code></strong> or <strong class="userinput"><code>0</code></strong> (default) — The primary slave becomes the active slave whenever it comes back up.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>better</code></strong> or <strong class="userinput"><code>1</code></strong> — The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>failure</code></strong> or <strong class="userinput"><code>2</code></strong> — The primary slave becomes the active slave only if the current active slave fails and the primary slave is up.
+ </div></li></ul></div><div class="para">
+ The <code class="literal">primary_reselect</code> setting is ignored in two cases:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no slaves are active, the first slave to recover is made the active slave.
+ </div></li><li class="listitem"><div class="para">
+ When initially enslaved, the primary slave is always made the active slave.
+ </div></li></ul></div><div class="para">
+ Changing the <code class="literal">primary_reselect</code> policy via <code class="systemitem">sysfs</code> will cause an immediate selection of the best active slave according to the new policy. This may or may not result in a change of the active slave, depending upon the circumstances
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">updelay=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait before enabling a link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">use_carrier=<em class="replaceable"><code>number</code></em> </code> </span></dt><dd><div class="para">
+ Specifies whether or not <code class="literal">miimon</code> should use MII/ETHTOOL ioctls or <code class="function">netif_carrier_ok()</code> to determine the link state. The <code class="function">netif_carrier_ok()</code> function relies on the device driver to maintains its state with <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>; most device drivers support this function.
+ </div><div class="para">
+ The MII/ETHROOL ioctls tools utilize a deprecated calling sequence within the kernel. However, this is still configurable in case your device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>.
+ </div><div class="para">
+ Valid values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Default setting. Enables the use of <code class="function">netif_carrier_ok()</code>.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Enables the use of MII/ETHTOOL ioctls.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ If the bonding interface insists that the link is up when it should not be, it is possible that your network device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em></code>.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">xmit_hash_policy=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Selects the transmit hash policy used for slave selection in <strong class="userinput"><code>balance-xor</code></strong> and <strong class="userinput"><code>802.3ad</code></strong> modes. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> or <strong class="userinput"><code>layer2</code></strong> — Default setting. This parameter uses the XOR of hardware MAC addresses to generate the hash. The formula used is:
+ </div><pre class="screen">(<em class="replaceable"><code>source_MAC_address</code></em> XOR <em class="replaceable"><code>destination_MAC</code></em>) MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave, and is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> or <strong class="userinput"><code>layer3+4</code></strong> — Uses upper layer protocol information (when available) to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves.
+ </div><div class="para">
+ The formula for unfragmented TCP and UDP packets used is:
+ </div><pre class="screen">((<em class="replaceable"><code>source_port</code></em> XOR <em class="replaceable"><code>dest_port</code></em>) XOR
+ ((<em class="replaceable"><code>source_IP</code></em> XOR <em class="replaceable"><code>dest_IP</code></em>) AND <code class="constant">0xffff</code>)
+ MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ For fragmented TCP or UDP packets and all other IP protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as the <code class="command">layer2</code> transmit hash policy.
+ </div><div class="para">
+ This policy intends to mimic the behavior of certain switches; particularly, Cisco switches with PFC2 as well as some Foundry and IBM products.
+ </div><div class="para">
+ The algorithm used by this policy is not 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>2</code></strong> or <strong class="userinput"><code>layer2+3</code></strong> — Uses a combination of layer2 and layer3 protocol information to generate the hash.
+ </div><div class="para">
+ Uses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is:
+ </div><pre class="screen">(((<em class="replaceable"><code>source_IP</code></em> XOR <em class="replaceable"><code>dest_IP</code></em>) AND <code class="constant">0xffff</code>) XOR
+ ( <em class="replaceable"><code>source_MAC</code></em> XOR <em class="replaceable"><code>destination_MAC</code></em> ))
+ MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy.
+ </div><div class="para">
+ This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.
+ </div><div class="para">
+ This algorithm is 802.3ad compliant.
+ </div></li></ul></div></dd></dl></div></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">22.8. その他のリソース</h2></div></div></div><div class="para">
+ For more information on kernel modules and their utilities, refer to the following resources.
+ </div><div class="section" id="s2-kernel-modules-additional-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.8.1. インストールされているドキュメント</h3></div></div></div><div class="para">
+ There is a number of manual pages for various utilities related to the kernel modules:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">man lsmod</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">lsmod</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man modinfo</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">modinfo</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man modprobe</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">modprobe</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man rmmod</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">rmmod</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ethtool</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">ethtool</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man mii-tool</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">mii-tool</code> command.
+ </div></dd></dl></div><div class="para">
+ Additionally, you can refer to the documentation provided by the <span class="package">kernel-doc</span> package:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/</code></span></dt><dd><div class="para">
+ This directory contains information on the kernel, kernel modules, and their respective parameters. Note that before accessing the kernel documentation, you must run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install kernel-doc</code></pre></dd></dl></div></div><div class="section" id="s2-kernel-modules-additional-resources-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.8.2. 役に立つ Web サイト</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel Module HOWTO</a></span></dt><dd><div class="para">
+ The <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> from the Linux Documentation Project contains further information on working with kernel modules.
+ </div></dd></dl></div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="footnote-Energy_Efficient_Ethernet" class="footnote"><div class="para"><a href="#footnote-Energy_Efficient_Ethernet" class="para"><sup class="para">[3] </sup></a>
+ Despite what the example might imply, Energy Efficient Ethernet is turned on by default in the <code class="systemitem">e1000e</code> driver.
+ </div></div></div></div><div xml:lang="ja-JP" class="chapter" id="ch-kdump" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第23章 The kdump Crash Recovery Service</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-kdump-installation">23.1. Installing the kdump Service</a></span></dt><dt><span class="section"><a href="#s1-kdump-configuration">23.2. Configuring the kdump Service</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kdump-configuration-firstboot">23.2.1. Configuring the kdump at First Boot</a></span></dt><dt><span class="section"><a href="#s2-kdump-configuration-gui">23.2.2. Using the Kernel Dump Configuration Utility</a></span></dt><dt><span class="section"><a href="#s2-kdump-configuration-cli">23.2.3. Configuring kdump on the Command Line</a></span></dt><dt><span class="section"><a href="#s2-kdump-configuration-testing">23.2.4. Testing the Configuration</a></span></dt></dl></dd><dt><span class="se
ction"><a href="#s1-kdump-crash">23.3. Analyzing the Core Dump</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kdump-crash-running">23.3.1. Running the crash Utility</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-log">23.3.2. Displaying the Message Buffer</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-backtrace">23.3.3. Displaying a Backtrace</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-processes">23.3.4. Displaying a Process Status</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-memory">23.3.5. Displaying Virtual Memory Information</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-files">23.3.6. Displaying Open Files</a></span></dt><dt><span class="section"><a href="#s2-kdump-crash-exit">23.3.7. Exiting the Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kdump-resources">23.4. その他のリソース</a></span></dt><dd><dl><dt><span class="sect
ion"><a href="#s2-kdump-resources-installed">23.4.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="#s2-kdump-resources-online">23.4.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></div><div class="para">
+ When the <code class="systemitem">kdump</code> crash dumping mechanism is enabled, the system is booted from the context of another kernel. This second kernel reserves a small amount of memory and its only purpose is to capture the core dump image in case the system crashes.
+ </div><div class="para">
+ Being able to analyze the core dump significantly helps to determine the exact cause of the system failure, and it is therefore strongly recommended to have this feature enabled. This chapter explains how to configure, test, and use the <code class="systemitem">kdump</code> service in Fedora, and provides a brief overview of how to analyze the resulting core dump using the <span class="application"><strong>crash</strong></span> debugging utility.
+ </div><div class="section" id="s1-kdump-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">23.1. Installing the kdump Service</h2></div></div></div><a id="idm67926096" class="indexterm"></a><div class="para">
+ In order use the <code class="systemitem">kdump</code> service on your system, make sure you have the <span class="package">kexec-tools</span> package installed. To do so, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install kexec-tools</code></pre><div class="para">
+ For more information on how to install new packages in Fedora, refer to <a class="xref" href="#sec-Installing">「パッケージのインストール」</a>.
+ </div></div><div class="section" id="s1-kdump-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">23.2. Configuring the kdump Service</h2></div></div></div><div class="para">
+ There are three common means of configuring the <code class="systemitem">kdump</code> service: at the first boot, using the <span class="application"><strong>Kernel Dump Configuration</strong></span> graphical utility, and doing so manually on the command line.
+ </div><a id="idm98408112" class="indexterm"></a><div class="important"><div class="admonition_header"><h2>Disable IOMMU on Intel chipsets</h2></div><div class="admonition"><div class="para">
+ A limitation in the current implementation of the <code class="systemitem">Intel IOMMU</code> driver can occasionally prevent the <code class="systemitem">kdump</code> service from capturing the core dump image. To use <code class="systemitem">kdump</code> on Intel architectures reliably, it is advised that the IOMMU support is disabled.
+ </div></div></div><div class="section" id="s2-kdump-configuration-firstboot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.2.1. Configuring the kdump at First Boot</h3></div></div></div><div class="para">
+ When the system boots for the first time, the <span class="application"><strong>firstboot</strong></span> application is launched to guide the user through the initial configuration of the freshly installed system. To configure <code class="systemitem">kdump</code>, navigate to the <span class="guilabel"><strong>Kdump</strong></span> section and follow the instructions below.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure the system has enough memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_17.html#sect-Release_Notes-Hardware_Overview"><em class="citetitle">Hardware Overview</em></a> section of the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><em class="citetitle">Fedora 17 Release Notes</em></a>. When the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ </div></div></div><div class="section" id="s3-kdump-configuration-firstboot-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.1.1. サービスの有効化</h4></div></div></div><a id="idm108278672" class="indexterm"></a><div class="para">
+ To allow the <code class="systemitem">kdump</code> daemon to start at boot time, select the <span class="guilabel"><strong>Enable kdump?</strong></span> checkbox. This will enable the service and start it for the current session. Similarly, unselecting the checkbox will disable it for and stop the service immediately.
+ </div></div><div class="section" id="s3-kdump-configuration-firstboot-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.1.2. Configuring the Memory Usage</h4></div></div></div><a id="idm133313104" class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel, click the up and down arrow buttons next to the <span class="guilabel"><strong>Kdump Memory</strong></span> field to increase or decrease the value. Notice that the <span class="guilabel"><strong>Usable System Memory</strong></span> field changes accordingly showing you the remaining memory that will be available to the system.
+ </div></div></div><div class="section" id="s2-kdump-configuration-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.2.2. Using the Kernel Dump Configuration Utility</h3></div></div></div><a id="idm76160752" class="indexterm"></a><a id="idm113614224" class="indexterm"></a><div class="para">
+ To start the <span class="application"><strong>Kernel Dump Configuration</strong></span> utility, select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>Other</strong></span> → <span class="guimenuitem"><strong>Kernel crash dumps</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">system-config-kdump</code> at a shell prompt. You will be presented with a window as shown in <a class="xref" href="#fig-kdump-kernel_dump_configuration">図23.1「Basic Settings」</a>.
+ </div><div class="para">
+ The utility allows you to configure <code class="systemitem">kdump</code> as well as to enable or disable starting the service at boot time. When you are done, click <span class="guibutton"><strong>Apply</strong></span> to save the changes. The system reboot will be requested, and unless you are already authenticated, you will be prompted to enter the superuser password.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure the system has enough memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_17.html#sect-Release_Notes-Hardware_Overview"><em class="citetitle">Hardware Overview</em></a> section of the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><em class="citetitle">Fedora 17 Release Notes</em></a>. When the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ </div></div></div><div class="section" id="s3-kdump-configuration-gui-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.1. サービスの有効化</h4></div></div></div><a id="idm109236880" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, click the <span class="guibutton"><strong>Enable</strong></span> button on the toolbar. This will enable the service and start it for the current session. Similarly, clicking the <span class="guibutton"><strong>Disable</strong></span> button will disable it and stop the service immediately.
+ </div><div class="para">
+ For more information on system services and their configuration, refer to <a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>.
+ </div></div><div class="section" id="s3-kdump-configuration-gui-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.2. The Basic Settings Tab</h4></div></div></div><a id="idm124943280" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Basic Settings</strong></span> tab enables you to configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel. To do so, select the <span class="guilabel"><strong>Manual kdump memory settings</strong></span> radio button, and click the up and down arrow buttons next to the <span class="guilabel"><strong>New kdump Memory</strong></span> field to increase or decrease the value. Notice that the <span class="guilabel"><strong>Usable Memory</strong></span> field changes accordingly showing you the remaining memory that will be available to the system.
+ </div><div class="figure" id="fig-kdump-kernel_dump_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration.png" alt="Basic Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Basic Settings</strong></span>
+ </div></div></div></div><h6>図23.1 Basic Settings</h6></div><br class="figure-break" /></div><div class="section" id="s3-kdump-configuration-gui-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.3. The Target Settings Tab</h4></div></div></div><a id="idm121570720" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Target Settings</strong></span> tab enables you to specify the target location for the <code class="filename">vmcore</code> dump. It can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol.
+ </div><div class="figure" id="fig-kdump-kernel_dump_configuration-target_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-target_settings.png" alt="Target Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Target Settings</strong></span>
+ </div></div></div></div><h6>図23.2 Target Settings</h6></div><br class="figure-break" /><div class="para">
+ To save the dump to the local file system, select the <span class="guilabel"><strong>Local filesystem</strong></span> radio button. Optionally, you can customize the settings by choosing a different partition from the <span class="guilabel"><strong>Partition</strong></span>, and a target directory from the <span class="guilabel"><strong>Path</strong></span> pulldown lists.
+ </div><div class="para">
+ To write the dump directly to a device, select the <span class="guilabel"><strong>Raw device</strong></span> radio button, and choose the desired target device from the pulldown list next to it.
+ </div><div class="para">
+ To store the dump to a remote machine, select the <span class="guilabel"><strong>Network</strong></span> radio button. To use the NFS protocol, select the <span class="guilabel"><strong>NFS</strong></span> radio button, and fill the <span class="guilabel"><strong>Server name</strong></span> and <span class="guilabel"><strong>Path to directory</strong></span> fields. To use the SSH protocol, select the <span class="guilabel"><strong>SSH</strong></span> radio button, and fill the <span class="guilabel"><strong>Server name</strong></span>, <span class="guilabel"><strong>Path to directory</strong></span>, and <span class="guilabel"><strong>User name</strong></span> fields with the remote server address, target directory, and a valid remote user name respectively. Refer to <a class="xref" href="#ch-OpenSSH">10章<em>OpenSSH</em></a> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ </div><a id="idm92449104" class="indexterm"></a><div class="para">
+ For a complete list of currently supported targets, see <a class="xref" href="#tab-kdump-supported_targets">表23.1「Supported kdump targets」</a>.
+ </div><div class="table" id="tab-kdump-supported_targets"><h6>表23.1 Supported kdump targets</h6><div class="table-contents"><table summary="Supported kdump targets" border="1"><colgroup><col width="20%" class="type" /><col width="40%" class="supported" /><col width="40%" class="unsupported" /></colgroup><thead><tr><th class="">
+ タイプ（Type）
+ </th><th class="">
+ Supported Targets
+ </th><th class="">
+ Unsupported Targets
+ </th></tr></thead><tbody><tr><td class="" valign="middle">
+ Raw device
+ </td><td class="">
+ All locally attached raw disks and partitions.
+ </td><td class="">
+ —
+ </td></tr><tr><td class="" valign="middle">
+ Local file system
+ </td><td class="">
+ <code class="systemitem">ext2</code>, <code class="systemitem">ext3</code>, <code class="systemitem">ext4</code>, <code class="systemitem">minix</code> file systems on directly attached disk drives, hardware RAID logical drives, LVM devices, and <code class="systemitem">mdraid</code> arrays.
+ </td><td class="">
+ The <code class="systemitem">eCryptfs</code> file system.
+ </td></tr><tr><td class="" rowspan="7" valign="middle">
+ Remote directory
+ </td><td class="">
+ Remote directories accessed using the <code class="systemitem">NFS</code> or <code class="systemitem">SSH</code> protocol over <code class="systemitem">IPv4</code>.
+ </td><td class="">
+ Remote directories on the <code class="systemitem">rootfs</code> file system accessed using the <code class="systemitem">NFS</code> protocol.
+ </td></tr><tr><td class="">
+ Remote directories accessed using the <code class="systemitem">iSCSI</code> protocol over hardware initiators.
+ </td><td class="">
+ Remote directories accessed using the <code class="systemitem">iSCSI</code> protocol over software initiators.
+ </td></tr><tr><td class="" rowspan="5">
+ —
+ </td><td class="">
+ Remote directories accessed over <code class="systemitem">IPv6</code>.
+ </td></tr><tr><td class="">
+ Remote directories accessed using the <code class="systemitem">SMB</code>/<code class="systemitem">CIFS</code> protocol.
+ </td></tr><tr><td class="">
+ Remote directories accessed using the <code class="systemitem">FCoE</code> (<em class="firstterm">Fibre Channel over Ethernet</em>) protocol.
+ </td></tr><tr><td class="">
+ Remote directories accessed using wireless network interfaces.
+ </td></tr><tr><td class="">
+ Multipath-based storages.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s3-kdump-configuration-gui-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.4. The Filtering Settings Tab</h4></div></div></div><a id="idm122576304" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Filtering Settings</strong></span> tab enables you to select the filtering level for the <code class="filename">vmcore</code> dump.
+ </div><div class="figure" id="fig-kdump-kernel_dump_configuration-filtering_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-filtering_settings.png" alt="Filtering Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Filtering Settings</strong></span>
+ </div></div></div></div><h6>図23.3 Filtering Settings</h6></div><br class="figure-break" /><div class="para">
+ To exclude the <span class="guilabel"><strong>zero page</strong></span>, <span class="guilabel"><strong>cache page</strong></span>, <span class="guilabel"><strong>cache private</strong></span>, <span class="guilabel"><strong>user data</strong></span>, or <span class="guilabel"><strong>free page</strong></span> from the dump, select the checkbox next to the appropriate label.
+ </div></div><div class="section" id="s3-kdump-configuration-gui-expert"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.5. The Expert Settings Tab</h4></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Expert Settings</strong></span> tab enables you to choose which kernel and initial RAM disk to use, as well as to customize the options that are passed to the kernel and the core collector program.
+ </div><div class="figure" id="fig-kdump-kernel_dump_configuration-expert_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-expert_settings.png" alt="Expert Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Expert Settings</strong></span>
+ </div></div></div></div><h6>図23.4 Expert Settings</h6></div><br class="figure-break" /><a id="idm126951232" class="indexterm"></a><div class="para">
+ To use a different initial RAM disk, select the <span class="guilabel"><strong>Custom initrd</strong></span> radio button, and choose the desired RAM disk from the pulldown list next to it.
+ </div><a id="idm124782176" class="indexterm"></a><div class="para">
+ To capture a different kernel, select the <span class="guilabel"><strong>Custom kernel</strong></span> radio button, and choose the desired kernel image from the pulldown list on the right.
+ </div><a id="idm91302560" class="indexterm"></a><div class="para">
+ To adjust the list of options that are passed to the kernel at boot time, edit the content of the <span class="guilabel"><strong>Edited</strong></span> text field. Note that you can always revert your changes by clicking the <span class="guibutton"><strong>Refresh</strong></span> button.
+ </div><a id="idm112819600" class="indexterm"></a><div class="para">
+ To choose what action to perform when <code class="systemitem">kdump</code> fails to create a core dump, select an appropriate option from the <span class="guilabel"><strong>Default action</strong></span> pulldown list. Available options are <span class="guimenuitem"><strong>mount rootfs and run /sbin/init</strong></span> (the default action), <span class="guimenuitem"><strong>reboot</strong></span> (to reboot the system), <span class="guimenuitem"><strong>shell</strong></span> (to present a user with an interactive shell prompt), <span class="guimenuitem"><strong>halt</strong></span> (to halt the system), and <span class="guimenuitem"><strong>poweroff</strong></span> (to power the system off).
+ </div><a id="idm126309952" class="indexterm"></a><div class="para">
+ To customize the options that are passed to the <code class="command">makedumpfile</code> core collector, edit the <span class="guilabel"><strong>Core collector</strong></span> text field; see <a class="xref" href="#s3-kdump-configuration-cli-filtering">「Configuring the Core Collector」</a> for more information.
+ </div></div></div><div class="section" id="s2-kdump-configuration-cli"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.2.3. Configuring kdump on the Command Line</h3></div></div></div><div class="section" id="s3-kdump-configuration-cli-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.1. Configuring the Memory Usage</h4></div></div></div><a id="idm60896560" class="indexterm"></a><a id="idm116288000" class="indexterm"></a><a id="idm116285616" class="indexterm"></a><a id="idm133521968" class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel, as <code class="systemitem">root</code>, edit the <code class="filename">/etc/default/grub</code> file and add the <code class="option">crashkernel=<em class="replaceable"><code><size></code></em>M</code> (or <code class="option">crashkernel=auto</code>) parameter to the list of kernel options (the <code class="option">GRUB_CMDLINE_LINUX</code> line). For example, to reserve 128 MB of memory, use:
+ </div><pre class="programlisting">GRUB_CMDLINE_LINUX="<strong class="userinput"><code>crashkernel=128M</code></strong> quiet rhgb"</pre><div class="para">
+ Then update the configuration file for the GRUB 2 boot loader by typing 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="important"><div class="admonition_header"><h2>Make sure the system has enough memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_17.html#sect-Release_Notes-Hardware_Overview"><em class="citetitle">Hardware Overview</em></a> section of the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><em class="citetitle">Fedora 17 Release Notes</em></a>. When the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Using the crashkernel=auto parameter</h2></div><div class="admonition"><div class="para">
+ In Fedora 17, the <code class="option">crashkernel=auto</code> only reserves memory if the system has 4 GB of physical memory or more.
+ </div></div></div></div><div class="section" id="s3-kdump-configuration-cli-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.2. Configuring the Target Type</h4></div></div></div><a id="idm69285328" class="indexterm"></a><div class="para">
+ When a kernel crash is captured, the core dump can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol. Only one of these options can be set at the moment, and the default option is to store the <code class="filename">vmcore</code> file in the <code class="filename">/var/crash/</code> directory of the local file system. To change this, as <code class="systemitem">root</code>, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor and edit the options as described below.
+ </div><div class="para">
+ To change the local directory in which the core dump is to be saved, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#path /var/crash</code> line, and replace the value with a desired directory path. Optionally, if you wish to write the file to a different partition, follow the same procedure with the <code class="literal">#ext4 /dev/sda3</code> line as well, and change both the file system type and the device (a device name, a file system label, and UUID are all supported) accordingly. For example:
+ </div><pre class="programlisting">ext3 /dev/sda4
+path /usr/local/cores</pre><div class="para">
+ To write the dump directly to a device, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#raw /dev/sda5</code> line, and replace the value with a desired device name. For example:
+ </div><pre class="programlisting">raw /dev/sdb1</pre><div class="para">
+ To store the dump to a remote machine using the NFS protocol, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#net my.server.com:/export/tmp</code> line, and replace the value with a valid hostname and directory path. For example:
+ </div><pre class="programlisting">net penguin.example.com:/export/cores</pre><div class="para">
+ To store the dump to a remote machine using the SSH protocol, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#net user at my.server.com</code> line, and replace the value with a valid username and hostname. For example:
+ </div><pre class="programlisting">net john at penguin.example.com</pre><div class="para">
+ Refer to <a class="xref" href="#ch-OpenSSH">10章<em>OpenSSH</em></a> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ </div><a id="idm138067568" class="indexterm"></a><div class="para">
+ For a complete list of currently supported targets, see <a class="xref" href="#tab-kdump-supported_targets">表23.1「Supported kdump targets」</a>.
+ </div></div><div class="section" id="s3-kdump-configuration-cli-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.3. Configuring the Core Collector</h4></div></div></div><div class="para">
+ To reduce the size of the <code class="filename">vmcore</code> dump file, <code class="systemitem">kdump</code> allows you to specify an external application (that is, a core collector) to compress the data, and optionally leave out all irrelevant information. Currently, the only fully supported core collector is <code class="command">makedumpfile</code>.
+ </div><div class="para">
+ To enable the core collector, as <code class="systemitem">root</code>, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#core_collector makedumpfile -c --message-level 1 -d 31</code> line, and edit the command line options as described below.
+ </div><a id="idm130524496" class="indexterm"></a><div class="para">
+ To enable the dump file compression, add the <code class="option">-c</code> parameter. For example:
+ </div><pre class="programlisting">core_collector makedumpfile -c</pre><a id="idm117879056" class="indexterm"></a><div class="para">
+ To remove certain pages from the dump, add the <code class="option">-d <em class="replaceable"><code>value</code></em></code> parameter, where <em class="replaceable"><code>value</code></em> is a sum of values of pages you want to omit as described in <a class="xref" href="#table-kdump-configuration-cli-filtering-makedumpfile">表23.2「Supported filtering levels」</a>. For example, to remove both zero and free pages, use the following:
+ </div><pre class="programlisting">core_collector makedumpfile -d 17 -c</pre><div class="para">
+ Refer to the manual page for <code class="command">makedumpfile</code> for a complete list of available options.
+ </div><div class="table" id="table-kdump-configuration-cli-filtering-makedumpfile"><h6>表23.2 Supported filtering levels</h6><div class="table-contents"><table summary="Supported filtering levels" border="1"><colgroup><col width="20%" class="option" /><col width="80%" class="description" /></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">1</code>
+ </td><td class="">
+ Zero pages
+ </td></tr><tr><td class="">
+ <code class="option">2</code>
+ </td><td class="">
+ Cache pages
+ </td></tr><tr><td class="">
+ <code class="option">4</code>
+ </td><td class="">
+ Cache private
+ </td></tr><tr><td class="">
+ <code class="option">8</code>
+ </td><td class="">
+ User pages
+ </td></tr><tr><td class="">
+ <code class="option">16</code>
+ </td><td class="">
+ Free pages
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s3-kdump-configuration-cli-action"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.4. Changing the Default Action</h4></div></div></div><a id="idm123374400" class="indexterm"></a><div class="para">
+ By default, when <code class="systemitem">kdump</code> fails to create a core dump, the root file system is mounted and <code class="command">/sbin/init</code> is run. To change this behavior, as <code class="systemitem">root</code>, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#default shell</code> line, and replace the value with a desired action as described in <a class="xref" href="#table-kdump-configuration-cli-action-actions">表23.3「Supported actions」</a>.
+ </div><div class="table" id="table-kdump-configuration-cli-action-actions"><h6>表23.3 Supported actions</h6><div class="table-contents"><table summary="Supported actions" border="1"><colgroup><col width="20%" class="option" /><col width="80%" class="description" /></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">reboot</code>
+ </td><td class="">
+ Reboot the system, losing the core in the process.
+ </td></tr><tr><td class="">
+ <code class="option">halt</code>
+ </td><td class="">
+ Halt the system.
+ </td></tr><tr><td class="">
+ <code class="option">poweroff</code>
+ </td><td class="">
+ Power off the system.
+ </td></tr><tr><td class="">
+ <code class="option">shell</code>
+ </td><td class="">
+ Run the <span class="application"><strong>msh</strong></span> session from within the initramfs, allowing a user to record the core manually.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ 例えば:
+ </div><pre class="programlisting">default halt</pre></div><div class="section" id="s3-kdump-configuration-cli-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.5. サービスの有効化</h4></div></div></div><a id="idm108838976" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, 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">enable</code> <code class="option">kdump.service</code></pre><div class="para">
+ Similarly, typing <code class="command">systemctl disable kdump.service</code> will disable it. To start the service in the current session, use the following command as <code class="systemitem">root</code>:
+ </div><a id="idm133102352" class="indexterm"></a><pre class="synopsis"><code class="command">systemctl</code> <code class="option">start</code> <code class="option">kdump.service</code></pre><div class="para">
+ For more information on services and their configuration, refer to <a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a>.
+ </div></div></div><div class="section" id="s2-kdump-configuration-testing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.2.4. Testing the Configuration</h3></div></div></div><a id="idm133459472" class="indexterm"></a><div class="warning"><div class="admonition_header"><h2>Be careful when using these commands</h2></div><div class="admonition"><div class="para">
+ The commands below will cause the kernel to crash. Use caution when following these steps, and by no means use them on a production machine.
+ </div></div></div><div class="para">
+ To test the configuration, reboot the system with <code class="systemitem">kdump</code> enabled, and make sure that the service is running (refer to <a class="xref" href="#s1-services-running">「サービスの実行」</a> for more information on how to run a service in Fedora):
+ </div><pre class="screen"><code class="command">systemctl is-active kdump.service</code></pre><div class="para">
+ Then type the following commands at a shell prompt:
+ </div><pre class="screen"><code class="command">echo 1 > /proc/sys/kernel/sysrq</code>
+<code class="command">echo c > /proc/sysrq-trigger</code></pre><div class="para">
+ This will force the Linux kernel to crash, and the <code class="filename"><em class="replaceable"><code>address</code></em>-<em class="replaceable"><code>YYYY-MM-DD</code></em>-<em class="replaceable"><code>HH:MM:SS</code></em>/vmcore</code> file will be copied to the location you have selected in the configuration (that is, to <code class="filename">/var/crash/</code> by default).
+ </div></div></div><div class="section" id="s1-kdump-crash"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">23.3. Analyzing the Core Dump</h2></div></div></div><a id="idm131616400" class="indexterm"></a><div class="para">
+ To determine the cause of the system crash, you can use the <span class="application"><strong>crash</strong></span> utility, which provides an interactive prompt very similar to the GNU Debugger (GDB). This utility allows you to interactively analyze a running Linux system as well as a core dump created by <code class="systemitem">netdump</code>, <code class="systemitem">diskdump</code>, <code class="systemitem">xendump</code>, or <code class="systemitem">kdump</code>.
+ </div><a id="idm112889424" class="indexterm"></a><div class="note"><div class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div class="admonition"><div class="para">
+ To analyze the <code class="filename">vmcore</code> dump file, you must have the <span class="package">crash</span> and <span class="package">kernel-debuginfo</span> packages installed. To install these packages, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install crash</code>
+<code class="command">debuginfo-install kernel</code></pre><div class="para">
+ For more information on how to install new packages in Fedora, refer to <a class="xref" href="#sec-Installing">「パッケージのインストール」</a>.
+ </div></div></div><div class="section" id="s2-kdump-crash-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.1. Running the crash Utility</h3></div></div></div><a id="idm87901200" class="indexterm"></a><div class="para">
+ To start the utility, type the command in the following form at a shell prompt:
+ </div><pre class="synopsis"><code class="command">crash</code> <code class="filename">/var/crash/<em class="replaceable"><code>timestamp</code></em>/vmcore</code> <code class="filename">/usr/lib/debug/lib/modules/<em class="replaceable"><code>kernel</code></em>/vmlinux</code></pre><div class="para">
+ Note that the <em class="replaceable"><code>kernel</code></em> version should be the same that was captured by <code class="systemitem">kdump</code>. To find out which kernel you are currently running, use the <code class="command">uname -r</code> command.
+ </div><div class="example" id="ex-kdump-crash-running"><h6>例23.1 Running the crash utility</h6><div class="example-contents"><pre class="screen">~]# <code class="command">crash /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux \</code>
+<code class="command">/var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore</code>
+
+crash 5.0.0-23.el6
+Copyright (C) 2002-2010 Red Hat, Inc.
+Copyright (C) 2004, 2005, 2006 IBM Corporation
+Copyright (C) 1999-2006 Hewlett-Packard Co
+Copyright (C) 2005, 2006 Fujitsu Limited
+Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
+Copyright (C) 2005 NEC Corporation
+Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
+Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
+This program is free software, covered by the GNU General Public License,
+and you are welcome to change it and/or distribute copies of it under
+certain conditions. Enter "help copying" to see the conditions.
+This program has absolutely no warranty. Enter "help warranty" for details.
+
+GNU gdb (GDB) 7.0
+Copyright (C) 2009 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law. Type "show copying"
+and "show warranty" for details.
+This GDB was configured as "i686-pc-linux-gnu"...
+
+ KERNEL: /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux
+ DUMPFILE: /var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore [PARTIAL DUMP]
+ CPUS: 4
+ DATE: Wed Aug 25 08:44:47 2010
+ UPTIME: 00:09:02
+LOAD AVERAGE: 0.00, 0.01, 0.00
+ TASKS: 140
+ NODENAME: hp-dl320g5-02.lab.bos.redhat.com
+ RELEASE: 2.6.32-69.el6.i686
+ VERSION: #1 SMP Tue Aug 24 10:31:45 EDT 2010
+ MACHINE: i686 (2394 Mhz)
+ MEMORY: 8 GB
+ PANIC: "Oops: 0002 [#1] SMP " (check log for details)
+ PID: 5591
+ COMMAND: "bash"
+ TASK: f196d560 [THREAD_INFO: ef4da000]
+ CPU: 2
+ STATE: TASK_RUNNING (PANIC)
+
+crash></pre></div></div><br class="example-break" /></div><div class="section" id="s2-kdump-crash-log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.2. Displaying the Message Buffer</h3></div></div></div><a id="idm116365872" class="indexterm"></a><div class="para">
+ To display the kernel message buffer, type the <code class="command">log</code> command at the interactive prompt.
+ </div><div class="example" id="ex-kdump-crash-log"><h6>例23.2 Displaying the kernel message buffer</h6><div class="example-contents"><pre class="screen">crash> <code class="command">log</code>
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+EIP: 0060:[<c068124f>] EFLAGS: 00010096 CPU: 2
+EIP is at sysrq_handle_crash+0xf/0x20
+EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000
+ESI: c0a09ca0 EDI: 00000286 EBP: 00000000 ESP: ef4dbf24
+ DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
+Process bash (pid: 5591, ti=ef4da000 task=f196d560 task.ti=ef4da000)
+Stack:
+ c068146b c0960891 c0968653 00000003 00000000 00000002 efade5c0 c06814d0
+<0> fffffffb c068150f b7776000 f2600c40 c0569ec4 ef4dbf9c 00000002 b7776000
+<0> efade5c0 00000002 b7776000 c0569e60 c051de50 ef4dbf9c f196d560 ef4dbfb4
+Call Trace:
+ [<c068146b>] ? __handle_sysrq+0xfb/0x160
+ [<c06814d0>] ? write_sysrq_trigger+0x0/0x50
+ [<c068150f>] ? write_sysrq_trigger+0x3f/0x50
+ [<c0569ec4>] ? proc_reg_write+0x64/0xa0
+ [<c0569e60>] ? proc_reg_write+0x0/0xa0
+ [<c051de50>] ? vfs_write+0xa0/0x190
+ [<c051e8d1>] ? sys_write+0x41/0x70
+ [<c0409adc>] ? syscall_call+0x7/0xb
+Code: a0 c0 01 0f b6 41 03 19 d2 f7 d2 83 e2 03 83 e0 cf c1 e2 04 09 d0 88 41 03 f3 c3 90 c7 05 c8 1b 9e c0 01 00 00 00 0f ae f8 89 f6 <c6> 05 00 00 00 00 01 c3 89 f6 8d bc 27 00 00 00 00 8d 50 d0 83
+EIP: [<c068124f>] sysrq_handle_crash+0xf/0x20 SS:ESP 0068:ef4dbf24
+CR2: 0000000000000000</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help log</code> for more information on the command usage.
+ </div></div><div class="section" id="s2-kdump-crash-backtrace"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.3. Displaying a Backtrace</h3></div></div></div><a id="idm111560528" class="indexterm"></a><div class="para">
+ To display the kernel stack trace, type the <code class="command">bt</code> command at the interactive prompt. You can use <code class="command">bt <em class="replaceable"><code>pid</code></em></code> to display the backtrace of the selected process.
+ </div><div class="example" id="ex-kdump-crash-backtrace"><h6>例23.3 Displaying the kernel stack trace</h6><div class="example-contents"><pre class="screen">crash> <code class="command">bt</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ #0 [ef4dbdcc] crash_kexec at c0494922
+ #1 [ef4dbe20] oops_end at c080e402
+ #2 [ef4dbe34] no_context at c043089d
+ #3 [ef4dbe58] bad_area at c0430b26
+ #4 [ef4dbe6c] do_page_fault at c080fb9b
+ #5 [ef4dbee4] error_code (via page_fault) at c080d809
+ EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000 EBP: 00000000
+ DS: 007b ESI: c0a09ca0 ES: 007b EDI: 00000286 GS: 00e0
+ CS: 0060 EIP: c068124f ERR: ffffffff EFLAGS: 00010096
+ #6 [ef4dbf18] sysrq_handle_crash at c068124f
+ #7 [ef4dbf24] __handle_sysrq at c0681469
+ #8 [ef4dbf48] write_sysrq_trigger at c068150a
+ #9 [ef4dbf54] proc_reg_write at c0569ec2
+#10 [ef4dbf74] vfs_write at c051de4e
+#11 [ef4dbf94] sys_write at c051e8cc
+#12 [ef4dbfb0] system_call at c0409ad5
+ EAX: ffffffda EBX: 00000001 ECX: b7776000 EDX: 00000002
+ DS: 007b ESI: 00000002 ES: 007b EDI: b7776000
+ SS: 007b ESP: bfcb2088 EBP: bfcb20b4 GS: 0033
+ CS: 0073 EIP: 00edc416 ERR: 00000004 EFLAGS: 00000246</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help bt</code> for more information on the command usage.
+ </div></div><div class="section" id="s2-kdump-crash-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.4. Displaying a Process Status</h3></div></div></div><a id="idm103347056" class="indexterm"></a><div class="para">
+ To display status of processes in the system, type the <code class="command">ps</code> command at the interactive prompt. You can use <code class="command">ps <em class="replaceable"><code>pid</code></em></code> to display the status of the selected process.
+ </div><div class="example" id="ex-kdump-crash-processes"><h6>例23.4 Displaying status of processes in the system</h6><div class="example-contents"><pre class="screen">crash> <code class="command">ps</code>
+ PID PPID CPU TASK ST %MEM VSZ RSS COMM
+> 0 0 0 c09dc560 RU 0.0 0 0 [swapper]
+> 0 0 1 f7072030 RU 0.0 0 0 [swapper]
+ 0 0 2 f70a3a90 RU 0.0 0 0 [swapper]
+> 0 0 3 f70ac560 RU 0.0 0 0 [swapper]
+ 1 0 1 f705ba90 IN 0.0 2828 1424 init
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+ 5566 1 1 f2592560 IN 0.0 12876 784 auditd
+ 5567 1 2 ef427560 IN 0.0 12876 784 auditd
+ 5587 5132 0 f196d030 IN 0.0 11064 3184 sshd
+> 5591 5587 2 f196d560 RU 0.0 5084 1648 bash</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help ps</code> for more information on the command usage.
+ </div></div><div class="section" id="s2-kdump-crash-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.5. Displaying Virtual Memory Information</h3></div></div></div><a id="idm121132448" class="indexterm"></a><div class="para">
+ To display basic virtual memory information, type the <code class="command">vm</code> command at the interactive prompt. You can use <code class="command">vm <em class="replaceable"><code>pid</code></em></code> to display information on the selected process.
+ </div><div class="example" id="ex-kdump-crash-memory"><h6>例23.5 Displaying virtual memory information of the current context</h6><div class="example-contents"><pre class="screen">crash> <code class="command">vm</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ MM PGD RSS TOTAL_VM
+f19b5900 ef9c6000 1648k 5084k
+ VMA START END FLAGS FILE
+f1bb0310 242000 260000 8000875 /lib/ld-2.12.so
+f26af0b8 260000 261000 8100871 /lib/ld-2.12.so
+efbc275c 261000 262000 8100873 /lib/ld-2.12.so
+efbc2a18 268000 3ed000 8000075 /lib/libc-2.12.so
+efbc23d8 3ed000 3ee000 8000070 /lib/libc-2.12.so
+efbc2888 3ee000 3f0000 8100071 /lib/libc-2.12.so
+efbc2cd4 3f0000 3f1000 8100073 /lib/libc-2.12.so
+efbc243c 3f1000 3f4000 100073
+efbc28ec 3f6000 3f9000 8000075 /lib/libdl-2.12.so
+efbc2568 3f9000 3fa000 8100071 /lib/libdl-2.12.so
+efbc2f2c 3fa000 3fb000 8100073 /lib/libdl-2.12.so
+f26af888 7e6000 7fc000 8000075 /lib/libtinfo.so.5.7
+f26aff2c 7fc000 7ff000 8100073 /lib/libtinfo.so.5.7
+efbc211c d83000 d8f000 8000075 /lib/libnss_files-2.12.so
+efbc2504 d8f000 d90000 8100071 /lib/libnss_files-2.12.so
+efbc2950 d90000 d91000 8100073 /lib/libnss_files-2.12.so
+f26afe00 edc000 edd000 4040075
+f1bb0a18 8047000 8118000 8001875 /bin/bash
+f1bb01e4 8118000 811d000 8101873 /bin/bash
+f1bb0c70 811d000 8122000 100073
+f26afae0 9fd9000 9ffa000 100073
+<span class="emphasis"><em>... several lines omitted ...</em></span></pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help vm</code> for more information on the command usage.
+ </div></div><div class="section" id="s2-kdump-crash-files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.6. Displaying Open Files</h3></div></div></div><a id="idm99305712" class="indexterm"></a><div class="para">
+ To display information about open files, type the <code class="command">files</code> command at the interactive prompt. You can use <code class="command">files <em class="replaceable"><code>pid</code></em></code> to display files opened by the selected process.
+ </div><div class="example" id="ex-kdump-crash-files"><h6>例23.6 Displaying information about open files of the current context</h6><div class="example-contents"><pre class="screen">crash> <code class="command">files</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ROOT: / CWD: /root
+ FD FILE DENTRY INODE TYPE PATH
+ 0 f734f640 eedc2c6c eecd6048 CHR /pts/0
+ 1 efade5c0 eee14090 f00431d4 REG /proc/sysrq-trigger
+ 2 f734f640 eedc2c6c eecd6048 CHR /pts/0
+ 10 f734f640 eedc2c6c eecd6048 CHR /pts/0
+255 f734f640 eedc2c6c eecd6048 CHR /pts/0</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help files</code> for more information on the command usage.
+ </div></div><div class="section" id="s2-kdump-crash-exit"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.7. Exiting the Utility</h3></div></div></div><div class="para">
+ To exit the interactive prompt and terminate <span class="application"><strong>crash</strong></span>, type <code class="command">exit</code> or <code class="command">q</code>.
+ </div><div class="example" id="ex-kdump-crash-exit"><h6>例23.7 Exiting the crash utility</h6><div class="example-contents"><pre class="screen">crash> <code class="command">exit</code>
+~]#</pre></div></div><br class="example-break" /></div></div><div class="section" id="s1-kdump-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">23.4. その他のリソース</h2></div></div></div><div class="section" id="s2-kdump-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.4.1. インストールされているドキュメント</h3></div></div></div><a id="idm81288336" class="indexterm"></a><a id="idm93090624" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>kdump.conf</strong></span>(5) — a manual page for the <code class="filename">/etc/kdump.conf</code> configuration file containing the full documentation of available options.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>makedumpfile</strong></span>(8) — a manual page for the <code class="command">makedumpfile</code> core collector.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>kexec</strong></span>(8) — a manual page for <span class="application"><strong>kexec</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>crash</strong></span>(8) — a manual page for the <span class="application"><strong>crash</strong></span> utility.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kexec-tools-<em class="replaceable"><code>version</code></em>/kexec-kdump-howto.txt</code> — an overview of the <code class="systemitem">kdump</code> and <span class="application"><strong>kexec</strong></span> installation and usage.
+ </div></li></ul></div></div><div class="section" id="s2-kdump-resources-online"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.4.2. 役に立つ Web サイト</h3></div></div></div><a id="idm130981568" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="https://access.redhat.com/kb/docs/DOC-6039">https://access.redhat.com/kb/docs/DOC-6039</a></span></dt><dd><div class="para">
+ The Red Hat Knowledgebase article about the <code class="command">kexec</code> and <code class="systemitem">kdump</code> configuration.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="https://access.redhat.com/kb/docs/DOC-45183">https://access.redhat.com/kb/docs/DOC-45183</a></span></dt><dd><div class="para">
+ The Red Hat Knowledgebase article about supported <code class="systemitem">kdump</code> targets.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://people.redhat.com/anderson/">http://people.redhat.com/anderson/</a></span></dt><dd><div class="para">
+ The <span class="application"><strong>crash</strong></span> utility homepage.
+ </div></dd></dl></div></div></div></div></div><div xml:lang="ja-JP" class="appendix" id="appe-Consistent_Network_Device_Naming" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">Consistent Network Device Naming</h1></div></div></div><div class="para">
+ Fedora 17 provides consistent network device naming for network interfaces. This feature changes the name of network interfaces on a system in order to make locating and differentiating the interfaces easier.
+ </div><div class="para">
+ Traditionally, network interfaces in Linux are enumerated as <code class="interfacename">eth[0123…]</code>, but these names do not necessarily correspond to actual labels on the chassis. Modern server platforms with multiple network adapters can encounter non-deterministic and counter-intuitive naming of these interfaces. This affects both network adapters embedded on the motherboard (<em class="firstterm">Lan-on-Motherboard</em>, or <em class="firstterm"><acronym class="acronym">LOM</acronym></em>) and add-in (single and multiport) adapters.
+ </div><div class="para">
+ The new naming convention assigns names to network interfaces based on their physical location, whether embedded or in PCI slots. By converting to this naming convention, system administrators will no longer have to guess at the physical location of a network port, or modify each system to rename them into some consistent order.
+ </div><div class="para">
+ This feature, implemented via the <span class="application"><strong>biosdevname</strong></span> program, will change the name of all embedded network interfaces, PCI card network interfaces, and virtual function network interfaces from the existing <code class="interfacename">eth[0123…]</code> to the new naming convention as shown in <a class="xref" href="#tabl-Consistent_Network_Device_Naming">表A.1「The new naming convention」</a>.
+ </div><div class="table" id="tabl-Consistent_Network_Device_Naming"><h6>表A.1 The new naming convention</h6><div class="table-contents"><table summary="The new naming convention" border="1"><colgroup><col width="35%" class="device" /><col width="15%" class="old" /><col width="50%" class="new" /></colgroup><thead><tr><th class="">
+ デバイス（Device）
+ </th><th class="">
+ Old Name
+ </th><th class="">
+ New Name
+ </th></tr></thead><tbody><tr><td class="">
+ Embedded network interface (LOM)
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">em[1234…]</code><a href="#ftn.idm102239776" class="footnote"><sup class="footnote" id="idm102239776">[a]</sup></a>
+ </td></tr><tr><td class="">
+ PCI card network interface
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">p<<em class="replaceable"><code>slot</code></em>>p<<em class="replaceable"><code>ethernet port</code></em>></code><a href="#ftn.idm134214544" class="footnote"><sup class="footnote" id="idm134214544">[b]</sup></a>
+ </td></tr><tr><td class="">
+ Virtual function
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">p<<em class="replaceable"><code>slot</code></em>>p<<em class="replaceable"><code>ethernet port</code></em>>_<<em class="replaceable"><code>virtual interface</code></em>></code><a href="#ftn.idm94447680" class="footnote"><sup class="footnote" id="idm94447680">[c]</sup></a>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div id="ftn.idm102239776" class="footnote"><div class="para"><a href="#idm102239776" class="para"><sup class="para">[a] </sup></a>
+ New enumeration starts at <code class="literal">1</code>.
+ </div></div><div id="ftn.idm134214544" class="footnote"><div class="para"><a href="#idm134214544" class="para"><sup class="para">[b] </sup></a>
+ For example: <code class="interfacename">p3p4</code>
+ </div></div><div id="ftn.idm94447680" class="footnote"><div class="para"><a href="#idm94447680" class="para"><sup class="para">[c] </sup></a>
+ For example: <code class="interfacename">p3p4_1</code>
+ </div></div></td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ System administrators may continue to write rules in <code class="filename">/etc/udev/rules.d/70-persistent-net.rules</code> to change the device names to anything desired; those will take precedence over this physical location naming convention.
+ </div><div class="section" id="sect-Consistent_Network_Device_Naming-Affected_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.1. Affected Systems</h2></div></div></div><div class="para">
+ Consistent network device naming is enabled by default for all systems that meet the requirements in <a class="xref" href="#sect-Consistent_Network_Device_Naming-System_Requirements">「システム要求」</a>.
+ </div><div class="para">
+ Regardless of the type of system, Fedora guests will not have devices renamed unless the virtual machine BIOS provides the SMBIOS information outlined in <a class="xref" href="#sect-Consistent_Network_Device_Naming-System_Requirements">「システム要求」</a>. Also, upgrades from prior releases that did not use this naming convention (that is, Fedora 14 and older) are unaffected, and the old naming convention will continue to be used.
+ </div></div><div class="section" id="sect-Consistent_Network_Device_Naming-System_Requirements"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.2. システム要求</h2></div></div></div><div class="para">
+ The <span class="application"><strong>biosdevname</strong></span> program uses information from the system's BIOS, specifically the <span class="emphasis"><em>type 9</em></span> (System Slot) and <span class="emphasis"><em>type 41</em></span> (Onboard Devices Extended Information) fields contained within the SMBIOS. If the system's BIOS does not have SMBIOS version 2.6 or higher and this data, the new naming convention will not be used. Most older hardware does not support this feature because of a lack of BIOSes with the correct SMBIOS version and field information. For BIOS or SMBIOS version information, contact your hardware vendor.
+ </div><div class="para">
+ For this feature to take effect, the <span class="package">biosdevname</span> package must also be installed. The <span class="package">biosdevname</span> package is part of the <code class="literal">base</code> package group in Fedora 17. All install options, except for <span class="guimenuitem"><strong>Minimal Install</strong></span>, include this package.
+ </div></div><div class="section" id="sect-Consistent_Network_Device_Naming-Enabling_and_Disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.3. Enabling and Disabling the Feature</h2></div></div></div><div class="para">
+ To disable the consistent network device naming on Dell systems that would normally have it on by default, pass the following option on the boot command line, both during and after installation:
+ </div><pre class="screen"><code class="option">biosdevname=0</code></pre><div class="para">
+ To enable this feature on other system types that meet the minimum requirements (see <a class="xref" href="#sect-Consistent_Network_Device_Naming-System_Requirements">「システム要求」</a>), pass the following option on the boot command line, both during and after installation:
+ </div><pre class="screen"><code class="option">biosdevname=1</code></pre><div class="para">
+ Unless the system meets the minimum requirements, this option will be ignored and the system will boot with the traditional network interface name format.
+ </div><div class="para">
+ If the <code class="option">biosdevname</code> install option is specified, it must remain as a boot option for the lifetime of the system.
+ </div></div><div class="section" id="sect-Consistent_Network_Device_Naming-Notes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.4. Notes for Administrators</h2></div></div></div><div class="para">
+ Many system customization files can include network interface names, and thus will require updates if moving a system from the old convention to the new convention. If you use the new naming convention, you will also need to update network interface names in areas such as custom iptables rules, scripts altering irqbalance, and other similar configuration files. Also, enabling this change for installation will require modification to existing kickstart files that use device names via the <code class="option">ksdevice</code> parameter; these kickstart files will need to be updated to use the network device's MAC address or the network device's new name.
+ </div><div class="para">
+ The Fedora Project strongly recommends that you consider this feature to be an install-time choice; enabling or disabling the feature post-install, while technically possible, can be complicated and is not recommended. For those system administrators who wish to do so, on a system that meets the minimum requirements, remove the <code class="filename">/etc/udev/rules.d/70-persistent-net.rules</code> file and the <code class="option">HWADDR</code> lines from all <code class="filename">/etc/sysconfig/network-scripts/ifcfg-*</code> files. In addition, rename those <code class="filename">ifcfg-*</code> files to use this new naming convention. The new names will be in effect after reboot. Remember to update any custom scripts, iptables rules, and service configuration files that might include network interface names.
+ </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="idm61531216" class="indexterm"></a><a id="idm61531984" class="indexterm"></a><div class="para">
+ The <em class="firstterm">RPM Package Manager</em> (RPM) is an open packaging system
+ <a id="idm61533552" class="indexterm"></a>
+ , which runs on Fedora as well as other Linux and UNIX systems. Red Hat, Inc. and the Fedora Project encourage other vendors to use RPM for their own products. RPM 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 RPM Package Manager only works with packages built to work with the <span class="emphasis"><em>RPM format</em></span>. RPM is itself provided as a pre-installed <span class="package">rpm</span> package. For the end user, RPM makes system updates easy. Installing, uninstalling and upgrading RPM packages can be accomplished with short commands. RPM maintains a database of installed packages and their files, so you can invoke powerful queries and verifications on your system.
+ </div><div class="para">
+ The RPM package format has been improved for Fedora 17. RPM packages are now compressed using the XZ lossless data compression format, which has the benefit of greater compression and less CPU usage during decompression, and support multiple strong hash algorithms, such as SHA-256, for package signing and verification.
+ </div><div class="warning" id="warning-Use_Yum_Instead_of_RPM_Whenever_Possible"><div class="admonition_header"><h2>Use Yum Instead of RPM Whenever Possible</h2></div><div class="admonition"><div class="para">
+ For most package management tasks, the <span class="application"><strong>Yum</strong></span> package manager offers equal and often greater capabilities and utility than RPM
+ <a id="idm120049664" class="indexterm"></a>
+ . <span class="application"><strong>Yum</strong></span> also performs and tracks complicated system dependency resolution, and will complain and force system integrity checks if you use RPM as well to install and remove packages. For these reasons, it is highly recommended that you use <span class="application"><strong>Yum</strong></span> instead of RPM whenever possible to perform package management tasks. Refer to <a class="xref" href="#ch-yum">4章<em>Yum</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>Yum</strong></span> as its back end, to manage your system's packages. Refer to <a class="xref" href="#ch-PackageKit">5章<em>PackageKit</em></a> for details.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Install RPM packages with the correct architecture!</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. Many of the following examples show RPM packages compiled for the AMD64/Intel 64 computer architectures; thus, the RPM file name ends in <code class="filename">x86_64.rpm</code>.
+ </div></div></div><div class="para">
+ During upgrades, RPM 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><div class="para">
+ For the developer, RPM allows you to take software source code and package it into source and binary packages for end users.
+ <a id="idm75945888" class="indexterm"></a>
+ This process is quite simple and is driven from a single file and optional patches that you create. This clear delineation between <em class="firstterm">pristine</em> 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"><div class="admonition_header"><h2>Running rpm commands must be performed as root</h2></div><div class="admonition"><div class="para">
+ Because RPM makes changes to your system, you must be logged in as root to install, remove, or upgrade an RPM package.
+ </div></div></div><div class="section" id="s1-rpm-design"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.1. RPM の設計目標</h2></div></div></div><a id="idm58218368" class="indexterm"></a><div class="para">
+ To understand how to use RPM, it can be helpful to understand the design goals of RPM:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Upgradability
+ <a id="idm58221104" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ With RPM, you can upgrade individual components of your system without completely reinstalling. When you get a new release of an operating system based on RPM, such as Fedora, you do not need to reinstall a fresh copy of the operating system your machine (as you might need to with operating systems based on other packaging systems). RPM allows 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 RPM file is used to both install and upgrade the package on your system.
+ </div></dd><dt class="varlistentry"><span class="term">Powerful Querying
+ <a id="idm81964352" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ RPM is designed to provide powerful querying options. You can perform searches on your entire database for packages or even just certain files. You can also easily find out what package a file belongs to and from where the package came. The files an RPM 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"> System Verification
+ <a id="idm120053520" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Another powerful RPM feature is the ability to verify packages. If you are worried that you deleted an important file for some package, you can verify the package. You are then notified of anomalies, if any—at which point 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">Pristine Sources
+ <a id="idm125491120" class="indexterm"></a>
+ </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 RPM, 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, too.
+ </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">B.2. RPMの使用法</h2></div></div></div><div class="para">
+ RPM has five basic modes of operation
+ <a id="idm48574560" 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 <code class="command">man rpm</code>. You can also refer to <a class="xref" href="#s1-rpm-additional-resources">「その他のリソース」</a> for more information on RPM.
+ </div><div class="section" id="s2-rpm-finding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.1. RPM パッケージの検索</h3></div></div></div><a id="idm96226896" class="indexterm"></a><a id="idm75948832" class="indexterm"></a><div class="para">
+ Before using any RPM packages, you must know where to find them. An Internet search returns many RPM repositories, but if you are looking for Red Hat RPM packages, they can be found at the following locations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The Fedora installation media
+ <a id="idm72705696" class="indexterm"></a>
+ <a id="idp1683200" class="indexterm"></a>
+ contain many installable RPMs.
+ </div></li><li class="listitem"><div class="para">
+ The initial RPM repositories provided with the YUM package manager
+ <a id="idm77730480" class="indexterm"></a>
+ <a id="idm125927024" class="indexterm"></a>
+ . Refer to <a class="xref" href="#ch-yum">4章<em>Yum</em></a> for details on how to use the official Fedora package repositories.
+ </div></li><li class="listitem"><div class="para">
+ The active Fedora mirrors contains many installable RPMs: <a href="http://mirrors.fedoraproject.org/publiclist/">http://mirrors.fedoraproject.org/publiclist/</a>.
+ </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>Third-party repositories and package compatibility</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="sec-Installing_and_Upgrading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.2. インストールとアップグレード</h3></div></div></div><a id="idm114844288" class="indexterm"></a><a id="idm119308256" class="indexterm"></a><a id="idm132910272" class="indexterm"></a><a id="idm105134464" class="indexterm"></a><div class="para">
+ RPM packages typically have file names
+ <a id="idm69290384" class="indexterm"></a>
+ like <code class="filename">tree-1.5.3-2.fc17.x86_64.rpm</code>. The file name includes the package name (<code class="filename">tree</code>), version (<code class="filename">1.5.3</code>), release (<code class="filename">2</code>), operating system major version (<code class="filename">fc17</code>) and CPU architecture (<code class="filename">x86_64</code>).
+ </div><div class="para">
+ <code class="command">rpm</code> の <code class="option">-U</code> オプションを使用できます:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ upgrade an existing but older package on the system to a newer version, or
+ </div></li><li class="listitem"><div class="para">
+ install the package even if an older version is not already installed.
+ </div></li></ul></div><div class="para">
+ That is, <code class="command">rpm -U <em class="replaceable"><code><rpm_file></code></em> </code> is able to perform the function of either <span class="emphasis"><em>upgrading</em></span> or <span class="emphasis"><em>installing</em></span> as is appropriate for the package.
+ </div><div class="para">
+ Assuming the <code class="filename">tree-1.5.3-2.fc17.x86_64.rpm</code> package is in the current directory, log in as root and type the following command at a shell prompt to either upgrade or install the <span class="package">tree</span> package as determined by <code class="command">rpm</code>:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh tree-1.5.3-2.fc17.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">
+ 更新/インストールが成功すると、以下の出力が表示されます:
+ </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, historically standing for <span class="emphasis"><em>install</em></span>. Because the <code class="option">-U</code> option subsumes both install and upgrade functions, we recommend to use <code class="command">rpm -Uvh</code> with all packages <span class="emphasis"><em>except <span class="package">kernel</span> packages</em></span>.
+ </div><div class="para">
+ You should always use the <code class="option">-i</code> option to simply <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, refer to <a class="xref" href="#ch-Manually_Upgrading_the_Kernel">21章<em>カーネルをアップグレードする</em></a>.
+ </div></div></div><div class="para">
+ パッケージの署名は、パッケージのインストールまたはアップグレード時に自動的にチェックされます。署名により、パッケージが認証機関によって署名されたことを確認できます。たとえば、署名の検証が失敗すると、次のようなエラーメッセージが表示されます。
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc17.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID
+d22e77f2</pre><div class="para">
+ ヘッダのみの新しい署名なら、次のようなエラーメッセージが表示されます。
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc17.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD,
+key ID d22e77f2</pre><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.5.2.2-4.fc17.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba</pre><div class="para">
+ Refer to <a class="xref" href="#s1-check-rpm-sig">「パッケージの署名を確認する」</a> for more information on checking a package's signature.
+ </div><div class="section" id="s3-rpm-errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">B.2.2.1. すでにインストールされているパッケージ</h4></div></div></div><div class="para">
+ If a package of the same name and version is already installed
+ <a id="idm17043712" class="indexterm"></a>
+ <a id="idm68028096" class="indexterm"></a>
+ , the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ package tree-1.5.3-2.fc17.x86_64 is already installed</pre><div class="para">
+ However, if you want to install the package anyway, you can use the <code class="command">--replacepkgs</code> option, which tells RPM to ignore the error:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --replacepkgs tree-1.5.3-2.fc17.x86_64.rpm</code>
+</pre><div class="para">
+ このオプションは、RPM からインストールされた ファイルが削除された場合や、RPM からオリジナルの 設定ファイルをインストールしたい場合に便利です。
+ </div></div><div class="section" id="s3-rpm-conflicting-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">B.2.2.2. ファイルの競合</h4></div></div></div><a id="idm132907792" class="indexterm"></a><div class="para">
+ If you attempt to install a package that contains a file which has already been installed by another package
+ <a id="idm102504576" class="indexterm"></a>
+ <a id="idm113606736" class="indexterm"></a>
+ , the following is displayed:
+ </div><pre class="screen">Preparing... ##################################################
+ file /usr/bin/foobar from install of foo-1.0-1.fc17.x86_64 conflicts
+with file from package bar-3.1.1.fc17.x86_64</pre><div class="para">
+ To make RPM ignore this error, use the <code class="command">--replacefiles</code> option:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --replacefiles foo-1.0-1.fc17.x86_64.rpm</code>
+</pre></div><div class="section" id="s3-rpm-unresolved-dependency"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">B.2.2.3. 未解決の依存性</h4></div></div></div><a id="idm69201920" class="indexterm"></a><a id="idm60653296" class="indexterm"></a><div class="para">
+ RPM packages may sometimes depend on other packages
+ <a id="idm60651568" class="indexterm"></a>
+ <a id="idm126084480" class="indexterm"></a>
+ , which means that they require other packages to be installed to run properly. If you try to install a package which has an unresolved dependency, output similar to the following is displayed:
+ </div><pre class="screen">error: Failed dependencies:
+ bar.so.3()(64bit) is needed by foo-1.0-1.fc17.x86_64</pre><div class="para">
+ If you are installing a package from the Fedora installation media, such as from a CD-ROM or DVD, the dependencies may be available. Find the suggested package(s) on the Fedora installation media or on one of the active Fedora mirrors and add it to the command:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh foo-1.0-1.fc17.x86_64.rpm bar-3.1.1.fc17.x86_64.rpm</code>
+</pre><div class="para">
+ 両方のパッケージのインストールが正常に行なわれると、以下のような出力が表示されます。
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ 1:foo ########################################### [ 50%]
+ 2:bar ########################################### [100%]</pre><div class="para">
+ You can try the <code class="option">--whatprovides</code> option to determine which package contains the required file.
+ </div><pre class="screen">
+<code class="command">rpm -q --whatprovides "bar.so.3"</code>
+</pre><div class="para">
+ <code class="filename">bar.so.3</code> を含むパッケージが RPM データベースにあると、パッケージの名前が表示されます:
+ </div><pre class="screen">bar-3.1.1.fc17.i586.rpm</pre><div class="warning" id="warning-install-Warning-Forcing_Package_Installation"><div class="admonition_header"><h2>警告: 強制的なパッケージのインストール</h2></div><div class="admonition"><div class="para">
+ Although we can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to install a package that gives us a <code class="computeroutput">Failed dependencies</code> error (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 package failing to run. Installing or removing packages with <code class="command">rpm --nodeps</code> can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager—whether <span class="application"><strong>RPM</strong></span>, <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>—shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The <span class="application"><stron
g>Yum</strong></span> package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing <code class="command">rpm</code> to carry out actions without regard to resolving dependencies.
+ </div></div></div></div></div><div class="section" id="sec-Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.3. 設定ファイルの変更</h3></div></div></div><a id="idm133440544" class="indexterm"></a><a id="idm102192416" class="indexterm"></a><div class="para">
+ Because RPM performs intelligent upgrading of packages with configuration files
+ <a id="idm113570224" class="indexterm"></a>
+ , you may see one or the other of the following messages:
+ </div><pre class="screen">saving /etc/foo.conf as /etc/foo.conf.rpmsave</pre><div class="para">
+ This message means that 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 RPM 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, RPM may save the package's <span class="emphasis"><em>new</em></span> configuration file as, for example, <code class="filename">foo.conf.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 with a <code class="command">diff</code> program.
+ </div><div class="para">
+ If you attempt to upgrade to a package with an <span class="emphasis"><em>older</em></span> version number (that is, if a higher version of the package is already installed), the output is similar to the following:
+ </div><pre class="screen">package foo-2.0-1.fc17.x86_64.rpm (which is newer than foo-1.0-1) is already installed</pre><div class="para">
+ To force RPM to upgrade anyway, use the <code class="command">--oldpackage</code> option:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --oldpackage foo-1.0-1.fc17.x86_64.rpm</code>
+</pre></div><div class="section" id="s2-rpm-uninstalling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.4. アンインストール</h3></div></div></div><a id="idm99924448" class="indexterm"></a><a id="idm99923040" class="indexterm"></a><a id="idm20757200" class="indexterm"></a><a id="idm70564400" class="indexterm"></a><div class="para">
+ パッケージのアンインストールは、インストールと 同様、簡単に実行できます。シェルプロンプトで以下の コマンドを入力します。
+ </div><pre class="screen">rpm -e foo</pre><div class="note"><div class="admonition_header"><h2>rpm -e and package name errors</h2></div><div class="admonition"><div class="para">
+ Notice that we used the package <span class="emphasis"><em>name</em></span> <code class="filename">foo</code>, not the name of the original package <span class="emphasis"><em>file</em></span>, <code class="filename">foo-1.0-1.fc17.x86_64</code>. If you attempt to uninstall a package using the <code class="command">rpm -e</code> command and the original full file name, you will 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:
+ libgs.so.8()(64bit) is needed by (installed) libspectre-0.2.2-3.fc17.x86_64
+ libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc17.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc17.x86_64
+ ghostscript is needed by (installed) printer-filters-1.1-4.fc17.noarch</pre><div class="para">
+ Similar to how we searched for a shared object library (i.e. a <code class="filename"><em class="replaceable"><code><library_name></code></em>.so.<em class="replaceable"><code><number></code></em> </code> file) in <a class="xref" href="#s3-rpm-unresolved-dependency">「未解決の依存性」</a>, we can search for a 64-bit shared object library using this exact syntax (and making sure to quote the file name):
+ </div><pre class="screen">~]# <code class="command">rpm -q --whatprovides "libgs.so.8()(64bit)"</code>
+ghostscript-8.70-1.fc17.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 we can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to remove a package that gives us a <code class="computeroutput">Failed dependencies</code> error (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended, and may cause harm to other installed applications. Installing or removing packages with <code class="command">rpm --nodeps</code> can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager—whether <span class="application"><strong>RPM</strong></span>, <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>—shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The <span class="application"><strong>Yum</strong><
/span> package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing <code class="command">rpm</code> to carry out actions without regard to resolving 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">B.2.5. インストール済みのアップグレードの実行</h3></div></div></div><a id="idm85584160" class="indexterm"></a><a id="idm85582752" class="indexterm"></a><div class="para">
+ Freshening is similar to upgrading, except that only existent packages are upgraded. Type the following command at a shell prompt:
+ </div><pre class="screen">
+<code class="command">rpm -Fvh foo-2.0-1.fc17.x86_64.rpm</code>
+</pre><div class="para">
+ RPM's freshen option checks the versions of the packages specified on the command line against the versions of packages that have already been installed on your system. When a newer version of an already-installed package is processed by RPM's freshen option, it is upgraded to the newer version. However, RPM's freshen option does not install a package if no previously-installed package of the same name exists. This differs from RPM's upgrade option, as an upgrade <span class="emphasis"><em>does</em></span> install packages whether or not an older version of the package was already installed.
+ </div><div class="para">
+ Freshening works for single packages or package groups. If you have just downloaded a large number of different packages, and you only want to upgrade those packages that are already installed on your system, freshening does the job. Thus, you do not have to delete any unwanted packages from the group that you downloaded before using RPM.
+ </div><div class="para">
+ In this case, issue the following with the <code class="filename">*.rpm</code> glob:
+ </div><pre class="screen">
+<code class="command">rpm -Fvh *.rpm</code>
+</pre><div class="para">
+ RPM 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">B.2.6. 問い合わせ</h3></div></div></div><a id="idm99985184" class="indexterm"></a><a id="idm121124976" class="indexterm"></a><div class="para">
+ The RPM database stores information about all RPM packages installed in your system. It is stored in the directory <code class="filename">/var/lib/rpm/</code>, and is used to query what packages are installed, what versions each package is, and to calculate any changes to any files in the package since installation, among other use cases.
+ </div><div class="para">
+ To query this database, use the <code class="command">-q</code> option. The <code class="command">rpm -q <em class="replaceable"><code>package name</code></em> </code> command displays the package name, version, and release number of the installed package <em class="replaceable"><code><package_name></code></em>. For example, using <code class="command">rpm -q tree</code> to query installed package <code class="filename">tree</code> might generate the following output:
+ </div><pre class="screen">tree-1.5.2.2-4.fc17.x86_64</pre><div class="para">
+ You can also use the following <span class="emphasis"><em>Package Selection Options</em></span> (which is a subheading in the RPM man page: see <code class="command">man rpm</code> for details) to further refine or qualify your query:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-a</code> — 現在の全インストール済みパッケージの問い合わせです。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f <code class="filename"><em class="replaceable"><code><file_name></code></em> </code> </code> — queries the RPM database for which package owns <code class="filename"><em class="replaceable"><code><file_name></code></em> </code>. Specify the absolute path of the file (for example, <code class="command">rpm -qf <code class="filename">/bin/ls</code> </code> instead of <code class="command">rpm -qf ls</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-p <code class="filename"><em class="replaceable"><code><package_file></code></em> </code> </code> — queries the uninstalled package <code class="filename"><em class="replaceable"><code><package_file></code></em> </code>.
+ </div></li></ul></div><div class="para">
+ There are a number of ways to specify what information to display about queried packages. The following options are used to select the type of information for which you are searching. These are called the <span class="emphasis"><em>Package Query Options</em></span>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-i</code> displays package information including name, description, release, size, build date, install date, vendor, and other miscellaneous information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-l</code> displays the list of files that the package contains.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-s</code> displays the state of all the files in the package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> displays a list of files marked as documentation (man pages, info pages, READMEs, etc.) in the package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-c</code> displays a list of files marked as configuration files. These are the files you edit after installation to adapt and customize the package to your system (for example, <code class="filename">sendmail.cf</code>, <code class="filename">passwd</code>, <code class="filename">inittab</code>, etc.).
+ </div></li></ul></div><div class="para">
+ For options that display lists of files, add <code class="command">-v</code> to the command to display the lists in a familiar <code class="command">ls -l</code> format.
+ </div></div><div class="section" id="s2-rpm-verifying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.7. 検証</h3></div></div></div><a id="idm123118064" class="indexterm"></a><a id="idm123116624" class="indexterm"></a><div class="para">
+ Verifying a package compares information about files installed from a package with the same information from the original package. Among other things, verifying compares the file size, MD5 sum, permissions, type, owner, and group of each file.
+ </div><div class="para">
+ The command <code class="command">rpm -V</code> verifies a package. You can use any of the <span class="emphasis"><em>Verify Options</em></span> listed for querying to specify the packages you wish to verify. A simple use of verifying is <code class="command">rpm -V tree</code>, which verifies that all the files in the <code class="command">tree</code> package are as they were when they were originally installed. For example:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 特定のファイルを含むパッケージを検証するには、
+ </div><pre class="screen">
+<code class="command">rpm -Vf /usr/bin/tree</code>
+</pre><div class="para">
+ In this example, <code class="filename">/usr/bin/tree</code> is the absolute path to the file used to query a package.
+ </div></li><li class="listitem"><div class="para">
+ To verify ALL installed packages throughout the system (which will take some time):
+ </div><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre></li><li class="listitem"><div class="para">
+ インストールされているパッケージと、 RPM パッケージファイルとを検証するには、
+ </div><pre class="screen">
+<code class="command">rpm -Vp tree-1.5.2.2-4.fc17.x86_64.rpm</code>
+</pre><div class="para">
+ This command can be useful if you suspect that your RPM database is corrupt.
+ </div></li></ul></div><div class="para">
+ If everything verified properly, there is no output. If there are any discrepancies, they are displayed. The format of the output is a string of eight characters (a "<code class="computeroutput">c</code>" denotes a configuration file) and then the file name. Each of the eight characters denotes the result of a comparison of one attribute of the file to the value of that attribute recorded in the RPM database. A single period (<code class="computeroutput">.</code>) means the test passed. The following characters denote specific discrepancies:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">5</code> — MD5 チェックサム
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">S</code> — ファイル サイズ
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">L</code> — シンボリック リンク
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">T</code> — ファイルの修正日時
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">D</code> — デバイス
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">U</code> — ユーザー
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">G</code> — グループ
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">M</code> — モード (パーミッションとファイルの種類を含む)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">?</code> — 読み込み不可ファイル (たとえばファイルのパーミッションエラー)
+ </div></li></ul></div><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 xml:lang="ja-JP" class="section" id="s1-check-rpm-sig" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.3. パッケージの署名を確認する</h2></div></div></div><a id="idm86906448" class="indexterm"></a><div class="para">
+ If you wish to verify that a package has not been corrupted or tampered with, you can examine just the md5sum by entering this command at the shell prompt: (where <em class="replaceable"><code><rpm_file></code></em> is the file name of the RPM package):
+ </div><pre class="screen">
+<code class="command">rpm -K --nosignature <em class="replaceable"><code><rpm_file></code></em> </code>
+</pre><div class="para">
+ The output <code class="computeroutput"><em class="replaceable"><code><rpm_file></code></em>: rsa sha1 (md5) pgp md5 OK</code> (specifically the <span class="emphasis"><em>OK</em></span> part of it) indicates that the file was not corrupted during download. To see a more verbose message, replace <code class="option">-K</code> with <code class="option">-Kvv</code> in the command.
+ </div><div class="para">
+ On the other hand, how trustworthy is the developer who created the package? If the package is <em class="firstterm">signed</em> with the developer's GnuPG <em class="firstterm">key</em>, you know that the developer really is who they say they are.
+ </div><a id="idm82979200" class="indexterm"></a><a id="idm97837456" class="indexterm"></a><a id="idm97835856" class="indexterm"></a><div class="para">
+ An RPM package can be signed using <em class="firstterm">Gnu Privacy Guard</em> (or GnuPG), to help you make certain your downloaded package is trustworthy.
+ </div><div class="para">
+ GnuPG is a tool for secure communication; it is a complete and free replacement for the encryption technology of PGP, an electronic privacy program. With GnuPG, you can authenticate the validity of documents and encrypt/decrypt data to and from other recipients. GnuPG is capable of decrypting and verifying PGP 5.<em class="replaceable"><code>x</code></em> files as well.
+ </div><div class="para">
+ During installation, GnuPG is installed by default, which enables you to immediately start using it to verify any packages that you download from the Fedora Project. Before doing so, you first need to import the correct Fedora key.
+ </div><div class="section" id="s2-keys-importing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.3.1. Importing Keys</h3></div></div></div><div class="para">
+ Fedora GnuPG keys are located in the <code class="filename">/etc/pki/rpm-gpg/</code> directory. To verify a Fedora Project package, first import the correct key based on your processor architecture:
+ </div><pre class="screen">
+<code class="command">rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-<em class="replaceable"><code>x86_64</code></em></code>
+</pre><div class="para">
+ To display a list of all keys installed for RPM verification, execute the command:
+ </div><pre class="screen">
+<code class="command">rpm -qa gpg-pubkey*</code>
+</pre><div class="para">
+ For the Fedora Project key, the output states:
+ </div><pre class="screen">gpg-pubkey-57bbccba-4a6f97af</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:
+ </div><pre class="screen">
+<code class="command">rpm -qi gpg-pubkey-57bbccba-4a6f97af</code>
+</pre></div><div class="section" id="s2-keys-checking"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.3.2. Verifying Signature of Packages</h3></div></div></div><div class="para">
+ To check the GnuPG signature of an RPM file after importing the builder's GnuPG key, use the following command (replace <em class="replaceable"><code><rpm_file></code></em> with the file name of the RPM package):
+ </div><pre class="screen">
+<code class="command">rpm -K <em class="replaceable"><code><rpm_file></code></em> </code>
+</pre><div class="para">
+ If all goes well, the following message is displayed: <code class="computeroutput">rsa sha1 (md5) pgp md5 OK</code>. This means that the signature of the package has been verified, that it is not corrupt, and is therefore safe to install and use.
+ </div><div class="para">
+ For more information, including a list of currently-used Fedora Project keys and their fingerprints, refer to <a href="http://fedoraproject.org/en/keys">http://fedoraproject.org/en/keys</a>.
+ </div></div></div><div class="section" id="s1-rpm-impressing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.4. Practical and Common Examples of RPM Usage</h2></div></div></div><a id="idm125287840" class="indexterm"></a><a id="idm99845360" class="indexterm"></a><div class="para">
+ RPM is a useful tool for both managing your system and diagnosing and fixing problems. The best way to make sense of all its options is to look at some examples.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 誤って何らかのファイルを削除してしまったものの、 何を削除したかわからないとします。 システム全体を検証して足りないものを調べるには、以下のコマンドを試すことができます。
+ </div><a id="idm121443072" class="indexterm"></a><a id="idm121441664" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre><div class="para">
+ 足りないファイルがあるか、壊れているファイルが あるように見える場合は、おそらくパッケージを再インストールするか、いったんアンインストールして 再インストールする必要があります。
+ </div></li><li class="listitem"><div class="para">
+ 所属先のわからないファイルを見つけたとします。そのファイルが含まれるパッケージを検索するには、以下のように入力します。
+ </div><a id="idm104897584" class="indexterm"></a><a id="idm84021504" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qf /usr/bin/ghostscript</code>
+</pre><div class="para">
+ 出力は以下のようになります。
+ </div><pre class="screen">ghostscript-8.70-1.fc17.x86_64</pre></li><li class="listitem"><div class="para">
+ We can combine the above two examples in the following scenario. Say you are having problems with <code class="filename">/usr/bin/paste</code>. You would like to verify the package that owns that program, but you do not know which package owns <code class="command">paste</code>. Enter the following command,
+ </div><pre class="screen">
+<code class="command">rpm -Vf /usr/bin/paste</code>
+</pre><div class="para">
+ 該当するパッケージが検証されます。
+ </div></li><li class="listitem"><div class="para">
+ 特定のプログラムに関して詳細な情報が必要 なら、次のコマンドを入力して、そのプログラムの入った パッケージに付随するドキュメントを検索することが できます。
+ </div><a id="idm84036640" class="indexterm"></a><a id="idm84035200" class="indexterm"></a><a id="idm84033792" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qdf /usr/bin/free</code>
+</pre><div class="para">
+ 出力は以下のようになります。
+ </div><pre class="screen">/usr/share/doc/procps-3.2.8/BUGS
+/usr/share/doc/procps-3.2.8/FAQ
+/usr/share/doc/procps-3.2.8/NEWS
+/usr/share/doc/procps-3.2.8/TODO
+/usr/share/man/man1/free.1.gz
+/usr/share/man/man1/pgrep.1.gz
+/usr/share/man/man1/pkill.1.gz
+/usr/share/man/man1/pmap.1.gz
+/usr/share/man/man1/ps.1.gz
+/usr/share/man/man1/pwdx.1.gz
+/usr/share/man/man1/skill.1.gz
+/usr/share/man/man1/slabtop.1.gz
+/usr/share/man/man1/snice.1.gz
+/usr/share/man/man1/tload.1.gz
+/usr/share/man/man1/top.1.gz
+/usr/share/man/man1/uptime.1.gz
+/usr/share/man/man1/w.1.gz
+/usr/share/man/man1/watch.1.gz
+/usr/share/man/man5/sysctl.conf.5.gz
+/usr/share/man/man8/sysctl.8.gz
+/usr/share/man/man8/vmstat.8.gz</pre></li><li class="listitem"><div class="para">
+ 新しい<span class="application"><strong>RPM</strong></span>パッケージ が見つかったものの、それが何であるかがわからないと します。それに関する情報を検索するには、以下のコマンド を使用します。
+ </div><a id="idm137272528" class="indexterm"></a><a id="idm137271120" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qip crontabs-1.10-31.fc17.noarch.rpm</code>
+</pre><div class="para">
+ 出力は以下のようになります。
+ </div><pre class="screen">Name : crontabs Relocations: (not relocatable)
+Size : 2486 License: Public Domain and GPLv2
+Signature : RSA/SHA1, Tue 11 Aug 2009 01:11:19 PM CEST, Key ID 9d1cc34857bbccba
+Packager : Fedora Project
+Summary : Root crontab files used to schedule the execution of programs
+Description :
+The crontabs package contains root crontab files and directories.
+You will need to install cron daemon to run the jobs from the crontabs.
+The cron daemon such as cronie or fcron checks the crontab files to
+see when particular commands are scheduled to be executed. If commands
+are scheduled, it executes them.
+Crontabs handles a basic system function, so it should be installed on
+your system.</pre></li><li class="listitem"><div class="para">
+ Perhaps you now want to see what files the <code class="filename">crontabs</code> RPM package installs. You would enter the following:
+ </div><a id="idm122125984" class="indexterm"></a><a id="idm122124576" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qlp crontabs-1.10-31.fc17.noarch.rpm</code>
+</pre><div class="para">
+ 出力は以下のようになります。
+ </div><pre class="screen">/etc/cron.daily
+/etc/cron.hourly
+/etc/cron.monthly
+/etc/cron.weekly
+/etc/crontab
+/usr/bin/run-parts
+/usr/share/man/man4/crontabs.4.gz</pre></li></ul></div><div class="para">
+ These are just a few examples. As you use RPM, you may find more uses for it.
+ </div></div><div class="section" id="s1-rpm-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.5. その他のリソース</h2></div></div></div><a id="idm122869920" class="indexterm"></a><div class="para">
+ RPM は、パッケージの問い合わせ、インストール、アップグレード、 削除を実行するためのたくさんのオプションや方法がある 非常に複雑なユーティリティです。RPM の詳細については、 以下のリソースを参照してください。
+ </div><div class="section" id="s2-rpm-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.5.1. インストールされているドキュメント</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rpm --help</code> — This command displays a quick reference of RPM parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man rpm</code> — The RPM man page gives more detail about RPM parameters than the <code class="command">rpm --help</code> command.
+ </div></li></ul></div></div><div class="section" id="s2-rpm-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.5.2. 役に立つ Web サイト</h3></div></div></div><div class="itemizedlist"><a id="idm113871696" class="indexterm"></a><ul><li class="listitem"><div class="para">
+ The RPM website — <a href="http://www.rpm.org/">http://www.rpm.org/</a>
+ </div></li><li class="listitem"><div class="para">
+ The RPM mailing list can be subscribed to, and its archives read from, here — <a href="http://www.redhat.com/mailman/listinfo/rpm-list/">https://lists.rpm.org/mailman/listinfo/rpm-list</a>
+ </div></li></ul></div></div><div class="section" id="s2-rpm-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.5.3. 関連書籍</h3></div></div></div><a id="idm91613936" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <em class="citetitle">Maximum RPM</em> — <a href="http://www.rpm.org/max-rpm/">http://www.rpm.org/max-rpm/</a> </span></dt><dd><div class="para">
+ The <em class="citetitle">Maximum RPM</em> book, which you can read online, covers everything from general RPM usage to building your own RPMs to programming with rpmlib.
+ </div></dd></dl></div></div></div></div><div xml:lang="ja-JP" class="appendix" id="ch-The_X_Window_System" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">X Window System</h1></div></div></div><a id="idm68378480" class="indexterm"></a><a id="idm96232480" class="indexterm"></a><a id="idm101328064" class="indexterm"></a><a id="idm116846976" class="indexterm"></a><a id="idm113687152" class="indexterm"></a><div class="para">
+ While the heart of Fedora is the kernel, for many users, the face of the operating system is the graphical environment provided by the <em class="firstterm">X Window System</em>, also called <em class="firstterm">X</em>.
+ </div><div class="para">
+ Other windowing environments have existed in the UNIX world, including some that predate the release of the X Window System in June 1984. Nonetheless, X has been the default graphical environment for most UNIX-like operating systems, including Fedora, for many years.
+ </div><div class="para">
+ The graphical environment for Fedora is supplied by the <em class="firstterm">X.Org Foundation</em>, an open source organization created to manage development and strategy for the X Window System and related technologies. X.Org is a large-scale, rapid-developing project with hundreds of developers around the world. It features a wide degree of support for a variety of hardware devices and architectures, and runs on myriad operating systems and platforms.
+ </div><div class="para">
+ The X Window System uses a client-server architecture. Its main purpose is to provide network transparent window system, which runs on a wide range of computing and graphics machines. The <em class="firstterm">X server</em> (the <code class="command">Xorg</code> binary) listens for connections from <em class="firstterm">X client</em> applications via a network or local loopback interface. The server communicates with the hardware, such as the video card, monitor, keyboard, and mouse. X client applications exist in the user space, creating a <em class="firstterm">graphical user interface</em> (<em class="firstterm">GUI</em>) for the user and passing user requests to the X server.
+ </div><div class="section" id="s1-x-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.1. The X Server</h2></div></div></div><a id="idm71470256" class="indexterm"></a><div class="para">
+ Fedora 17 uses X server version, which includes several video drivers, EXA, and platform support enhancements over the previous release, among others. In addition, this release includes several automatic configuration features for the X server, as well as the generic input driver, <code class="systemitem">evdev</code>, that supports all input devices that the kernel knows about, including most mice and keyboards.
+ </div><div class="para">
+ X11R7.1 was the first release to take specific advantage of the modularization of the X Window System. With it, X is split into logically distinct modules, which make it easier for open source developers to contribute code to the system.
+ </div><div class="para">
+ In the current release, all libraries, headers, and binaries live under the <code class="filename">/usr/</code> directory. The <code class="filename">/etc/X11/</code> directory contains configuration files for X client and server applications. This includes configuration files for the X server itself, the X display managers, and many other base components.
+ </div><div class="para">
+ The configuration file for the newer Fontconfig-based font architecture is still <code class="filename">/etc/fonts/fonts.conf</code>. For more information on configuring and adding fonts, refer to <a class="xref" href="#s1-x-fonts">「フォント」</a>.
+ </div><div class="para">
+ Because the X server performs advanced tasks on a wide array of hardware, it requires detailed information about the hardware it works on. The X server is able to automatically detect most of the hardware that it runs on and configure itself accordingly. Alternatively, hardware can be manually specified in configuration files.
+ </div><div class="para">
+ The Fedora system installer, Anaconda, installs and configures X automatically, unless the X packages are not selected for installation. If there are any changes to the monitor, video card or other devices managed by the X server, most of the time, X detects and reconfigures these changes automatically. In rare cases, X must be reconfigured manually.
+ </div></div><div class="section" id="s1-x-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.2. デスクトップ環境とウィンドウマネージャ</h2></div></div></div><a id="idm86685632" class="indexterm"></a><div class="para">
+ Once an X server is running, X client applications can connect to it and create a GUI for the user. A range of GUIs are available with Fedora, from the rudimentary <em class="firstterm">Tab Window Manager</em> (twm) to the highly developed and interactive desktop environment (such as <em class="firstterm">GNOME</em> or <em class="firstterm">KDE</em>) that most Fedora users are familiar with.
+ </div><div class="para">
+ To create the latter, more comprehensive GUI, two main classes of X client application must connect to the X server: a <em class="firstterm">window manager</em> and a <em class="firstterm">desktop environment</em>.
+ </div><div class="section" id="s2-x-clients-desktop"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.2.1. デスクトップ環境</h3></div></div></div><a id="idm110492736" class="indexterm"></a><a id="idm110490624" class="indexterm"></a><a id="idm127894896" class="indexterm"></a><a id="idm127893264" class="indexterm"></a><a id="idm124413040" class="indexterm"></a><a id="idm124410928" class="indexterm"></a><div class="para">
+ A desktop environment integrates various X clients to create a common graphical user environment and a development platform.
+ </div><div class="para">
+ Desktop environments have advanced features allowing X clients and other running processes to communicate with one another, while also allowing all applications written to work in that environment to perform advanced tasks, such as drag-and-drop operations.
+ </div><div class="para">
+ Fedora provides two desktop environments:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>GNOME</em></span> — The default desktop environment for Fedora based on the GTK+ 2 graphical toolkit.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>KDE</em></span> — An alternative desktop environment based on the Qt 4 graphical toolkit.
+ </div></li></ul></div><div class="para">
+ Both GNOME and KDE have advanced-productivity applications, such as word processors, spreadsheets, and Web browsers; both also provide tools to customize the look and feel of the GUI. Additionally, if both the GTK+ 2 and the Qt libraries are present, KDE applications can run in GNOME and vice versa.
+ </div></div><div class="section" id="s2-x-clients-winmanagers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.2.2. ウィンドウマネージャ</h3></div></div></div><a id="idm98375264" class="indexterm"></a><a id="idm127059152" class="indexterm"></a><a id="idm127057040" class="indexterm"></a><a id="idm108848096" class="indexterm"></a><a id="idm148091664" class="indexterm"></a><a id="idm148089072" class="indexterm"></a><a id="idm97204672" class="indexterm"></a><a id="idm118589696" class="indexterm"></a><a id="idm118587584" class="indexterm"></a><a id="idm86849696" class="indexterm"></a><div class="para">
+ <em class="firstterm">ウィンドウマネージャ</em> は、 X クライアントプログラムであり、デスクトップ環境の一部、または場合によってはスタンドアローンのこともあります。その主要目的はグラフィカルウィンドウの配置、サイズ変更、移動などを制御することです。ウィンドウマネージャは、タイトルバー、ウィンドウの焦点調節、ユーザー設定のキーやマウスボタンの連携なども制御します。
+ </div><div class="para">
+ The Fedora repositories provide five different window managers:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="command">metacity</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Metacity</em> window manager is the default window manager for GNOME. It is a simple and efficient window manager which supports custom themes. This window manager is automatically pulled in as a dependency when the GNOME desktop is installed.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">kwin</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">KWin</em> window manager is the default window manager for KDE. It is an efficient window manager which supports custom themes. This window manager is automatically pulled in as a dependency when the KDE desktop is installed.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">compiz</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Compiz</em> compositing window manager is based on OpenGL and can use 3D graphics hardware to create fast compositing desktop effects for window management. Advanced features, such as a cube workspace, are implemented as loadable plug-ins. To run this window manager, you need to install the <code class="filename">compiz</code> package.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">mwm</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Motif Window Manager</em> (<code class="command">mwm</code>) is a basic, stand-alone window manager. Since it is designed to be stand-alone, it should not be used in conjunction with GNOME or KDE. To run this window manager, you need to install the <code class="filename">openmotif</code> package.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">twm</code></span></dt><dd><div class="para">
+ The minimalist <em class="firstterm">Tab Window Manager</em> (<code class="command">twm</code>), which provides the most basic tool set among the available window managers, can be used either as a stand-alone or with a desktop environment. To run this window manager, you need to install the <code class="filename">xorg-x11-twm</code> package.
+ </div></dd></dl></div></div></div><div class="section" id="s1-x-server-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.3. X サーバー設定ファイル</h2></div></div></div><a id="idm82369120" class="indexterm"></a><a id="idm112481552" class="indexterm"></a><div class="para">
+ The X server is a single binary executable <code class="filename">/usr/bin/Xorg</code>; a symbolic link <code class="filename">X</code> pointing to this file is also provided. Associated configuration files are stored in the <code class="filename">/etc/X11/</code> and <code class="filename">/usr/share/X11/</code> directories.
+ </div><div class="para">
+ The X Window System supports two different configuration schemes. Configuration files in the <code class="filename">xorg.conf.d</code> directory contain preconfigured settings from vendors and from distribution, and these files should not be edited by hand. Configuration in the <code class="filename">xorg.conf</code> file, on the other hand, is done completely by hand but is not necessary in most scenarios.
+ </div><div class="note"><div class="admonition_header"><h2>When do you need the xorg.conf file?</h2></div><div class="admonition"><div class="para">
+ All necessary parameters for a display and peripherals are auto-detected and configured during installation. The configuration file for the X server, <code class="filename">/etc/X11/xorg.conf</code>, that was necessary in previous releases, is not supplied with the current release of the X Window System. It can still be useful to create the file manually to configure new hardware, to set up an environment with multiple video cards, or for debugging purposes.
+ </div></div></div><div class="para">
+ The <code class="filename">/usr/lib/xorg/modules/</code> (or <code class="filename">/usr/lib64/xorg/modules/</code>) directory contains X server modules that can be loaded dynamically at runtime. By default, only some modules in <code class="filename">/usr/lib/xorg/modules/</code> are automatically loaded by the X server.
+ </div><div class="para">
+ When Fedora 17 is installed, the configuration files for X are created using information gathered about the system hardware during the installation process by the HAL (Hardware Abstraction Layer) configuration back end. Whenever the X server is started, it asks HAL for the list of input devices and adds each of them with their respective driver. Whenever a new input device is plugged in, or an existing input device is removed, HAL notifies the X server about the change. Because of this notification system, devices using the <code class="systemitem">mouse</code>, <code class="systemitem">kbd</code>, or <code class="systemitem">vmmouse</code> driver configured in the <code class="filename">xorg.conf</code> file are, by default, ignored by the X server. Refer to <a class="xref" href="#s3-x-server-config-xorg.conf-serverf">「The <code class="option">ServerFlags</code> section」</a> for further details. Additional configuration is provided in the <code class="filename">/etc/
X11/xorg.conf.d/</code> directory and it can override or augment any configuration that has been obtained through HAL.
+ </div><div class="section" id="s2-x-server-config-xorg.conf-struct"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.3.1. The Structure of the Configuration</h3></div></div></div><a id="idm98953200" class="indexterm"></a><a id="idm127043808" class="indexterm"></a><a id="idm127040736" class="indexterm"></a><div class="para">
+ The format of the X configuration files is comprised of many different sections which address specific aspects of the system hardware. Each section begins with a <code class="option">Section "<em class="replaceable"><code>section-name</code></em>"</code> line, where "<em class="replaceable"><code>section-name</code></em>" is the title for the section, and ends with an <code class="option">EndSection</code> line. Each section contains lines that include option names and one or more option values. Some of these are sometimes enclosed in double quotes (<code class="literal">"</code>).
+ </div><div class="para">
+ Some options within the <code class="filename">/etc/X11/xorg.conf</code> file accept a boolean switch which turns the feature on or off. The acceptable values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">1</code>, <code class="literal">on</code>, <code class="literal">true</code>, or <code class="literal">yes</code> — Turns the option on.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">0</code>, <code class="literal">off</code>, <code class="literal">false</code>, or <code class="literal">no</code> — Turns the option off.
+ </div></li></ul></div><div class="para">
+ The following shows a typical configuration file for the keyboard. Lines beginning with a hash sign (<code class="literal">#</code>) are not read by the X server and are used for human-readable comments.
+ </div><pre class="screen"># This file is autogenerated by system-setup-keyboard. Any
+# modifications will be lost.
+
+Section "InputClass"
+ Identifier "system-setup-keyboard"
+ MatchIsKeyboard "on"
+ Option "XkbModel" "pc105"
+ Option "XkbLayout" "cz,us"
+# Option "XkbVariant" "(null)"
+ Option "XkbOptions" "terminate:ctrl_alt_bksp,grp:shifts_toggle,grp_led:scroll"
+EndSection</pre></div><div class="section" id="s2-x-server-config-xorg.conf.d"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.3.2. The <code class="filename">xorg.conf.d</code> Directory</h3></div></div></div><a id="idm107839936" class="indexterm"></a><a id="idm94882688" class="indexterm"></a><a id="idm131595536" class="indexterm"></a><div class="para">
+ The X server supports two configuration directories. The <code class="filename">/usr/share/X11/xorg.conf.d/</code> provides separate configuration files from vendors or third-party packages; changes to files in this directory may be overwritten by settings specified in the <code class="filename">/etc/X11/xorg.conf</code> file. The <code class="filename">/etc/X11/xorg.conf.d/</code> directory stores user-specific configuration.
+ </div><div class="para">
+ Files with the suffix <code class="filename">.conf</code> in configuration directories are parsed by the X server upon startup and are treated like part of the traditional <code class="filename">xorg.conf</code> configuration file. These files may contain one or more sections; for a description of the options in a section and the general layout of the configuration file, refer to <a class="xref" href="#s2-x-server-config-xorg.conf">「The <code class="filename">xorg.conf</code> File」</a> or to the <code class="systemitem">xorg.conf(5)</code> man page. The X server essentially treats the collection of configuration files as one big file with entries from <code class="filename">xorg.conf</code> at the end. Users are encouraged to put custom configuration into <code class="filename">/etc/xorg.conf</code> and leave the directory for configuration snippets provided by the distribution.
+ </div></div><div class="section" id="s2-x-server-config-xorg.conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.3.3. The <code class="filename">xorg.conf</code> File</h3></div></div></div><a id="idm104113888" class="indexterm"></a><a id="idm84790224" class="indexterm"></a><a id="idm84788112" class="indexterm"></a><div class="para">
+ In previous releases of the X Window System, <code class="filename">/etc/X11/xorg.conf</code> file was used to store initial setup for X. When a change occurred with the monitor, video card or other device managed by the X server, the file needed to be edited manually. In Fedora, there is rarely a need to manually create and edit the <code class="filename">/etc/X11/xorg.conf</code> file. Nevertheless, it is still useful to understand various sections and optional parameters available, especially when troubleshooting or setting up unusual hardware configuration.
+ </div><div class="para">
+ In the following, some important sections are described in the order in which they appear in a typical <code class="filename">/etc/X11/xorg.conf</code> file. More detailed information about the X server configuration file can be found in the <code class="filename">xorg.conf(5)</code> man page. This section is mostly intended for advanced users as most configuration options described below are not needed in typical configuration scenarios.
+ </div><div class="section" id="s3-x-server-config-xorg.conf.d-inputclass"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.1. The <code class="option">InputClass</code> section</h4></div></div></div><div class="para">
+ <code class="option">InputClass</code> is a new type of configuration section that does not apply to a single device but rather to a class of devices, including hot-plugged devices. An <code class="option">InputClass</code> section's scope is limited by the matches specified; in order to apply to an input device, all matches must apply to the device as seen in the example below:
+ </div><pre class="screen">Section "InputClass"
+ Identifier "touchpad catchall"
+ MatchIsTouchpad "on"
+ Driver "synaptics"
+EndSection</pre><div class="para">
+ If this snippet is present in an <code class="filename">xorg.conf</code> file or an <code class="filename">xorg.conf.d</code> directory, any touchpad present in the system is assigned the <code class="systemitem">synaptics</code> driver.
+ </div><div class="note"><div class="admonition_header"><h2>Alphanumeric sorting in <code class="filename">xorg.conf.d</code></h2></div><div class="admonition"><div class="para">
+ Note that due to alphanumeric sorting of configuration files in the <code class="filename">xorg.conf.d</code> directory, the <code class="option">Driver</code> setting in the example above overwrites previously set driver options. The more generic the class, the earlier it should be listed.
+ </div></div></div><div class="para">
+ The match options specify which devices a section may apply to. To match a device, all match options must correspond. The following options are commonly used in the <code class="option">InputClass</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">MatchIsPointer</code>, <code class="option">MatchIsKeyboard</code>, <code class="option">MatchIsTouchpad</code>, <code class="option">MatchIsTouchscreen</code>, <code class="option">MatchIsJoystick</code> — boolean options to specify a type of a device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">MatchProduct "<em class="replaceable"><code>product_name</code></em>"</code> — this option matches if the <em class="replaceable"><code>product_name</code></em> substring occurs in the product name of the device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">MatchVendor "<em class="replaceable"><code>vendor_name</code></em>"</code> — this option matches if the <em class="replaceable"><code>vendor_name</code></em> substring occurs in the vendor name of the device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">MatchDevicePath "<em class="replaceable"><code>/path/to/device</code></em>"</code> — this option matches any device if its device path corresponds to the patterns given in the "<em class="replaceable"><code>/path/to/device</code></em>" template, for example <code class="literal">/dev/input/event*</code>. Refer to the <code class="command">fnmatch(3)</code> man page for further details.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">MatchTag "<em class="replaceable"><code>tag_pattern</code></em>"</code> — this option matches if at least one tag assigned by the HAL configuration back end matches the <em class="replaceable"><code>tag_pattern</code></em> pattern.
+ </div></li></ul></div><div class="para">
+ A configuration file may have multiple <code class="option">InputClass</code> sections. These sections are optional and are used to configure a class of input devices as they are automatically added. An input device can match more than one <code class="option">InputClass</code> section. When arranging these sections, it is recommended to put generic matches above specific ones because each input class can override settings from a previous one if an overlap occurs.
+ </div></div><div class="section" id="s3-x-server-config-xorg.conf-inputd"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.2. The <code class="option">InputDevice</code> section</h4></div></div></div><a id="idm125094528" class="indexterm"></a><div class="para">
+ Each <code class="option">InputDevice</code> section configures one input device for the X server. Previously, systems typically had at least one <code class="option">InputDevice</code> section for the keyboard, and most mouse settings were automatically detected.
+ </div><div class="para">
+ With Fedora 17, no <code class="option">InputDevice</code> configuration is needed for most setups, and the <span class="package">xorg-x11-drv-*</span> input driver packages provide the automatic configuration through HAL. The default driver for both keyboards and mice is <code class="literal">evdev</code>.
+ </div><div class="para">
+ The following example shows a typical <code class="option">InputDevice</code> section for a keyboard:
+ </div><pre class="screen">Section "InputDevice"
+ Identifier "Keyboard0"
+ Driver "kbd"
+ Option "XkbModel" "pc105"
+ Option "XkbLayout" "us"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">InputDevice</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">InputDevice</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Driver</code> — Specifies the name of the device driver X must load for the device. If the <code class="option">AutoAddDevices</code> option is enabled (which is the default setting), any input device section with <code class="option">Driver "mouse"</code> or <code class="option">Driver "kbd"</code> will be ignored. This is necessary due to conflicts between the legacy mouse and keyboard drivers and the new <code class="literal">evdev</code> generic driver. Instead, the server will use the information from the back end for any input devices. Any custom input device configuration in the <code class="filename">xorg.conf</code> should be moved to the back end. In most cases, the back end will be HAL and the configuration location will be the <code class="filename">/etc/X11/xorg.conf.d</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option</code> — Specifies necessary options pertaining to the device.
+ </div><div class="para">
+ A mouse may also be specified to override any auto-detected values for the device. The following options are typically included when adding a mouse in the <code class="filename">xorg.conf</code> file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Protocol</code> — Specifies the protocol used by the mouse, such as <code class="literal">IMPS/2</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Device</code> — Specifies the location of the physical device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Emulate3Buttons</code> — Specifies whether to allow a two-button mouse to act like a three-button mouse when both mouse buttons are pressed simultaneously.
+ </div></li></ul></div><div class="para">
+ Consult the <code class="filename">xorg.conf(5)</code> man page for a complete list of valid options for this section.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-serverf"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.3. The <code class="option">ServerFlags</code> section</h4></div></div></div><a id="idm92417136" class="indexterm"></a><div class="para">
+ The optional <code class="option">ServerFlags</code> section contains miscellaneous global X server settings. Any settings in this section may be overridden by options placed in the <code class="option">ServerLayout</code> section (refer to <a class="xref" href="#s3-x-server-config-xorg.conf-serverl">「<code class="option">ServerLayout</code>」</a> for details).
+ </div><div class="para">
+ Each entry within the <code class="option">ServerFlags</code> section occupies a single line and begins with the term <code class="option">Option</code> followed by an option enclosed in double quotation marks (<code class="literal">"</code>).
+ </div><div class="para">
+ The following is a sample <code class="option">ServerFlags</code> section:
+ </div><pre class="screen">Section "ServerFlags"
+ Option "DontZap" "true"
+EndSection</pre><div class="para">
+ 特に役立つオプションの幾つかを以下に一覧表示します：
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">"DontZap" "<em class="replaceable"><code>boolean</code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to <code class="literal">true</code>, this setting prevents the use of the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Backspace</strong></span> key combination to immediately terminate the X server.
+ </div><div class="note"><div class="admonition_header"><h2>X keyboard extension</h2></div><div class="admonition"><div class="para">
+ Even if this option is enabled, the key combination still must be configured in the X Keyboard Extension (XKB) map before it can be used. One way how to add the key combination to the map is to run the following command:
+<pre class="screen"><code class="command">setxkbmap -option "terminate:ctrl_alt_bksp"</code></pre>
+
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">"DontZoom" "<em class="replaceable"><code>boolean</code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to <code class="literal">true</code>, this setting prevents cycling through configured video resolutions using the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Keypad-Plus</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Keypad-Minus</strong></span> key combinations.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">"AutoAddDevices" "<em class="replaceable"><code>boolean</code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to <code class="literal">false</code>, the server will not hot plug input devices and instead rely solely on devices configured in the <code class="filename">xorg.conf</code> file. Refer to <a class="xref" href="#s3-x-server-config-xorg.conf-inputd">「The <code class="option">InputDevice</code> section」</a> for more information concerning input devices. This option is enabled by default and HAL (hardware abstraction layer) is used as a back end for device discovery.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-serverl"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.4. <code class="option">ServerLayout</code></h4></div></div></div><a id="idm108523296" class="indexterm"></a><div class="para">
+ The <code class="option">ServerLayout</code> section binds together the input and output devices controlled by the X server. At a minimum, this section must specify one input device and one output device. By default, a monitor (output device) and a keyboard (input device) are specified.
+ </div><div class="para">
+ The following example shows a typical <code class="option">ServerLayout</code> section:
+ </div><pre class="screen">Section "ServerLayout"
+ Identifier "Default Layout"
+ Screen 0 "Screen0" 0 0
+ InputDevice "Mouse0" "CorePointer"
+ InputDevice "Keyboard0" "CoreKeyboard"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">ServerLayout</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">ServerLayout</code> section.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Screen</code> — Specifies the name of a <code class="option">Screen</code> section to be used with the X server. More than one <code class="option">Screen</code> option may be present.
+ </div><div class="para">
+ The following is an example of a typical <code class="option">Screen</code> entry:
+ </div><pre class="screen">Screen 0 "Screen0" 0 0</pre><div class="para">
+ The first number in this example <code class="option">Screen</code> entry (<code class="literal">0</code>) indicates that the first monitor connector, or <em class="firstterm">head</em> on the video card, uses the configuration specified in the <code class="option">Screen</code> section with the identifier <code class="option">"Screen0"</code>.
+ </div><div class="para">
+ An example of a <code class="option">Screen</code> section with the identifier <code class="option">"Screen0"</code> can be found in <a class="xref" href="#s3-x-server-config-xorg.conf-screen">「The <code class="option">Screen</code> section」</a>.
+ </div><div class="para">
+ If the video card has more than one head, another <code class="option">Screen</code> entry with a different number and a different <code class="option">Screen</code> section identifier is necessary.
+ </div><div class="para">
+ The numbers to the right of <code class="option">"Screen0"</code> give the absolute X and Y coordinates for the upper left corner of the screen (<code class="literal">0 0</code> by default).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">InputDevice</code> — Specifies the name of an <code class="option">InputDevice</code> section to be used with the X server.
+ </div><div class="para">
+ It is advisable that there be at least two <code class="option">InputDevice</code> entries: one for the default mouse and one for the default keyboard. The options <code class="option">CorePointer</code> and <code class="option">CoreKeyboard</code> indicate that these are the primary mouse and keyboard. If the <code class="option">AutoAddDevices</code> option is enabled, this entry needs not to be specified in the <code class="option">ServerLayout</code> section. If the <code class="option">AutoAddDevices</code> option is disabled, both mouse and keyboard are auto-detected with the default values.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option "<em class="replaceable"><code>option-name</code></em>"</code> — An optional entry which specifies extra parameters for the section. Any options listed here override those listed in the <code class="option">ServerFlags</code> section.
+ </div><div class="para">
+ Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf(5)</code> man page.
+ </div></li></ul></div><div class="para">
+ It is possible to put more than one <code class="option">ServerLayout</code> section in the <code class="filename">/etc/X11/xorg.conf</code> file. By default, the server only reads the first one it encounters, however. If there is an alternative <code class="option">ServerLayout</code> section, it can be specified as a command line argument when starting an X session; as in the <code class="command">Xorg -layout <layoutname></code> command.
+ </div></div><div class="section" id="s3-x-server-config-xorg.conf-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.5. The <code class="option">Files</code> section</h4></div></div></div><a id="idm105789968" class="indexterm"></a><div class="para">
+ The <code class="option">Files</code> section sets paths for services vital to the X server, such as the font path. This is an optional section, as these paths are normally detected automatically. This section can be used to override automatically detected values.
+ </div><div class="para">
+ The following example shows a typical <code class="option">Files</code> section:
+ </div><pre class="screen">Section "Files"
+ RgbPath "/usr/share/X11/rgb.txt"
+ FontPath "unix/:7100"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">Files</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">ModulePath</code> — An optional parameter which specifies alternate directories which store X server modules.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.6. The <code class="option">Monitor</code> section</h4></div></div></div><a id="idp2607728" class="indexterm"></a><div class="para">
+ Each <code class="option">Monitor</code> section configures one type of monitor used by the system. This is an optional entry as most monitors are now detected automatically.
+ </div><div class="para">
+ This example shows a typical <code class="option">Monitor</code> section for a monitor:
+ </div><pre class="screen">Section "Monitor"
+ Identifier "Monitor0"
+ VendorName "Monitor Vendor"
+ ModelName "DDC Probed Monitor - ViewSonic G773-2"
+ DisplaySize 320 240
+ HorizSync 30.0 - 70.0
+ VertRefresh 50.0 - 180.0
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">Monitor</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">Monitor</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">VendorName</code> — An optional parameter which specifies the vendor of the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ModelName</code> — An optional parameter which specifies the monitor's model name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">DisplaySize</code> — An optional parameter which specifies, in millimeters, the physical size of the monitor's picture area.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">HorizSync</code> — Specifies the range of horizontal sync frequencies compatible with the monitor, in kHz. These values help the X server determine the validity of built-in or specified <code class="option">Modeline</code> entries for the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">VertRefresh</code> — Specifies the range of vertical refresh frequencies supported by the monitor, in kHz. These values help the X server determine the validity of built-in or specified <code class="option">Modeline</code> entries for the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Modeline</code> — An optional parameter which specifies additional video modes for the monitor at particular resolutions, with certain horizontal sync and vertical refresh resolutions. Refer to the <code class="filename">xorg.conf(5)</code> man page for a more detailed explanation of <code class="option">Modeline</code> entries.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option "<em class="replaceable"><code>option-name</code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf(5)</code> man page.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-device"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.7. The <code class="option">Device</code> section</h4></div></div></div><a id="idm113651520" class="indexterm"></a><div class="para">
+ Each <code class="option">Device</code> section configures one video card on the system. While one <code class="option">Device</code> section is the minimum, additional instances may occur for each video card installed on the machine.
+ </div><div class="para">
+ The following example shows a typical <code class="option">Device</code> section for a video card:
+ </div><pre class="screen">Section "Device"
+ Identifier "Videocard0"
+ Driver "mga"
+ VendorName "Videocard vendor"
+ BoardName "Matrox Millennium G200"
+ VideoRam 8192
+ Option "dpms"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">Device</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">Device</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Driver</code> — Specifies which driver the X server must load to utilize the video card. A list of drivers can be found in <code class="filename">/usr/share/hwdata/videodrivers</code>, which is installed with the <span class="package">hwdata</span> package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">VendorName</code> — An optional parameter which specifies the vendor of the video card.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">BoardName</code> — An optional parameter which specifies the name of the video card.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">VideoRam</code> — An optional parameter which specifies the amount of RAM available on the video card, in kilobytes. This setting is only necessary for video cards the X server cannot probe to detect the amount of video RAM.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">BusID</code> — An entry which specifies the bus location of the video card. On systems with only one video card a <code class="option">BusID</code> entry is optional and may not even be present in the default <code class="filename">/etc/X11/xorg.conf</code> file. On systems with more than one video card, however, a <code class="option">BusID</code> entry is required.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Screen</code> — An optional entry which specifies which monitor connector or head on the video card the <code class="option">Device</code> section configures. This option is only useful for video cards with multiple heads.
+ </div><div class="para">
+ If multiple monitors are connected to different heads on the same video card, separate <code class="option">Device</code> sections must exist and each of these sections must have a different <code class="option">Screen</code> value.
+ </div><div class="para">
+ Values for the <code class="option">Screen</code> entry must be an integer. The first head on the video card has a value of <code class="literal">0</code>. The value for each additional head increments this value by one.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option "<em class="replaceable"><code>option-name</code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf(5)</code> man page.
+ </div><div class="para">
+ One of the more common options is <code class="literal">"dpms"</code> (for Display Power Management Signaling, a VESA standard), which activates the Service Star energy compliance setting for the monitor.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-screen"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.8. The <code class="option">Screen</code> section</h4></div></div></div><a id="idm117883888" class="indexterm"></a><div class="para">
+ Each <code class="option">Screen</code> section binds one video card (or video card head) to one monitor by referencing the <code class="option">Device</code> section and the <code class="option">Monitor</code> section for each. While one <code class="option">Screen</code> section is the minimum, additional instances may occur for each video card and monitor combination present on the machine.
+ </div><div class="para">
+ The following example shows a typical <code class="option">Screen</code> section:
+ </div><pre class="screen">Section "Screen"
+ Identifier "Screen0"
+ Device "Videocard0"
+ Monitor "Monitor0"
+ DefaultDepth 16
+
+ SubSection "Display"
+ Depth 24
+ Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
+ EndSubSection
+
+ SubSection "Display"
+ Depth 16
+ Modes "1152x864" "1024x768" "800x600" "640x480"
+ EndSubSection
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">Screen</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">Screen</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Device</code> — Specifies the unique name of a <code class="option">Device</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Monitor</code> — Specifies the unique name of a <code class="option">Monitor</code> section. This is only required if a specific <code class="option">Monitor</code> section is defined in the <code class="filename">xorg.conf</code> file. Normally, monitors are detected automatically.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">DefaultDepth</code> — Specifies the default color depth in bits. In the previous example, <code class="literal">16</code> (which provides thousands of colors) is the default. Only one <code class="option">DefaultDepth</code> entry is permitted, although this can be overridden with the Xorg command line option <code class="command">-depth <em class="replaceable"><code><n></code></em></code>, where <code class="command"><em class="replaceable"><code><n></code></em></code> is any additional depth specified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">SubSection "Display"</code> — Specifies the screen modes available at a particular color depth. The <code class="option">Screen</code> section can have multiple <code class="option">Display</code> subsections, which are entirely optional since screen modes are detected automatically.
+ </div><div class="para">
+ This subsection is normally used to override auto-detected modes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option "<em class="replaceable"><code>option-name</code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf(5)</code> man page.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-dri"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.9. The <code class="option">DRI</code> section</h4></div></div></div><a id="idm88916880" class="indexterm"></a><div class="para">
+ The optional <code class="option">DRI</code> section specifies parameters for the <em class="firstterm">Direct Rendering Infrastructure</em> (<em class="firstterm">DRI</em>). DRI is an interface which allows 3D software applications to take advantage of 3D hardware acceleration capabilities built into most modern video hardware. In addition, DRI can improve 2D performance via hardware acceleration, if supported by the video card driver.
+ </div><div class="para">
+ This section is rarely used, as the DRI Group and Mode are automatically initialized to default values. If a different Group or Mode is needed, then adding this section to the <code class="filename">xorg.conf</code> file will override the default values.
+ </div><div class="para">
+ The following example shows a typical <code class="option">DRI</code> section:
+ </div><pre class="screen">Section "DRI"
+ Group 0
+ Mode 0666
+EndSection</pre><div class="para">
+ Since different video cards use DRI in different ways, do not add to this section without first referring to <a href="http://dri.freedesktop.org/wiki/">http://dri.freedesktop.org/wiki/</a>.
+ </div></div></div></div><div class="section" id="s1-x-fonts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.4. フォント</h2></div></div></div><a id="idm110462640" class="indexterm"></a><a id="idm113383008" class="indexterm"></a><a id="idm113380896" class="indexterm"></a><a id="idm106374736" class="indexterm"></a><div class="para">
+ Fedora uses <em class="firstterm">Fontconfig</em> subsystem to manage and display fonts under the X Window System. It simplifies font management and provides advanced display features, such as anti-aliasing. This system is used automatically for applications programmed using the <code class="literal">Qt 3</code> or <code class="literal">GTK+ 2</code> graphical toolkits, or their newer versions.
+ </div><div class="para">
+ The Fontconfig font subsystem allows applications to directly access fonts on the system and use the <em class="firstterm">X FreeType interface library</em> (<em class="firstterm">Xft</em>) or other rendering mechanisms to render Fontconfig fonts with advanced features such as anti-aliasing. Graphical applications can use the Xft library with Fontconfig to draw text to the screen.
+ </div><div class="note"><div class="admonition_header"><h2>Font configuration</h2></div><div class="admonition"><div class="para">
+ Fontconfig uses the <code class="filename">/etc/fonts/fonts.conf</code> configuration file, which should not be edited by hand.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Fonts group</h2></div><div class="admonition"><div class="para">
+ Any system where the user expects to run remote X applications needs to have the <code class="systemitem">fonts</code> group installed. This can be done by selecting the group in the installer, and also by running the <code class="command">yum groupinstall fonts</code> command after installation.
+ </div></div></div><div class="section" id="s3-x-fonts-fontconfig-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.4.1. Fontconfig へのフォントの追加</h3></div></div></div><a id="idm129060112" class="indexterm"></a><div class="para">
+ Adding new fonts to the Fontconfig subsystem is a straightforward process:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To add fonts for an individual user, copy the new fonts into the <code class="filename">.fonts/</code> directory in the user's home directory.
+ </div><div class="para">
+ To add fonts system-wide, copy the new fonts into the <code class="filename">/usr/share/fonts/</code> directory. It is a good idea to create a new subdirectory, such as <code class="filename">local/</code> or similar, to help distinguish between user-installed and default fonts.
+ </div></li><li class="listitem"><div class="para">
+ Run the <code class="command">fc-cache</code> command as root to update the font information cache:
+ </div><pre class="screen"><code class="command">fc-cache <em class="replaceable"><code><path-to-font-directory></code></em></code></pre><div class="para">
+ In this command, replace <em class="replaceable"><code><path-to-font-directory></code></em> with the directory containing the new fonts (either <code class="filename">/usr/share/fonts/local/</code> or <code class="filename">/home/<em class="replaceable"><code><user></code></em>/.fonts/</code>).
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Interactive font installation</h2></div><div class="admonition"><div class="para">
+ Individual users may also install fonts interactively, by typing <code class="filename">fonts:///</code> into the <span class="application"><strong>Nautilus</strong></span> address bar, and dragging the new font files there.
+ </div></div></div></div></div><div class="section" id="s1-x-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.5. その他のリソース</h2></div></div></div><a id="idm104032608" class="indexterm"></a><div class="para">
+ X サーバー、このサーバーに接続されているクライアント、及びさまざまなデスクトップ環境とウィンドウマネージャについては他にも多量の詳細情報があります。
+ </div><div class="section" id="s2-x-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.5.1. インストールされているドキュメント</h3></div></div></div><a id="idm99329456" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/X11/doc/</code> — contains detailed documentation on the X Window System architecture, as well as how to get additional information about the Xorg project as a new user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/gdm-<em class="replaceable"><code><version-number></code></em>/README</code> — contains information on how display managers control user authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man xorg.conf</code> — Contains information about the <code class="filename">xorg.conf</code> configuration files, including the meaning and syntax for the different sections within the files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man Xorg</code> — Describes the <code class="command">Xorg</code> display server.
+ </div></li></ul></div></div><div class="section" id="s2-x-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.5.2. 役に立つ Web サイト</h3></div></div></div><a id="idm20518304" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.X.org/">http://www.X.org/</a> — Home page of the X.Org Foundation, which produces major releases of the X Window System bundled with Fedora to control the necessary hardware and provide a GUI environment.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://dri.sourceforge.net/">http://dri.sourceforge.net/</a> — Home page of the DRI (Direct Rendering Infrastructure) project. The DRI is the core hardware 3D acceleration component of X.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.gnome.org">http://www.gnome.org/</a> — Home of the GNOME project.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.kde.org">http://www.kde.org/</a> — Home of the KDE desktop environment.
+ </div></li></ul></div></div></div></div><div xml:lang="ja-JP" class="appendix" id="ch-The_sysconfig_Directory" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">sysconfig ディレクトリー</h1></div></div></div><a id="idm121522592" class="indexterm"></a><a id="idm94975824" class="indexterm"></a><div class="para">
+ This appendix outlines some of the files and directories found in the <code class="filename">/etc/sysconfig/</code> directory, their function, and their contents. The information in this appendix is not intended to be complete, as many of these files have a variety of options that are only used in very specific or rare circumstances.
+ </div><div class="note"><div class="admonition_header"><h2>The content of the /etc/sysconfig/ directory</h2></div><div class="admonition"><div class="para">
+ <code class="filename">/etc/sysconfig/</code> ディレクトリーの実際の内容は、マシンにインストールされているプログラムに依存します。設定ファイルが含まれるパッケージの名前を見つけるには、シェルプロンプトにおいて次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">yum provides /etc/sysconfig/<em class="replaceable"><code>filename</code></em> </code>
+</pre><div class="para">
+ Fedora にある新しいパッケージをインストールする方法に関する詳細は <a class="xref" href="#sec-Installing">「パッケージのインストール」</a> を参照してください。
+ </div></div></div><div class="section" id="s1-sysconfig-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">D.1. Files in the /etc/sysconfig/ Directory</h2></div></div></div><a id="idm107724240" class="indexterm"></a><div class="para">
+ The following sections offer descriptions of files normally found in the <code class="filename">/etc/sysconfig/</code> directory.
+ </div><div class="section" id="s2-sysconfig-arpwatch"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.1. /etc/sysconfig/arpwatch </h3></div></div></div><a id="idm87882064" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/arpwatch</code> file is used to pass arguments to the <code class="command">arpwatch</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">arpwatch</code> daemon. For example:
+ </div><pre class="screen">OPTIONS="-u arpwatch -e root -s 'root (Arpwatch)'"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-authconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.2. /etc/sysconfig/authconfig </h3></div></div></div><a id="idm107720224" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/authconfig</code> file sets the authorization to be used on the host. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">USEMKHOMEDIR=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) creating a home directory for a user on the first login. For example:
+ </div><pre class="screen">USEMKHOMEDIR=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEPAMACCESS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the PAM authentication. For example:
+ </div><pre class="screen">USEPAMACCESS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESSSDAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the SSSD authentication. For example:
+ </div><pre class="screen">USESSSDAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESHADOW=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) shadow passwords. For example:
+ </div><pre class="screen">USESHADOW=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEWINBIND=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using Winbind for user account configuration. For example:
+ </div><pre class="screen">USEWINBIND=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEDB=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the FAS authentication. For example:
+ </div><pre class="screen">USEDB=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEFPRINTD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the fingerprint authentication. For example:
+ </div><pre class="screen">USEFPRINTD=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">FORCESMARTCARD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) enforcing the smart card authentication. For example:
+ </div><pre class="screen">FORCESMARTCARD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PASSWDALGORITHM=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The password algorithm. The <em class="replaceable"><code>value</code></em> can be <code class="option">bigcrypt</code>, <code class="option">descrypt</code>, <code class="option">md5</code>, <code class="option">sha256</code>, or <code class="option">sha512</code>. For example:
+ </div><pre class="screen">PASSWDALGORITHM=sha512</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELDAPAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the LDAP authentication. For example:
+ </div><pre class="screen">USELDAPAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELOCAUTHORIZE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the local authorization for local users. For example:
+ </div><pre class="screen">USELOCAUTHORIZE=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USECRACKLIB=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the CrackLib. For example:
+ </div><pre class="screen">USECRACKLIB=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEWINBINDAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the Winbind authentication. For example:
+ </div><pre class="screen">USEWINBINDAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESMARTCARD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the smart card authentication. For example:
+ </div><pre class="screen">USESMARTCARD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELDAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using LDAP for user account configuration. For example:
+ </div><pre class="screen">USELDAP=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USENIS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using NIS for user account configuration. For example:
+ </div><pre class="screen">USENIS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEKERBEROS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the Kerberos authentication. For example:
+ </div><pre class="screen">USEKERBEROS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESYSNETAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) authenticating system accounts with network services. For example:
+ </div><pre class="screen">USESYSNETAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESMBAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the SMB authentication. For example:
+ </div><pre class="screen">USESMBAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESSSD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using SSSD for obtaining user information. For example:
+ </div><pre class="screen">USESSSD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEHESIOD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the Hesoid name service. For example:
+ </div><pre class="screen">USEHESIOD=no</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#ch-Configuring_Authentication">9章<em>認証の設定</em></a> for more information on this topic.
+ </div></div><div class="section" id="s2-sysconfig-autofs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.3. /etc/sysconfig/autofs </h3></div></div></div><a id="idm105115408" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/autofs</code> file defines custom options for the automatic mounting of devices. This file controls the operation of the automount daemons, which automatically mount file systems when you use them and unmount them after a period of inactivity. File systems can include network file systems, CD-ROM drives, diskettes, and other media.
+ </div><div class="para">
+ By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">MASTER_MAP_NAME=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default name for the master map. For example:
+ </div><pre class="screen">MASTER_MAP_NAME="auto.master"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default mount timeout. For example:
+ </div><pre class="screen">TIMEOUT=300</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">NEGATIVE_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default negative timeout for unsuccessful mount attempts. For example:
+ </div><pre class="screen">NEGATIVE_TIMEOUT=60</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOUNT_WAIT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for a response from <code class="command">mount</code>. For example:
+ </div><pre class="screen">MOUNT_WAIT=-1</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">UMOUNT_WAIT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for a response from <code class="command">umount</code>. For example:
+ </div><pre class="screen">UMOUNT_WAIT=12</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">BROWSE_MODE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) browsing the maps. For example:
+ </div><pre class="screen">BROWSE_MODE="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOUNT_NFS_DEFAULT_PROTOCOL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default protocol to be used by <code class="command">mount.nfs</code>. For example:
+ </div><pre class="screen">MOUNT_NFS_DEFAULT_PROTOCOL=4</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">APPEND_OPTIONS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) appending the global options instead of replacing them. For example:
+ </div><pre class="screen">APPEND_OPTIONS="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LOGGING=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default logging level. The <em class="replaceable"><code>value</code></em> has to be either <code class="option">none</code>, <code class="option">verbose</code>, or <code class="option">debug</code>. For example:
+ </div><pre class="screen">LOGGING="none"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_URI=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of server URIs in the form of <code class="systemitem"><em class="replaceable"><code>protocol</code></em>://<em class="replaceable"><code>server</code></em> </code>. For example:
+ </div><pre class="screen">LDAP_URI="ldaps://ldap.example.com/"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The synchronous API calls timeout. For example:
+ </div><pre class="screen">LDAP_TIMEOUT=-1</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_NETWORK_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The network response timeout. For example:
+ </div><pre class="screen">LDAP_NETWORK_TIMEOUT=8</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SEARCH_BASE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The base Distinguished Name (DN) for the map search. For example:
+ </div><pre class="screen">SEARCH_BASE=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">AUTH_CONF_FILE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default location of the SASL authentication configuration file. For example:
+ </div><pre class="screen">AUTH_CONF_FILE="/etc/autofs_ldap_auth.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MAP_HASH_TABLE_SIZE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The hash table size for the map cache. For example:
+ </div><pre class="screen">MAP_HASH_TABLE_SIZE=1024</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USE_MISC_DEVICE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the autofs miscellaneous device. For example:
+ </div><pre class="screen">USE_MISC_DEVICE="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the LDAP daemon. For example:
+ </div><pre class="screen">OPTIONS=""</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-clock"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.4. /etc/sysconfig/clock </h3></div></div></div><a id="idm109351088" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/clock</code> file controls the interpretation of values read from the system hardware clock. It is used by the <span class="application"><strong>Date and Time</strong></span> configuration tool, and should not be edited by hand. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">ZONE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time zone file under <code class="filename">/usr/share/zoneinfo</code> that <code class="filename">/etc/localtime</code> is a copy of. For example:
+ </div><pre class="screen">ZONE="Europe/Prague"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#sect-Configuring_the_Date_and_Time-Date_and_Time">「日付と時刻の設定ツールの使い方」</a> for more information on the <span class="application"><strong>Date and Time</strong></span> configuration tool and its usage.
+ </div></div><div class="section" id="s2-sysconfig-dhcpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.5. /etc/sysconfig/dhcpd </h3></div></div></div><a id="idm112026672" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/dhcpd</code> file is used to pass arguments to the <code class="command">dhcpd</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">DHCPDARGS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">dhcpd</code> daemon. For example:
+ </div><pre class="screen">DHCPDARGS=</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#ch-DHCP_Servers">11章<em>DHCP サーバー</em></a> for more information on DHCP and its usage.
+ </div></div><div class="section" id="s2-sysconfig-firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.6. /etc/sysconfig/firstboot </h3></div></div></div><a id="idm104637072" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/firstboot</code> file defines whether to run the <code class="command">firstboot</code> utility. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">RUN_FIRSTBOOT=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">YES</code>) or disable (<code class="option">NO</code>) running the <code class="command">firstboot</code> program. For example:
+ </div><pre class="screen">RUN_FIRSTBOOT=NO</pre></dd></dl></div><div class="para">
+ The first time the system boots, the <code class="command">init</code> program calls the <code class="filename">/etc/rc.d/init.d/firstboot</code> script, which looks for the <code class="filename">/etc/sysconfig/firstboot</code> file. If this file does not contain the <code class="option">RUN_FIRSTBOOT=NO</code> option, the <code class="command">firstboot</code> program is run, guiding a user through the initial configuration of the system.
+ </div><div class="note"><div class="admonition_header"><h2>You can run the firstboot program again</h2></div><div class="admonition"><div class="para">
+ To start the <code class="command">firstboot</code> program the next time the system boots, change the value of <code class="command">RUN_FIRSTBOOT</code> option to <code class="option">YES</code>, and type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl enable firstboot.service</code>
+</pre></div></div></div><div class="section" id="s2-sysconfig-i18n"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.7. /etc/sysconfig/i18n </h3></div></div></div><div class="para">
+ The <code class="filename">/etc/sysconfig/i18n</code> configuration file defines the default language, any supported languages, and the default system font. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">LANG=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default language. For example:
+ </div><pre class="screen">LANG="en_US.UTF-8"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SUPPORTED=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A colon-separated list of supported languages. For example:
+ </div><pre class="screen">SUPPORTED="en_US.UTF-8:en_US:en"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SYSFONT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default system font. For example:
+ </div><pre class="screen">SYSFONT="latarcyrheb-sun16"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-init"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.8. /etc/sysconfig/init </h3></div></div></div><a id="idm92647872" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/init</code> file controls how the system appears and functions during the boot process. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">BOOTUP=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The bootup style. The value has to be either <code class="option">color</code> (the standard color boot display), <code class="option">verbose</code> (an old style display which provides more information), or anything else for the new style display, but without ANSI formatting. For example:
+ </div><pre class="screen">BOOTUP=color</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RES_COL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The number of the column in which the status labels start. For example:
+ </div><pre class="screen">RES_COL=60</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOVE_TO_COL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to move the cursor to the column specified in <code class="option">RES_COL</code> (see above). For example:
+ </div><pre class="screen">MOVE_TO_COL="echo -en \\033[${RES_COL}G"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_SUCCESS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the success color. For example:
+ </div><pre class="screen">SETCOLOR_SUCCESS="echo -en \\033[0;32m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_FAILURE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the failure color. For example:
+ </div><pre class="screen">SETCOLOR_FAILURE="echo -en \\033[0;31m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_WARNING=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the warning color. For example:
+ </div><pre class="screen">SETCOLOR_WARNING="echo -en \\033[0;33m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_NORMAL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the default color. For example:
+ </div><pre class="screen">SETCOLOR_NORMAL="echo -en \\033[0;39m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LOGLEVEL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The initial console logging level. The <em class="replaceable"><code>value</code></em> has to be in the range from <code class="option">1</code> (kernel panics only) to <code class="option">8</code> (everything, including the debugging information). For example:
+ </div><pre class="screen">LOGLEVEL=3</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PROMPT=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the hotkey interactive startup. For example:
+ </div><pre class="screen">PROMPT=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">AUTOSWAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) probing for devices with swap signatures. For example:
+ </div><pre class="screen">AUTOSWAP=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ACTIVE_CONSOLES=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The list of active consoles. For example:
+ </div><pre class="screen">ACTIVE_CONSOLES=/dev/tty[1-6]</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SINGLE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The single-user mode type. The <em class="replaceable"><code>value</code></em> has to be either <code class="option">/sbin/sulogin</code> (a user will be prompted for a password to log in), or <code class="option">/sbin/sushell</code> (the user will be logged in directly). For example:
+ </div><pre class="screen">SINGLE=/sbin/sushell</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-ip6tables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.9. /etc/sysconfig/ip6tables-config </h3></div></div></div><a id="idm114441584" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ip6tables-config</code> file stores information used by the kernel to set up IPv6 packet filtering at boot time or whenever the <code class="command">ip6tables</code> service is started. Note that you should not modify it unless you are familiar with <code class="command">ip6tables</code> rules. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_MODULES=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of helpers to be loaded after the firewall rules are applied. For example:
+ </div><pre class="screen">IP6TABLES_MODULES="ip_nat_ftp ip_nat_irc"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_MODULES_UNLOAD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) module unloading when the firewall is stopped or restarted. For example:
+ </div><pre class="screen">IP6TABLES_MODULES_UNLOAD="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_ON_STOP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the current firewall rules when the firewall is stopped. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_ON_STOP="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_ON_RESTART=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the current firewall rules when the firewall is restarted. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_ON_RESTART="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_COUNTER=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the rule and chain counters. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_COUNTER="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_NUMERIC=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing IP addresses and port numbers in a numeric format in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_NUMERIC="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_VERBOSE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing information about the number of packets and bytes in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_VERBOSE="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_LINENUMBERS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing line numbers in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_LINENUMBERS="yes"</pre></dd></dl></div><div class="para">
+ </div><div class="note"><div class="admonition_header"><h2>Use the ip6tables command to create the rules</h2></div><div class="admonition"><div class="para">
+ You can create the rules manually using the <code class="command">ip6tables</code> command. Once created, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service ip6tables save</code>
+</pre><div class="para">
+ This will add the rules to <code class="filename">/etc/sysconfig/ip6tables</code>. Once this file exists, any firewall rules saved in it persist through a system reboot or a service restart.
+ </div></div></div></div><div class="section" id="s2-sysconfig-kybd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.10. /etc/sysconfig/keyboard </h3></div></div></div><a id="idm123540208" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/keyboard</code> file controls the behavior of the keyboard. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">KEYTABLE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The name of a keytable file. The files that can be used as keytables start in the <code class="filename">/lib/kbd/keymaps/i386/</code> directory, and branch into different keyboard layouts from there, all labeled <code class="filename"><em class="replaceable"><code>value</code></em>.kmap.gz</code>. The first file name that matches the <code class="option">KEYTABLE</code> setting is used. For example:
+ </div><pre class="screen">KEYTABLE="us"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MODEL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard model. For example:
+ </div><pre class="screen">MODEL="pc105+inet"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LAYOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard layout. For example:
+ </div><pre class="screen">LAYOUT="us"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">KEYBOARDTYPE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard type. Allowed values are <code class="option">pc</code> (a PS/2 keyboard), or <code class="option">sun</code> (a Sun keyboard). For example:
+ </div><pre class="screen">KEYBOARDTYPE="pc"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.11. /etc/sysconfig/ldap </h3></div></div></div><a id="idm113894272" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ldap</code> file holds the basic configuration for the LDAP server. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">slapd</code> daemon. For example:
+ </div><pre class="screen">SLAPD_OPTIONS="-4"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLURPD_OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">slurpd</code> daemon. For example:
+ </div><pre class="screen">SLURPD_OPTIONS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over TCP (that is, <code class="systemitem">ldap:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAP="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAPI=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over IPC (that is, <code class="systemitem">ldapi:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAPI="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAPS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over TLS (that is, <code class="systemitem">ldaps:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAPS="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_URLS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of URLs. For example:
+ </div><pre class="screen">SLAPD_URLS="ldapi:///var/lib/ldap_root/ldapi ldapi:/// ldaps:///"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_SHUTDOWN_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for <code class="command">slapd</code> to shut down. For example:
+ </div><pre class="screen">SLAPD_SHUTDOWN_TIMEOUT=3</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_ULIMIT_SETTINGS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The parameters to be passed to <code class="command">ulimit</code> before the <code class="command">slapd</code> daemon is started. For example:
+ </div><pre class="screen">SLAPD_ULIMIT_SETTINGS=""</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s1-OpenLDAP">「OpenLDAP」</a> for more information on LDAP and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-named"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.12. /etc/sysconfig/named </h3></div></div></div><a id="idm71726672" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/named</code> file is used to pass arguments to the <code class="command">named</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">ROOTDIR=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The chroot environment under which the <code class="command">named</code> daemon runs. The <em class="replaceable"><code>value</code></em> has to be a full directory path. For example:
+ </div><pre class="screen">ROOTDIR="/var/named/chroot"</pre><div class="para">
+ Note that the chroot environment has to be configured first (type <code class="command">info chroot</code> at a shell prompt for more information).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">named</code>. For example:
+ </div><pre class="screen">OPTIONS="-6"</pre><div class="para">
+ Note that you should not use the <code class="option">-t</code> option. Instead, use <code class="option">ROOTDIR</code> as described above.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">KEYTAB_FILE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keytab file name. For example:
+ </div><pre class="screen">KEYTAB_FILE="/etc/named.keytab"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s1-BIND">「BIND」</a> for more information on the BIND DNS server and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-network"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.13. /etc/sysconfig/network</h3></div></div></div><a id="idm121953360" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/network</code> file is used to specify information about the desired network configuration. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">NETWORKING=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the networking. For example:
+ </div><pre class="screen">NETWORKING=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">HOSTNAME=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The hostname of the machine. For example:
+ </div><pre class="screen">HOSTNAME=penguin.example.com</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">GATEWAY=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The IP address of the network's gateway. For example:
+ </div><pre class="screen">GATEWAY=192.168.1.0</pre></dd></dl></div><div class="warning"><div class="admonition_header"><h2>Avoid using custom init scripts</h2></div><div class="admonition"><div class="para">
+ Do not use custom init scripts to configure network settings. When performing a post-boot network service restart, custom init scripts configuring network settings that are run outside of the network init script lead to unpredictable results.
+ </div></div></div></div><div class="section" id="s2-sysconfig-ntpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.14. /etc/sysconfig/ntpd </h3></div></div></div><a id="idm119883408" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ntpd</code> file is used to pass arguments to the <code class="command">ntpd</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">ntpd</code>. For example:
+ </div><pre class="screen">OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid -g"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">「Network Time Protocol の設定」</a> for more information on how to configure the <code class="command">ntpd</code> daemon.
+ </div></div><div class="section" id="s2-sysconfig-quagga"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.15. /etc/sysconfig/quagga </h3></div></div></div><a id="idm118060400" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/quagga</code> file holds the basic configuration for Quagga daemons. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">QCONFDIR=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The directory with the configuration files for Quagga daemons. For example:
+ </div><pre class="screen">QCONFDIR="/etc/quagga"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">BGPD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">bgpd</code> daemon. For example:
+ </div><pre class="screen">BGPD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/bgpd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OSPF6D_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ospf6d</code> daemon. For example:
+ </div><pre class="screen">OSPF6D_OPTS="-A ::1 -f ${QCONFDIR}/ospf6d.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OSPFD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ospfd</code> daemon. For example:
+ </div><pre class="screen">OSPFD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/ospfd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RIPD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ripd</code> daemon. For example:
+ </div><pre class="screen">RIPD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/ripd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RIPNGD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ripngd</code> daemon. For example:
+ </div><pre class="screen">RIPNGD_OPTS="-A ::1 -f ${QCONFDIR}/ripngd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ZEBRA_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">zebra</code> daemon. For example:
+ </div><pre class="screen">ZEBRA_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/zebra.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ISISD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">isisd</code> daemon. For example:
+ </div><pre class="screen">ISISD_OPTS="-A ::1 -f ${QCONFDIR}/isisd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WATCH_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">watchquagga</code> daemon. For example:
+ </div><pre class="screen">WATCH_OPTS="-Az -b_ -r/sbin/service_%s_restart -s/sbin/service_%s_start -k/sbin/service_%s_stop"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WATCH_DAEMONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space separated list of monitored daemons. For example:
+ </div><pre class="screen">WATCH_DAEMONS="zebra bgpd ospfd ospf6d ripd ripngd"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-radvd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.16. /etc/sysconfig/radvd </h3></div></div></div><a id="idm124353824" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/radvd</code> file is used to pass arguments to the <code class="command">radvd</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">radvd</code> daemon. For example:
+ </div><pre class="screen">OPTIONS="-u radvd"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-samba"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.17. /etc/sysconfig/samba </h3></div></div></div><a id="idm85346272" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/samba</code> file is used to pass arguments to the Samba daemons at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SMBDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">smbd</code>. For example:
+ </div><pre class="screen">SMBDOPTIONS="-D"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">NMBDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">nmbd</code>. For example:
+ </div><pre class="screen">NMBDOPTIONS="-D"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WINBINDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">winbindd</code>. For example:
+ </div><pre class="screen">WINBINDOPTIONS=""</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s1-Samba">「Samba」</a> for more information on Samba and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-selinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.18. /etc/sysconfig/selinux </h3></div></div></div><a id="idm89585776" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/selinux</code> file contains the basic configuration options for SELinux. It is a symbolic link to <code class="filename">/etc/selinux/config</code>, and by default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SELINUX=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The security policy. The <em class="replaceable"><code>value </code></em> can be either <code class="option">enforcing</code> (the security policy is always enforced), <code class="option">permissive</code> (instead of enforcing the policy, appropriate warnings are displayed), or <code class="option">disabled</code> (no policy is used). For example:
+ </div><pre class="screen">SELINUX=enforcing</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SELINUXTYPE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The protection type. The <em class="replaceable"><code>value</code></em> can be either <code class="option">targeted</code> (the targeted processes are protected), or <code class="option">mls</code> (the Multi Level Security protection). For example:
+ </div><pre class="screen">SELINUXTYPE=targeted</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.19. /etc/sysconfig/sendmail </h3></div></div></div><a id="idm71385152" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/sendmail</code> is used to set the default values for the <span class="application"><strong>Sendmail</strong></span> application. By default, it contains the following values:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">DAEMON=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) running <code class="command">sendmail</code> as a daemon. For example:
+ </div><pre class="screen">DAEMON=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">QUEUE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The interval at which the messages are to be processed. For example:
+ </div><pre class="screen">QUEUE=1h</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s2-email-mta-sendmail">「Sendmail」</a> for more information on Sendmail and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-spamd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.20. /etc/sysconfig/spamassassin </h3></div></div></div><a id="idm124461920" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/spamassassin</code> file is used to pass arguments to the <code class="command">spamd</code> daemon (a daemonized version of <span class="application"><strong>Spamassassin</strong></span>) at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SPAMDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">spamd</code> daemon. For example:
+ </div><pre class="screen">SPAMDOPTIONS="-d -c -m5 -H"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s3-email-mda-spam">「スパムフィルタ」</a> for more information on Spamassassin and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-squid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.21. /etc/sysconfig/squid </h3></div></div></div><a id="idm133485632" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/squid</code> file is used to pass arguments to the <code class="command">squid</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SQUID_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">squid</code> daemon. For example:
+ </div><pre class="screen">SQUID_OPTS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SQUID_SHUTDOWN_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for <code class="command">squid</code> daemon to shut down. For example:
+ </div><pre class="screen">SQUID_SHUTDOWN_TIMEOUT=100</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SQUID_CONF=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default configuration file. For example:
+ </div><pre class="screen">SQUID_CONF="/etc/squid/squid.conf"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-rcu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.22. /etc/sysconfig/system-config-users </h3></div></div></div><a id="idm117178112" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/system-config-users</code> file is the configuration file for the <span class="application"><strong>User Manager</strong></span> utility, and should not be edited by hand. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">FILTER=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) filtering of system users. For example:
+ </div><pre class="screen">FILTER=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ASSIGN_HIGHEST_UID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) assigning the highest available UID to newly added users. For example:
+ </div><pre class="screen">ASSIGN_HIGHEST_UID=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ASSIGN_HIGHEST_GID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) assigning the highest available GID to newly added groups. For example:
+ </div><pre class="screen">ASSIGN_HIGHEST_GID=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PREFER_SAME_UID_GID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) using the same UID and GID for newly added users when possible. For example:
+ </div><pre class="screen">PREFER_SAME_UID_GID=true</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s1-users-configui">「ユーザー管理のツールを使う」</a> for more information on <span class="application"><strong>User Manager</strong></span> and its usage.
+ </div></div><div class="section" id="s2-sysconfig-vncservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.23. /etc/sysconfig/vncservers </h3></div></div></div><a id="idm114432976" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/vncservers</code> file configures the way the <em class="firstterm">Virtual Network Computing</em> (<em class="firstterm">VNC</em>) server starts up. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">VNCSERVERS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A list of space separated <code class="option"><em class="replaceable"><code>display</code></em>:<em class="replaceable"><code>username</code></em> </code> pairs. For example:
+ </div><pre class="screen">VNCSERVERS="2:myusername"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">VNCSERVERARGS[<em class="replaceable"><code>display</code></em>]=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional arguments to be passed to the VNC server running on the specified <em class="replaceable"><code>display</code></em>. For example:
+ </div><pre class="screen">VNCSERVERARGS[2]="-geometry 800x600 -nolisten tcp -localhost"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.24. /etc/sysconfig/xinetd </h3></div></div></div><a id="idm81240896" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/xinetd</code> file is used to pass arguments to the <code class="command">xinetd</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">EXTRAOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">xinetd</code>. For example:
+ </div><pre class="screen">EXTRAOPTIONS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">XINETD_LANG=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The locale information to be passed to every service started by <code class="command">xinetd</code>. Note that to remove locale information from the <code class="command">xinetd</code> environment, you can use an empty string (<code class="option">""</code>) or <code class="option">none</code>. For example:
+ </div><pre class="screen">XINETD_LANG="en_US"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#ch-Services_and_Daemons">8章<em>サービスおよびデーモン</em></a> for more information on how to configure the <code class="command">xinetd</code> services.
+ </div></div></div><div class="section" id="s1-sysconfig-etcsysconf-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">D.2. Directories in the /etc/sysconfig/ Directory</h2></div></div></div><a id="idm133140560" class="indexterm"></a><div class="para">
+ The following directories are normally found in <code class="filename">/etc/sysconfig/</code>.
+ </div><a id="idm133137520" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/cbq/</code> </span></dt><dd><div class="para">
+ <a id="idm102507440" class="indexterm"></a>
+ This directory contains the configuration files needed to do <em class="firstterm">Class Based Queuing</em> for bandwidth management on network interfaces. CBQ divides user traffic into a hierarchy of classes based on any combination of IP addresses, protocols, and application types.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/networking/</code> </span></dt><dd><div class="para">
+ <a id="idm53225936" class="indexterm"></a>
+ This directory is used by the <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>), and its contents should not be edited manually.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/network-scripts/</code> </span></dt><dd><div class="para">
+ <a id="idm69200160" class="indexterm"></a>
+ This directory contains the following network-related configuration files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Network configuration files for each configured network interface, such as <code class="filename">ifcfg-eth0</code> for the <code class="systemitem">eth0</code> Ethernet interface.
+ </div></li><li class="listitem"><div class="para">
+ Scripts used to bring network interfaces up and down, such as <code class="command">ifup</code> and <code class="command">ifdown</code>.
+ </div></li><li class="listitem"><div class="para">
+ Scripts used to bring ISDN interfaces up and down, such as <code class="command">ifup-isdn</code> and <code class="command">ifdown-isdn</code>.
+ </div></li><li class="listitem"><div class="para">
+ 直接編集すべきではない各種共有のネットワーク機能スクリプト。
+ </div></li></ul></div><div class="para">
+ For more information on the <code class="filename">/etc/sysconfig/network-scripts/</code> directory, refer to <a class="xref" href="#ch-Network_Interfaces">7章<em>ネットワーク・インターフェース</em></a>.
+ </div></dd></dl></div></div><div class="section" id="s1-sysconfig-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">D.3. その他のリソース</h2></div></div></div><a id="idp1768080" class="indexterm"></a><div class="para">
+ This chapter is only intended as an introduction to the files in the <code class="filename">/etc/sysconfig/</code> directory. The following source contains more comprehensive information.
+ </div><div class="section" id="s2-sysconfig-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.3.1. インストールされているドキュメント</h3></div></div></div><a id="idm104661568" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code>version</code></em>/sysconfig.txt</code></span></dt><dd><div class="para">
+ A more authoritative listing of the files found in the <code class="filename">/etc/sysconfig/</code> directory and the configuration options available for them.
+ </div></dd></dl></div></div></div></div><div xml:lang="ja-JP" class="appendix" id="ch-proc" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">The proc File System</h1></div></div></div><a id="idm110411312" class="indexterm"></a><a id="idm104774192" class="indexterm"></a><div class="para">
+ The Linux kernel has two primary functions: to control access to physical devices on the computer and to schedule when and how processes interact with these devices. The <code class="filename">/proc/</code> directory (also called the <code class="filename">proc</code> file system) contains a hierarchy of special files which represent the current state of the kernel, allowing applications and users to peer into the kernel's view of the system.
+ </div><div class="para">
+ The <code class="filename">/proc/</code> directory contains a wealth of information detailing system hardware and any running processes. In addition, some of the files within <code class="filename">/proc/</code> can be manipulated by users and applications to communicate configuration changes to the kernel.
+ </div><div class="note"><div class="admonition_header"><h2>The /proc/ide/ and /proc/pci/ directories</h2></div><div class="admonition"><div class="para">
+ Later versions of the 2.6 kernel have made the <code class="filename">/proc/ide/</code> and <code class="filename">/proc/pci/</code> directories obsolete. The <code class="command">/proc/ide/</code> file system is now superseded by files in <code class="command">sysfs</code>; to retrieve information on PCI devices, use <code class="command">lspci</code> instead. For more information on <code class="command">sysfs</code> or <code class="command">lspci</code>, refer to their respective <code class="command">man</code> pages.
+ </div></div></div><div class="section" id="s1-proc-virtual"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.1. A Virtual File System</h2></div></div></div><a id="idm104391504" class="indexterm"></a><a id="idm120956496" class="indexterm"></a><a id="idm59243360" class="indexterm"></a><div class="para">
+ Linux systems store all data as <span class="emphasis"><em>files</em></span>. Most users are familiar with the two primary types of files: text and binary. But the <code class="filename">/proc/</code> directory contains another type of file called a <em class="firstterm">virtual file</em>. As such, <code class="filename">/proc/</code> is often referred to as a <em class="firstterm">virtual file system</em>.
+ </div><div class="para">
+ Virtual files have unique qualities. Most of them are listed as zero bytes in size, but can still contain a large amount of information when viewed. In addition, most of the time and date stamps on virtual files reflect the current time and date, indicative of the fact they are constantly updated.
+ </div><div class="para">
+ Virtual files such as <code class="filename">/proc/interrupts</code>, <code class="filename">/proc/meminfo</code>, <code class="filename">/proc/mounts</code>, and <code class="filename">/proc/partitions</code> provide an up-to-the-moment glimpse of the system's hardware. Others, like the <code class="filename">/proc/filesystems</code> file and the <code class="filename">/proc/sys/</code> directory provide system configuration information and interfaces.
+ </div><div class="para">
+ For organizational purposes, files containing information on a similar topic are grouped into virtual directories and sub-directories. Process directories contain information about each running process on the system.
+ </div><div class="section" id="s2-proc-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.1.1. Viewing Virtual Files</h3></div></div></div><a id="idm126248640" class="indexterm"></a><a id="idm126247008" class="indexterm"></a><div class="para">
+ Most files within <code class="filename">/proc/</code> files operate similarly to text files, storing useful system and hardware data in human-readable text format. As such, you can use <code class="command">cat</code>, <code class="command">more</code>, or <code class="command">less</code> to view them. For example, to display information about the system's CPU, run <code class="command">cat /proc/cpuinfo</code>. This will return output similar to the following:
+ </div><pre class="screen">
+processor : 0
+vendor_id : AuthenticAMD
+cpu family : 5
+model : 9
+model name : AMD-K6(tm) 3D+
+Processor stepping : 1 cpu
+MHz : 400.919
+cache size : 256 KB
+fdiv_bug : no
+hlt_bug : no
+f00f_bug : no
+coma_bug : no
+fpu : yes
+fpu_exception : yes
+cpuid level : 1
+wp : yes
+flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
+bogomips : 799.53
+</pre><div class="para">
+ Some files in <code class="command">/proc/</code> contain information that is not human-readable. To retrieve information from such files, use tools such as <code class="command">lspci</code>, <code class="command">apm</code>, <code class="command">free</code>, and <code class="command">top</code>.
+ </div><div class="note"><div class="admonition_header"><h2>Certain files can only be accessed with root privileges</h2></div><div class="admonition"><div class="para">
+ Some of the virtual files in the <code class="filename">/proc/</code> directory are readable only by the root user.
+ </div></div></div></div><div class="section" id="s2-proc-change"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.1.2. Changing Virtual Files</h3></div></div></div><a id="idm84882320" class="indexterm"></a><a id="idm84880688" class="indexterm"></a><div class="para">
+ As a general rule, most virtual files within the <code class="filename">/proc/</code> directory are read-only. However, some can be used to adjust settings in the kernel. This is especially true for files in the <code class="filename">/proc/sys/</code> subdirectory.
+ </div><div class="para">
+ To change the value of a virtual file, use the following command:
+ </div><div class="para">
+ <code class="command">echo <em class="replaceable"><code>value</code></em> > /proc/<em class="replaceable"><code>file</code></em> </code>
+ </div><div class="para">
+ For example, to change the hostname on the fly, run:
+ </div><div class="para">
+ <code class="command">echo <em class="replaceable"><code>www.example.com</code></em> > /proc/sys/kernel/hostname </code>
+ </div><div class="para">
+ Other files act as binary or Boolean switches. Typing <code class="command">cat /proc/sys/net/ipv4/ip_forward</code> returns either a <code class="computeroutput">0</code> (off or false) or a <code class="computeroutput">1</code> (on or true). A <code class="computeroutput">0</code> indicates that the kernel is not forwarding network packets. To turn packet forwarding on, run <code class="command">echo 1 > /proc/sys/net/ipv4/ip_forward</code>.
+ </div><div class="note"><div class="admonition_header"><h2>The sysctl command</h2></div><div class="admonition"><div class="para">
+ Another command used to alter settings in the <code class="filename">/proc/sys/</code> subdirectory is <code class="command">/sbin/sysctl</code>. For more information on this command, refer to <a class="xref" href="#s1-proc-sysctl">「Using the sysctl Command」</a>
+ </div></div></div><div class="para">
+ For a listing of some of the kernel configuration files available in the <code class="filename">/proc/sys/</code> subdirectory, refer to <a class="xref" href="#s2-proc-dir-sys">「 /proc/sys/ 」</a>.
+ </div></div></div><div class="section" id="s1-proc-topfiles"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.2. Top-level Files within the <code class="filename">proc</code> File System</h2></div></div></div><a id="idm120229776" class="indexterm"></a><div class="para">
+ Below is a list of some of the more useful virtual files in the top-level of the <code class="filename">/proc/</code> directory.
+ </div><div class="note"><div class="admonition_header"><h2>The content of your files may differ</h2></div><div class="admonition"><div class="para">
+ In most cases, the content of the files listed in this section are not the same as those installed on your machine. This is because much of the information is specific to the hardware on which Fedora is running for this documentation effort.
+ </div></div></div><div class="section" id="s2-proc-buddyinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.1. /proc/buddyinfo </h3></div></div></div><a id="idm69107152" class="indexterm"></a><div class="para">
+ This file is used primarily for diagnosing memory fragmentation issues. Using the buddy algorithm, each column represents the number of pages of a certain order (a certain size) that are available at any given time. For example, for zone <em class="firstterm">direct memory access</em> (DMA), there are 90 of 2<sup>(0*PAGE_SIZE)</sup> chunks of memory. Similarly, there are 6 of 2<sup>(1*PAGE_SIZE)</sup> chunks, and 2 of 2<sup>(2*PAGE_SIZE)</sup> chunks of memory available.
+ </div><div class="para">
+ The <code class="computeroutput">DMA</code> row references the first 16 MB on a system, the <code class="computeroutput">HighMem</code> row references all memory greater than 4 GB on a system, and the <code class="computeroutput">Normal</code> row references all memory in between.
+ </div><div class="para">
+ The following is an example of the output typical of <code class="filename">/proc/buddyinfo</code>:
+ </div><pre class="screen">
+Node 0, zone DMA 90 6 2 1 1 ...
+Node 0, zone Normal 1650 310 5 0 0 ...
+Node 0, zone HighMem 2 0 0 1 1 ...
+</pre></div><div class="section" id="s2-proc-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.2. /proc/cmdline </h3></div></div></div><a id="idm47760448" class="indexterm"></a><div class="para">
+ This file shows the parameters passed to the kernel at the time it is started. A sample <code class="filename">/proc/cmdline</code> file looks like the following:
+ </div><pre class="screen">
+ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3
+</pre><div class="para">
+ This tells us that the kernel is mounted read-only (signified by <code class="computeroutput">(ro)</code>), located on the first logical volume (<code class="computeroutput">LogVol00</code>) of the first volume group (<code class="computeroutput">/dev/VolGroup00</code>). <code class="computeroutput">LogVol00</code> is the equivalent of a disk partition in a non-LVM system (Logical Volume Management), just as <code class="computeroutput">/dev/VolGroup00</code> is similar in concept to <code class="filename">/dev/hda1</code>, but much more extensible.
+ </div><div class="para">
+ For more information on LVM used in Fedora, refer to <a href="http://www.tldp.org/HOWTO/LVM-HOWTO/index.html">http://www.tldp.org/HOWTO/LVM-HOWTO/index.html</a>.
+ </div><div class="para">
+ Next, <code class="computeroutput">rhgb</code> signals that the <code class="filename">rhgb</code> package has been installed, and graphical booting is supported, assuming <code class="filename">/etc/inittab</code> shows a default runlevel set to <code class="command">id:5:initdefault:</code>.
+ </div><div class="para">
+ Finally, <code class="computeroutput">quiet</code> indicates all verbose kernel messages are suppressed at boot time.
+ </div></div><div class="section" id="s2-proc-cpuinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.3. /proc/cpuinfo </h3></div></div></div><a id="idm77735120" class="indexterm"></a><div class="para">
+ This virtual file identifies the type of processor used by your system. The following is an example of the output typical of <code class="filename">/proc/cpuinfo</code>:
+ </div><pre class="screen">
+processor : 0
+vendor_id : GenuineIntel
+cpu family : 15
+model : 2
+model name : Intel(R) Xeon(TM) CPU 2.40GHz
+stepping : 7 cpu
+MHz : 2392.371
+cache size : 512 KB
+physical id : 0
+siblings : 2
+runqueue : 0
+fdiv_bug : no
+hlt_bug : no
+f00f_bug : no
+coma_bug : no
+fpu : yes
+fpu_exception : yes
+cpuid level : 2
+wp : yes
+flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
+bogomips : 4771.02
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">processor</code> — Provides each processor with an identifying number. On systems that have one processor, only a <code class="computeroutput">0</code> is present.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu family</code> — Authoritatively identifies the type of processor in the system. For an Intel-based system, place the number in front of "86" to determine the value. This is particularly helpful for those attempting to identify the architecture of an older system such as a 586, 486, or 386. Because some RPM packages are compiled for each of these particular architectures, this value also helps users determine which packages to install.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">model name</code> — Displays the common name of the processor, including its project name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu MHz</code> — Shows the precise speed in megahertz for the processor to the thousandths decimal place.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cache size</code> — Displays the amount of level 2 memory cache available to the processor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">siblings</code> — Displays the number of sibling CPUs on the same physical CPU for architectures which use hyper-threading.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">flags</code> — Defines a number of different qualities about the processor, such as the presence of a floating point unit (FPU) and the ability to process MMX instructions.
+ </div></li></ul></div></div><div class="section" id="s2-proc-crypto"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.4. /proc/crypto </h3></div></div></div><a id="idm122134912" class="indexterm"></a><div class="para">
+ This file lists all installed cryptographic ciphers used by the Linux kernel, including additional details for each. A sample <code class="filename">/proc/crypto</code> file looks like the following:
+ </div><pre class="screen">
+name : sha1
+module : kernel
+type : digest
+blocksize : 64
+digestsize : 20
+name : md5
+module : md5
+type : digest
+blocksize : 64
+digestsize : 16
+</pre></div><div class="section" id="s2-proc-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.5. /proc/devices </h3></div></div></div><a id="idm89303296" class="indexterm"></a><a id="idm89300224" class="indexterm"></a><a id="idm72651536" class="indexterm"></a><a id="idm72649904" class="indexterm"></a><a id="idm72647792" class="indexterm"></a><a id="idm95740720" class="indexterm"></a><div class="para">
+ This file displays the various character and block devices currently configured (not including devices whose modules are not loaded). Below is a sample output from this file:
+ </div><pre class="screen">
+Character devices:
+ 1 mem
+ 4 /dev/vc/0
+ 4 tty
+ 4 ttyS
+ 5 /dev/tty
+ 5 /dev/console
+ 5 /dev/ptmx
+ 7 vcs
+ 10 misc
+ 13 input
+ 29 fb
+ 36 netlink
+ 128 ptm
+ 136 pts
+ 180 usb
+
+Block devices:
+ 1 ramdisk
+ 3 ide0
+ 9 md
+ 22 ide1
+ 253 device-mapper
+ 254 mdp
+</pre><div class="para">
+ The output from <code class="filename">/proc/devices</code> includes the major number and name of the device, and is broken into two major sections: <code class="computeroutput">Character devices</code> and <code class="computeroutput">Block devices</code>.
+ </div><div class="para">
+ <em class="firstterm">Character devices</em> are similar to <em class="firstterm">block devices</em>, except for two basic differences:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Character devices do not require buffering. Block devices have a buffer available, allowing them to order requests before addressing them. This is important for devices designed to store information — such as hard drives — because the ability to order the information before writing it to the device allows it to be placed in a more efficient order.
+ </div></li><li class="listitem"><div class="para">
+ Character devices send data with no preconfigured size. Block devices can send and receive information in blocks of a size configured per device.
+ </div></li></ol></div><div class="para">
+ For more information about devices refer to the following installed documentation:
+ </div><pre class="screen">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/devices.txt</pre></div><div class="section" id="s2-proc-dma"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.6. /proc/dma </h3></div></div></div><a id="idm106968656" class="indexterm"></a><div class="para">
+ This file contains a list of the registered ISA DMA channels in use. A sample <code class="filename">/proc/dma</code> files looks like the following:
+ </div><pre class="screen">
+4: cascade
+</pre></div><div class="section" id="s2-proc-execdomains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.7. /proc/execdomains </h3></div></div></div><a id="idm106963472" class="indexterm"></a><a id="idm60649744" class="indexterm"></a><a id="idm60647632" class="indexterm"></a><div class="para">
+ This file lists the <em class="firstterm">execution domains</em> currently supported by the Linux kernel, along with the range of personalities they support.
+ </div><pre class="screen">
+0-0 Linux [kernel]
+</pre><div class="para">
+ Think of execution domains as the "personality" for an operating system. Because other binary formats, such as Solaris, UnixWare, and FreeBSD, can be used with Linux, programmers can change the way the operating system treats system calls from these binaries by changing the personality of the task. Except for the <code class="computeroutput">PER_LINUX</code> execution domain, different personalities can be implemented as dynamically loadable modules.
+ </div></div><div class="section" id="s2-proc-fb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.8. /proc/fb </h3></div></div></div><a id="idm135801008" class="indexterm"></a><a id="idm135798416" class="indexterm"></a><div class="para">
+ This file contains a list of frame buffer devices, with the frame buffer device number and the driver that controls it. Typical output of <code class="filename">/proc/fb</code> for systems which contain frame buffer devices looks similar to the following:
+ </div><pre class="screen">
+0 VESA VGA
+</pre></div><div class="section" id="s2-proc-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.9. /proc/filesystems </h3></div></div></div><a id="idm190570800" class="indexterm"></a><div class="para">
+ This file displays a list of the file system types currently supported by the kernel. Sample output from a generic <code class="filename">/proc/filesystems</code> file looks similar to the following:
+ </div><pre class="screen">
+nodev sysfs
+nodev rootfs
+nodev bdev
+nodev proc
+nodev sockfs
+nodev binfmt_misc
+nodev usbfs
+nodev usbdevfs
+nodev futexfs
+nodev tmpfs
+nodev pipefs
+nodev eventpollfs
+nodev devpts
+ ext2
+nodev ramfs
+nodev hugetlbfs
+ iso9660
+nodev mqueue
+ ext3
+nodev rpc_pipefs
+nodev autofs
+</pre><div class="para">
+ The first column signifies whether the file system is mounted on a block device. Those beginning with <code class="computeroutput">nodev</code> are not mounted on a device. The second column lists the names of the file systems supported.
+ </div><div class="para">
+ The <code class="command">mount</code> command cycles through the file systems listed here when one is not specified as an argument.
+ </div></div><div class="section" id="s2-proc-interrupts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.10. /proc/interrupts </h3></div></div></div><a id="idm129188192" class="indexterm"></a><div class="para">
+ This file records the number of interrupts per IRQ on the x86 architecture. A standard <code class="filename">/proc/interrupts</code> looks similar to the following:
+ </div><pre class="screen">
+ CPU0
+ 0: 80448940 XT-PIC timer
+ 1: 174412 XT-PIC keyboard
+ 2: 0 XT-PIC cascade
+ 8: 1 XT-PIC rtc
+ 10: 410964 XT-PIC eth0
+ 12: 60330 XT-PIC PS/2 Mouse
+ 14: 1314121 XT-PIC ide0
+ 15: 5195422 XT-PIC ide1
+NMI: 0
+ERR: 0
+</pre><div class="para">
+ For a multi-processor machine, this file may look slightly different:
+ </div><pre class="screen">
+ CPU0 CPU1
+ 0: 1366814704 0 XT-PIC timer
+ 1: 128 340 IO-APIC-edge keyboard
+ 2: 0 0 XT-PIC cascade
+ 8: 0 1 IO-APIC-edge rtc
+ 12: 5323 5793 IO-APIC-edge PS/2 Mouse
+ 13: 1 0 XT-PIC fpu
+ 16: 11184294 15940594 IO-APIC-level Intel EtherExpress Pro 10/100 Ethernet
+ 20: 8450043 11120093 IO-APIC-level megaraid
+ 30: 10432 10722 IO-APIC-level aic7xxx
+ 31: 23 22 IO-APIC-level aic7xxx
+NMI: 0
+ERR: 0
+</pre><div class="para">
+ The first column refers to the IRQ number. Each CPU in the system has its own column and its own number of interrupts per IRQ. The next column reports the type of interrupt, and the last column contains the name of the device that is located at that IRQ.
+ </div><div class="para">
+ Each of the types of interrupts seen in this file, which are architecture-specific, mean something different. For x86 machines, the following values are common:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">XT-PIC</code> — This is the old AT computer interrupts.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">IO-APIC-edge</code> — The voltage signal on this interrupt transitions from low to high, creating an <span class="emphasis"><em>edge</em></span>, where the interrupt occurs and is only signaled once. This kind of interrupt, as well as the <code class="computeroutput">IO-APIC-level</code> interrupt, are only seen on systems with processors from the 586 family and higher.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">IO-APIC-level</code> — Generates interrupts when its voltage signal is high until the signal is low again.
+ </div></li></ul></div></div><div class="section" id="s2-proc-iomem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.11. /proc/iomem </h3></div></div></div><a id="idm126414928" class="indexterm"></a><div class="para">
+ This file shows you the current map of the system's memory for each physical device:
+ </div><pre class="screen">
+00000000-0009fbff : System RAM
+0009fc00-0009ffff : reserved
+000a0000-000bffff : Video RAM area
+000c0000-000c7fff : Video ROM
+000f0000-000fffff : System ROM
+00100000-07ffffff : System RAM
+00100000-00291ba8 : Kernel code
+00291ba9-002e09cb : Kernel data
+e0000000-e3ffffff : VIA Technologies, Inc. VT82C597 [Apollo VP3] e4000000-e7ffffff : PCI Bus #01
+e4000000-e4003fff : Matrox Graphics, Inc. MGA G200 AGP
+e5000000-e57fffff : Matrox Graphics, Inc. MGA G200 AGP
+e8000000-e8ffffff : PCI Bus #01
+e8000000-e8ffffff : Matrox Graphics, Inc. MGA G200 AGP
+ea000000-ea00007f : Digital Equipment Corporation DECchip 21140 [FasterNet]
+ea000000-ea00007f : tulip ffff0000-ffffffff : reserved
+</pre><div class="para">
+ The first column displays the memory registers used by each of the different types of memory. The second column lists the kind of memory located within those registers and displays which memory registers are used by the kernel within the system RAM or, if the network interface card has multiple Ethernet ports, the memory registers assigned for each port.
+ </div></div><div class="section" id="s2-proc-ioports"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.12. /proc/ioports </h3></div></div></div><a id="idm93187936" class="indexterm"></a><div class="para">
+ The output of <code class="filename">/proc/ioports</code> provides a list of currently registered port regions used for input or output communication with a device. This file can be quite long. The following is a partial listing:
+ </div><pre class="screen">
+0000-001f : dma1
+0020-003f : pic1
+0040-005f : timer
+0060-006f : keyboard
+0070-007f : rtc
+0080-008f : dma page reg
+00a0-00bf : pic2
+00c0-00df : dma2
+00f0-00ff : fpu
+0170-0177 : ide1
+01f0-01f7 : ide0
+02f8-02ff : serial(auto)
+0376-0376 : ide1
+03c0-03df : vga+
+03f6-03f6 : ide0
+03f8-03ff : serial(auto)
+0cf8-0cff : PCI conf1
+d000-dfff : PCI Bus #01
+e000-e00f : VIA Technologies, Inc. Bus Master IDE
+e000-e007 : ide0
+e008-e00f : ide1
+e800-e87f : Digital Equipment Corporation DECchip 21140 [FasterNet]
+e800-e87f : tulip
+</pre><div class="para">
+ The first column gives the I/O port address range reserved for the device listed in the second column.
+ </div></div><div class="section" id="s2-proc-kcore"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.13. /proc/kcore </h3></div></div></div><a id="idm82068880" class="indexterm"></a><div class="para">
+ This file represents the physical memory of the system and is stored in the core file format. Unlike most <code class="filename">/proc/</code> files, <code class="filename">kcore</code> displays a size. This value is given in bytes and is equal to the size of the physical memory (RAM) used plus 4 KB.
+ </div><div class="para">
+ The contents of this file are designed to be examined by a debugger, such as <code class="command">gdb</code>, and is not human readable.
+ </div><div class="warning"><div class="admonition_header"><h2>Do not attempt to view the content of /proc/kcore</h2></div><div class="admonition"><div class="para">
+ Do not view the <code class="filename">/proc/kcore</code> virtual file. The contents of the file scramble text output on the terminal. If this file is accidentally viewed, press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>C</strong></span> to stop the process and then type <code class="command">reset</code> to bring back the command line prompt.
+ </div></div></div></div><div class="section" id="s2-proc-kmsg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.14. /proc/kmsg </h3></div></div></div><a id="idm98762320" class="indexterm"></a><div class="para">
+ This file is used to hold messages generated by the kernel. These messages are then picked up by other programs, such as <code class="command">/sbin/klogd</code> or <code class="command">/bin/dmesg</code>.
+ </div></div><div class="section" id="s2-proc-loadavg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.15. /proc/loadavg </h3></div></div></div><a id="idm80325104" class="indexterm"></a><div class="para">
+ This file provides a look at the load average in regard to both the CPU and IO over time, as well as additional data used by <code class="command">uptime</code> and other commands. A sample <code class="filename">/proc/loadavg</code> file looks similar to the following:
+ </div><pre class="screen">
+0.20 0.18 0.12 1/80 11206
+</pre><div class="para">
+ The first three columns measure CPU and IO utilization of the last one, five, and 15 minute periods. The fourth column shows the number of currently running processes and the total number of processes. The last column displays the last process ID used.
+ </div><div class="para">
+ In addition, load average also refers to the number of processes ready to run (i.e. in the run queue, waiting for a CPU share.
+ </div></div><div class="section" id="s2-proc-locks"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.16. /proc/locks </h3></div></div></div><a id="idm127872976" class="indexterm"></a><div class="para">
+ This file displays the files currently locked by the kernel. The contents of this file contain internal kernel debugging data and can vary tremendously, depending on the use of the system. A sample <code class="filename">/proc/locks</code> file for a lightly loaded system looks similar to the following:
+ </div><pre class="screen">
+1: POSIX ADVISORY WRITE 3568 fd:00:2531452 0 EOF
+2: FLOCK ADVISORY WRITE 3517 fd:00:2531448 0 EOF
+3: POSIX ADVISORY WRITE 3452 fd:00:2531442 0 EOF
+4: POSIX ADVISORY WRITE 3443 fd:00:2531440 0 EOF
+5: POSIX ADVISORY WRITE 3326 fd:00:2531430 0 EOF
+6: POSIX ADVISORY WRITE 3175 fd:00:2531425 0 EOF
+7: POSIX ADVISORY WRITE 3056 fd:00:2548663 0 EOF
+</pre><div class="para">
+ Each lock has its own line which starts with a unique number. The second column refers to the class of lock used, with <code class="computeroutput">FLOCK</code> signifying the older-style UNIX file locks from a <code class="command">flock</code> system call and <code class="computeroutput">POSIX</code> representing the newer POSIX locks from the <code class="command">lockf</code> system call.
+ </div><div class="para">
+ The third column can have two values: <code class="computeroutput">ADVISORY</code> or <code class="computeroutput">MANDATORY</code>. <code class="computeroutput">ADVISORY</code> means that the lock does not prevent other people from accessing the data; it only prevents other attempts to lock it. <code class="computeroutput">MANDATORY</code> means that no other access to the data is permitted while the lock is held. The fourth column reveals whether the lock is allowing the holder <code class="computeroutput">READ</code> or <code class="computeroutput">WRITE</code> access to the file. The fifth column shows the ID of the process holding the lock. The sixth column shows the ID of the file being locked, in the format of <code class="computeroutput"><em class="replaceable"><code>MAJOR-DEVICE</code></em>:<em class="replaceable"><code>MINOR-DEVICE</code></em>:<em class="replaceable"><code>INODE-NUMBER</code></em> </code>. The seventh and eighth column shows the start and end o
f the file's locked region.
+ </div></div><div class="section" id="s2-proc-mdstat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.17. /proc/mdstat </h3></div></div></div><a id="idm90848736" class="indexterm"></a><div class="para">
+ This file contains the current information for multiple-disk, RAID configurations. If the system does not contain such a configuration, then <code class="filename">/proc/mdstat</code> looks similar to the following:
+ </div><pre class="screen">
+Personalities : read_ahead not set unused devices: <none>
+</pre><div class="para">
+ This file remains in the same state as seen above unless a software RAID or <code class="filename">md</code> device is present. In that case, view <code class="filename">/proc/mdstat</code> to find the current status of <code class="filename">md<em class="replaceable"><code>X</code></em> </code> RAID devices.
+ </div><div class="para">
+ The <code class="filename">/proc/mdstat</code> file below shows a system with its <code class="filename">md0</code> configured as a RAID 1 device, while it is currently re-syncing the disks:
+ </div><pre class="screen">
+Personalities : [linear] [raid1] read_ahead 1024 sectors
+md0: active raid1 sda2[1] sdb2[0] 9940 blocks [2/2] [UU] resync=1% finish=12.3min algorithm 2 [3/3] [UUU]
+unused devices: <none>
+</pre></div><div class="section" id="s2-proc-meminfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.18. /proc/meminfo </h3></div></div></div><a id="idp1743440" class="indexterm"></a><div class="para">
+ This is one of the more commonly used files in the <code class="filename">/proc/</code> directory, as it reports a large amount of valuable information about the systems RAM usage.
+ </div><div class="para">
+ The following sample <code class="filename">/proc/meminfo</code> virtual file is from a system with 256 MB of RAM and 512 MB of swap space:
+ </div><pre class="screen">
+MemTotal: 255908 kB
+MemFree: 69936 kB
+Buffers: 15812 kB
+Cached: 115124 kB
+SwapCached: 0 kB
+Active: 92700 kB
+Inactive: 63792 kB
+HighTotal: 0 kB
+HighFree: 0 kB
+LowTotal: 255908 kB
+LowFree: 69936 kB
+SwapTotal: 524280 kB
+SwapFree: 524280 kB
+Dirty: 4 kB
+Writeback: 0 kB
+Mapped: 42236 kB
+Slab: 25912 kB
+Committed_AS: 118680 kB
+PageTables: 1236 kB
+VmallocTotal: 3874808 kB
+VmallocUsed: 1416 kB
+VmallocChunk: 3872908 kB
+HugePages_Total: 0
+HugePages_Free: 0
+Hugepagesize: 4096 kB
+</pre><div class="para">
+ Much of the information here is used by the <code class="command">free</code>, <code class="command">top</code>, and <code class="command">ps</code> commands. In fact, the output of the <code class="command">free</code> command is similar in appearance to the contents and structure of <code class="filename">/proc/meminfo</code>. But by looking directly at <code class="filename">/proc/meminfo</code>, more details are revealed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">MemTotal</code> — Total amount of physical RAM, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">MemFree</code> — The amount of physical RAM, in kilobytes, left unused by the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Buffers</code> — The amount of physical RAM, in kilobytes, used for file buffers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Cached</code> — The amount of physical RAM, in kilobytes, used as cache memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapCached</code> — The amount of swap, in kilobytes, used as cache memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Active</code> — The total amount of buffer or page cache memory, in kilobytes, that is in active use. This is memory that has been recently used and is usually not reclaimed for other purposes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Inactive</code> — The total amount of buffer or page cache memory, in kilobytes, that are free and available. This is memory that has not been recently used and can be reclaimed for other purposes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HighTotal</code> and <code class="computeroutput">HighFree</code> — The total and free amount of memory, in kilobytes, that is not directly mapped into kernel space. The <code class="computeroutput">HighTotal</code> value can vary based on the type of kernel used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">LowTotal</code> and <code class="computeroutput">LowFree</code> — The total and free amount of memory, in kilobytes, that is directly mapped into kernel space. The <code class="computeroutput">LowTotal</code> value can vary based on the type of kernel used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapTotal</code> — The total amount of swap available, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapFree</code> — The total amount of swap free, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Dirty</code> — The total amount of memory, in kilobytes, waiting to be written back to the disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Writeback</code> — The total amount of memory, in kilobytes, actively being written back to the disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Mapped</code> — The total amount of memory, in kilobytes, which have been used to map devices, files, or libraries using the <code class="command">mmap</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Slab</code> — The total amount of memory, in kilobytes, used by the kernel to cache data structures for its own use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Committed_AS</code> — The total amount of memory, in kilobytes, estimated to complete the workload. This value represents the worst case scenario value, and also includes swap memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">PageTables</code> — The total amount of memory, in kilobytes, dedicated to the lowest page table level.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocTotal</code> — The total amount of memory, in kilobytes, of total allocated virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocUsed</code> — The total amount of memory, in kilobytes, of used virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocChunk</code> — The largest contiguous block of memory, in kilobytes, of available virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HugePages_Total</code> — The total number of hugepages for the system. The number is derived by dividing <code class="computeroutput">Hugepagesize</code> by the megabytes set aside for hugepages specified in <code class="filename">/proc/sys/vm/hugetlb_pool</code>. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HugePages_Free</code> — The total number of hugepages available for the system. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Hugepagesize</code> — The size for each hugepages unit in kilobytes. By default, the value is 4096 KB on uniprocessor kernels for 32 bit architectures. For SMP, hugemem kernels, and AMD64, the default is 2048 KB. For Itanium architectures, the default is 262144 KB. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li></ul></div></div><div class="section" id="s2-proc-misc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.19. /proc/misc </h3></div></div></div><a id="idm59202848" class="indexterm"></a><div class="para">
+ This file lists miscellaneous drivers registered on the miscellaneous major device, which is device number 10:
+ </div><pre class="screen">
+63 device-mapper 175 agpgart 135 rtc 134 apm_bios
+</pre><div class="para">
+ The first column is the minor number of each device, while the second column shows the driver in use.
+ </div></div><div class="section" id="s2-proc-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.20. /proc/modules </h3></div></div></div><a id="idm111646976" class="indexterm"></a><div class="para">
+ This file displays a list of all modules loaded into the kernel. Its contents vary based on the configuration and use of your system, but it should be organized in a similar manner to this sample <code class="filename">/proc/modules</code> file output:
+ </div><div class="note"><div class="admonition_header"><h2>The content of /proc/modules</h2></div><div class="admonition"><div class="para">
+ This example has been reformatted into a readable format. Most of this information can also be viewed via the <code class="command">/sbin/lsmod</code> command.
+ </div></div></div><pre class="screen">
+nfs 170109 0 - Live 0x129b0000
+lockd 51593 1 nfs, Live 0x128b0000
+nls_utf8 1729 0 - Live 0x12830000
+vfat 12097 0 - Live 0x12823000
+fat 38881 1 vfat, Live 0x1287b000
+autofs4 20293 2 - Live 0x1284f000
+sunrpc 140453 3 nfs,lockd, Live 0x12954000
+3c59x 33257 0 - Live 0x12871000
+uhci_hcd 28377 0 - Live 0x12869000
+md5 3777 1 - Live 0x1282c000
+ipv6 211845 16 - Live 0x128de000
+ext3 92585 2 - Live 0x12886000
+jbd 65625 1 ext3, Live 0x12857000
+dm_mod 46677 3 - Live 0x12833000
+</pre><div class="para">
+ The first column contains the name of the module.
+ </div><div class="para">
+ The second column refers to the memory size of the module, in bytes.
+ </div><div class="para">
+ The third column lists how many instances of the module are currently loaded. A value of zero represents an unloaded module.
+ </div><div class="para">
+ The fourth column states if the module depends upon another module to be present in order to function, and lists those other modules.
+ </div><div class="para">
+ The fifth column lists what load state the module is in: <code class="command">Live</code>, <code class="command">Loading</code>, or <code class="command">Unloading</code> are the only possible values.
+ </div><div class="para">
+ The sixth column lists the current kernel memory offset for the loaded module. This information can be useful for debugging purposes, or for profiling tools such as <code class="filename">oprofile</code>.
+ </div></div><div class="section" id="s2-proc-mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.21. /proc/mounts </h3></div></div></div><a id="idm132295424" class="indexterm"></a><div class="para">
+ This file provides a list of all mounts in use by the system:
+ </div><pre class="screen">
+rootfs / rootfs rw 0 0
+/proc /proc proc rw,nodiratime 0 0 none
+/dev ramfs rw 0 0
+/dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0
+none /dev ramfs rw 0 0
+/proc /proc proc rw,nodiratime 0 0
+/sys /sys sysfs rw 0 0
+none /dev/pts devpts rw 0 0
+usbdevfs /proc/bus/usb usbdevfs rw 0 0
+/dev/hda1 /boot ext3 rw 0 0
+none /dev/shm tmpfs rw 0 0
+none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
+sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
+</pre><div class="para">
+ The output found here is similar to the contents of <code class="filename">/etc/mtab</code>, except that <code class="filename">/proc/mounts</code> is more up-to-date.
+ </div><div class="para">
+ The first column specifies the device that is mounted, the second column reveals the mount point, and the third column tells the file system type, and the fourth column tells you if it is mounted read-only (<code class="computeroutput">ro</code>) or read-write (<code class="computeroutput">rw</code>). The fifth and sixth columns are dummy values designed to match the format used in <code class="filename">/etc/mtab</code>.
+ </div></div><div class="section" id="s2-proc-mtrr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.22. /proc/mtrr </h3></div></div></div><a id="idm120748368" class="indexterm"></a><div class="para">
+ This file refers to the current Memory Type Range Registers (MTRRs) in use with the system. If the system architecture supports MTRRs, then the <code class="filename">/proc/mtrr</code> file may look similar to the following:
+ </div><pre class="screen">
+reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
+reg01: base=0xe8000000 (3712MB), size= 32MB: write-combining, count=1
+</pre><div class="para">
+ MTRRs are used with the Intel P6 family of processors (Pentium II and higher) and control processor access to memory ranges. When using a video card on a PCI or AGP bus, a properly configured <code class="filename">/proc/mtrr</code> file can increase performance more than 150%.
+ </div><div class="para">
+ Most of the time, this value is properly configured by default. More information on manually configuring this file can be found locally at the following location:
+ </div><pre class="screen">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/<em class="replaceable"><code><arch></code></em>/mtrr.txt</pre></div><div class="section" id="s2-proc-partitions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.23. /proc/partitions </h3></div></div></div><a id="idm95981840" class="indexterm"></a><div class="para">
+ This file contains partition block allocation information. A sampling of this file from a basic system looks similar to the following:
+ </div><pre class="screen">
+major minor #blocks name
+ 3 0 19531250 hda
+ 3 1 104391 hda1
+ 3 2 19422585 hda2
+253 0 22708224 dm-0
+253 1 524288 dm-1
+</pre><div class="para">
+ Most of the information here is of little importance to the user, except for the following columns:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">major</code> — The major number of the device with this partition. The major number in the <code class="filename">/proc/partitions</code>, (<code class="computeroutput">3</code>), corresponds with the block device <code class="computeroutput">ide0</code>, in <code class="filename">/proc/devices</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">minor</code> — The minor number of the device with this partition. This serves to separate the partitions into different physical devices and relates to the number at the end of the name of the partition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">#blocks</code> — Lists the number of physical disk blocks contained in a particular partition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">name</code> — The name of the partition.
+ </div></li></ul></div></div><div class="section" id="s2-proc-slabinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.24. /proc/slabinfo </h3></div></div></div><a id="idm95246640" class="indexterm"></a><a id="idm95243936" class="indexterm"></a><div class="para">
+ This file gives full information about memory usage on the <em class="firstterm">slab</em> level. Linux kernels greater than version 2.2 use <em class="firstterm">slab pools</em> to manage memory above the page level. Commonly used objects have their own slab pools.
+ </div><div class="para">
+ Instead of parsing the highly verbose <code class="filename">/proc/slabinfo</code> file manually, the <code class="filename">/usr/bin/slabtop</code> program displays kernel slab cache information in real time. This program allows for custom configurations, including column sorting and screen refreshing.
+ </div><div class="para">
+ A sample screen shot of <code class="filename">/usr/bin/slabtop</code> usually looks like the following example:
+ </div><pre class="screen">
+Active / Total Objects (% used) : 133629 / 147300 (90.7%)
+Active / Total Slabs (% used) : 11492 / 11493 (100.0%)
+Active / Total Caches (% used) : 77 / 121 (63.6%)
+Active / Total Size (% used) : 41739.83K / 44081.89K (94.7%)
+Minimum / Average / Maximum Object : 0.01K / 0.30K / 128.00K
+OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
+44814 43159 96% 0.62K 7469 6 29876K ext3_inode_cache
+36900 34614 93% 0.05K 492 75 1968K buffer_head
+35213 33124 94% 0.16K 1531 23 6124K dentry_cache
+7364 6463 87% 0.27K 526 14 2104K radix_tree_node
+2585 1781 68% 0.08K 55 47 220K vm_area_struct
+2263 2116 93% 0.12K 73 31 292K size-128
+1904 1125 59% 0.03K 16 119 64K size-32
+1666 768 46% 0.03K 14 119 56K anon_vma
+1512 1482 98% 0.44K 168 9 672K inode_cache
+1464 1040 71% 0.06K 24 61 96K size-64
+1320 820 62% 0.19K 66 20 264K filp
+678 587 86% 0.02K 3 226 12K dm_io
+678 587 86% 0.02K 3 226 12K dm_tio
+576 574 99% 0.47K 72 8 288K proc_inode_cache
+528 514 97% 0.50K 66 8 264K size-512
+492 372 75% 0.09K 12 41 48K bio
+465 314 67% 0.25K 31 15 124K size-256
+452 331 73% 0.02K 2 226 8K biovec-1
+420 420 100% 0.19K 21 20 84K skbuff_head_cache
+305 256 83% 0.06K 5 61 20K biovec-4
+290 4 1% 0.01K 1 290 4K revoke_table
+264 264 100% 4.00K 264 1 1056K size-4096
+260 256 98% 0.19K 13 20 52K biovec-16
+260 256 98% 0.75K 52 5 208K biovec-64
+</pre><div class="para">
+ Some of the more commonly used statistics in <code class="filename">/proc/slabinfo</code> that are included into <code class="filename">/usr/bin/slabtop</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJS</code> — The total number of objects (memory blocks), including those in use (allocated), and some spares not in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">ACTIVE</code> — The number of objects (memory blocks) that are in use (allocated).
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">USE</code> — Percentage of total objects that are active. ((ACTIVE/OBJS)(100))
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJ SIZE</code> — The size of the objects.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SLABS</code> — The total number of slabs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJ/SLAB</code> — The number of objects that fit into a slab.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">CACHE SIZE</code> — The cache size of the slab.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NAME</code> — The name of the slab.
+ </div></li></ul></div><div class="para">
+ For more information on the <code class="filename">/usr/bin/slabtop</code> program, refer to the <code class="filename">slabtop</code> man page.
+ </div></div><div class="section" id="s2-proc-stat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.25. /proc/stat </h3></div></div></div><a id="idm130633088" class="indexterm"></a><a id="idm130630496" class="indexterm"></a><a id="idm130628752" class="indexterm"></a><div class="para">
+ This file keeps track of a variety of different statistics about the system since it was last restarted. The contents of <code class="filename">/proc/stat</code>, which can be quite long, usually begins like the following example:
+ </div><pre class="screen">
+cpu 259246 7001 60190 34250993 137517 772 0
+cpu0 259246 7001 60190 34250993 137517 772 0
+intr 354133732 347209999 2272 0 4 4 0 0 3 1 1249247 0 0 80143 0 422626 5169433
+ctxt 12547729
+btime 1093631447
+processes 130523
+procs_running 1
+procs_blocked 0
+preempt 5651840
+cpu 209841 1554 21720 118519346 72939 154 27168
+cpu0 42536 798 4841 14790880 14778 124 3117
+cpu1 24184 569 3875 14794524 30209 29 3130
+cpu2 28616 11 2182 14818198 4020 1 3493
+cpu3 35350 6 2942 14811519 3045 0 3659
+cpu4 18209 135 2263 14820076 12465 0 3373
+cpu5 20795 35 1866 14825701 4508 0 3615
+cpu6 21607 0 2201 14827053 2325 0 3334
+cpu7 18544 0 1550 14831395 1589 0 3447
+intr 15239682 14857833 6 0 6 6 0 5 0 1 0 0 0 29 0 2 0 0 0 0 0 0 0 94982 0 286812
+ctxt 4209609
+btime 1078711415
+processes 21905
+procs_running 1
+procs_blocked 0
+</pre><div class="para">
+ Some of the more commonly used statistics include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu</code> — Measures the number of <em class="firstterm">jiffies</em> (1/100 of a second for x86 systems) that the system has been in user mode, user mode with low priority (nice), system mode, idle task, I/O wait, IRQ (hardirq), and softirq respectively. The IRQ (hardirq) is the direct response to a hardware event. The IRQ takes minimal work for queuing the "heavy" work up for the softirq to execute. The softirq runs at a lower priority than the IRQ and therefore may be interrupted more frequently. The total for all CPUs is given at the top, while each individual CPU is listed below with its own statistics. The following example is a 4-way Intel Pentium Xeon configuration with multi-threading enabled, therefore showing four physical processors and four virtual processors totaling eight processors.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">page</code> — The number of memory pages the system has written in and out to disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">swap</code> — The number of swap pages the system has brought in and out.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">intr</code> — The number of interrupts the system has experienced.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">btime</code> — The boot time, measured in the number of seconds since January 1, 1970, otherwise known as the <em class="firstterm">epoch</em>.
+ </div></li></ul></div></div><div class="section" id="s2-proc-swaps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.26. /proc/swaps </h3></div></div></div><a id="idm109765392" class="indexterm"></a><div class="para">
+ This file measures swap space and its utilization. For a system with only one swap partition, the output of <code class="filename">/proc/swaps</code> may look similar to the following:
+ </div><pre class="screen">
+Filename Type Size Used Priority
+/dev/mapper/VolGroup00-LogVol01 partition 524280 0 -1
+</pre><div class="para">
+ While some of this information can be found in other files in the <code class="filename">/proc/</code> directory, <code class="filename">/proc/swap</code> provides a snapshot of every swap file name, the type of swap space, the total size, and the amount of space in use (in kilobytes). The priority column is useful when multiple swap files are in use. The lower the priority, the more likely the swap file is to be used.
+ </div></div><div class="section" id="s2-proc-sysrq-trigger"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.27. /proc/sysrq-trigger </h3></div></div></div><a id="idm131559360" class="indexterm"></a><div class="para">
+ Using the <code class="command">echo</code> command to write to this file, a remote root user can execute most System Request Key commands remotely as if at the local terminal. To <code class="command">echo</code> values to this file, the <code class="filename">/proc/sys/kernel/sysrq</code> must be set to a value other than <code class="computeroutput">0</code>. For more information about the System Request Key, refer to <a class="xref" href="#s3-proc-sys-kernel">「 /proc/sys/kernel/ 」</a>.
+ </div><div class="para">
+ Although it is possible to write to this file, it cannot be read, even by the root user.
+ </div></div><div class="section" id="s2-proc-uptime"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.28. /proc/uptime </h3></div></div></div><a id="idm135125744" class="indexterm"></a><div class="para">
+ This file contains information detailing how long the system has been on since its last restart. The output of <code class="filename">/proc/uptime</code> is quite minimal:
+ </div><pre class="screen">
+350735.47 234388.90
+</pre><div class="para">
+ The first number is the total number of seconds the system has been up. The second number is how much of that time the machine has spent idle, in seconds.
+ </div></div><div class="section" id="s2-proc-version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.29. /proc/version </h3></div></div></div><a id="idm126735840" class="indexterm"></a><div class="para">
+ This file specifies the version of the Linux kernel, the version of <code class="command">gcc</code> used to compile the kernel, and the time of kernel compilation. It also contains the kernel compiler's user name (in parentheses).
+ </div><pre class="screen">
+Linux version 2.6.8-1.523 (user at foo.redhat.com) (gcc version 3.4.1 20040714 \ (Red Hat Enterprise Linux 3.4.1-7)) #1 Mon Aug 16 13:27:03 EDT 2004
+</pre><div class="para">
+ This information is used for a variety of purposes, including the version data presented when a user logs in.
+ </div></div></div><div class="section" id="s1-proc-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.3. Directories within /proc/</h2></div></div></div><a id="idm59348192" class="indexterm"></a><div class="para">
+ Common groups of information concerning the kernel are grouped into directories and subdirectories within the <code class="filename">/proc/</code> directory.
+ </div><div class="section" id="s2-proc-processdirs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.1. Process Directories</h3></div></div></div><a id="idm59343744" class="indexterm"></a><div class="para">
+ Every <code class="filename">/proc/</code> directory contains a number of directories with numerical names. A listing of them may be similar to the following:
+ </div><pre class="screen">
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 1
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 1010
+dr-xr-xr-x 3 xfs xfs 0 Feb 13 01:28 1087
+dr-xr-xr-x 3 daemon daemon 0 Feb 13 01:28 1123
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 11307
+dr-xr-xr-x 3 apache apache 0 Feb 13 01:28 13660
+dr-xr-xr-x 3 rpc rpc 0 Feb 13 01:28 637
+dr-xr-xr-x 3 rpcuser rpcuser 0 Feb 13 01:28 666
+</pre><div class="para">
+ These directories are called <em class="firstterm">process directories</em>, as they are named after a program's process ID and contain information specific to that process. The owner and group of each process directory is set to the user running the process. When the process is terminated, its <code class="filename">/proc/</code> process directory vanishes.
+ </div><div class="para">
+ Each process directory contains the following files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">cmdline</code> — Contains the command issued when starting the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cwd</code> — A symbolic link to the current working directory for the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">environ</code> — A list of the environment variables for the process. The environment variable is given in all upper-case characters, and the value is in lower-case characters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">exe</code> — A symbolic link to the executable of this process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">fd</code> — A directory containing all of the file descriptors for a particular process. These are given in numbered links:
+ </div><pre class="screen">
+total 0
+lrwx------ 1 root root 64 May 8 11:31 0 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 1 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 2 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 3 -> /dev/ptmx
+lrwx------ 1 root root 64 May 8 11:31 4 -> socket:[7774817]
+lrwx------ 1 root root 64 May 8 11:31 5 -> /dev/ptmx
+lrwx------ 1 root root 64 May 8 11:31 6 -> socket:[7774829]
+lrwx------ 1 root root 64 May 8 11:31 7 -> /dev/ptmx
+</pre></li><li class="listitem"><div class="para">
+ <code class="computeroutput">maps</code> — A list of memory maps to the various executables and library files associated with this process. This file can be rather long, depending upon the complexity of the process, but sample output from the <code class="command">sshd</code> process begins like the following:
+ </div><pre class="screen">
+08048000-08086000 r-xp 00000000 03:03 391479 /usr/sbin/sshd
+08086000-08088000 rw-p 0003e000 03:03 391479 /usr/sbin/sshd
+08088000-08095000 rwxp 00000000 00:00 0
+40000000-40013000 r-xp 0000000 03:03 293205 /lib/ld-2.2.5.so
+40013000-40014000 rw-p 00013000 03:03 293205 /lib/ld-2.2.5.so
+40031000-40038000 r-xp 00000000 03:03 293282 /lib/libpam.so.0.75
+40038000-40039000 rw-p 00006000 03:03 293282 /lib/libpam.so.0.75
+40039000-4003a000 rw-p 00000000 00:00 0
+4003a000-4003c000 r-xp 00000000 03:03 293218 /lib/libdl-2.2.5.so
+4003c000-4003d000 rw-p 00001000 03:03 293218 /lib/libdl-2.2.5.so
+</pre></li><li class="listitem"><div class="para">
+ <code class="computeroutput">mem</code> — The memory held by the process. This file cannot be read by the user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">root</code> — A link to the root directory of the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">stat</code> — The status of the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">statm</code> — The status of the memory in use by the process. Below is a sample <code class="filename">/proc/statm</code> file:
+ </div><pre class="screen">
+263 210 210 5 0 205 0
+</pre><div class="para">
+ The seven columns relate to different memory statistics for the process. From left to right, they report the following aspects of the memory used:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Total program size, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ Size of memory portions, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages that are shared.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages that are code.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages of data/stack.
+ </div></li><li class="listitem"><div class="para">
+ Number of library pages.
+ </div></li><li class="listitem"><div class="para">
+ Number of dirty pages.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">status</code> — The status of the process in a more readable form than <code class="filename">stat</code> or <code class="filename">statm</code>. Sample output for <code class="command">sshd</code> looks similar to the following:
+ </div><pre class="screen">
+Name: sshd
+State: S (sleeping)
+Tgid: 797
+Pid: 797
+PPid: 1
+TracerPid: 0
+Uid: 0 0 0 0
+Gid: 0 0 0 0
+FDSize: 32
+Groups:
+VmSize: 3072 kB
+VmLck: 0 kB
+VmRSS: 840 kB
+VmData: 104 kB
+VmStk: 12 kB
+VmExe: 300 kB
+VmLib: 2528 kB
+SigPnd: 0000000000000000
+SigBlk: 0000000000000000
+SigIgn: 8000000000001000
+SigCgt: 0000000000014005
+CapInh: 0000000000000000
+CapPrm: 00000000fffffeff
+CapEff: 00000000fffffeff
+</pre><div class="para">
+ The information in this output includes the process name and ID, the state (such as <code class="computeroutput">S (sleeping)</code> or <code class="computeroutput">R (running)</code>), user/group ID running the process, and detailed data regarding memory usage.
+ </div></li></ul></div><div class="section" id="s3-proc-self"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.1.1. /proc/self/ </h4></div></div></div><a id="idm131911184" class="indexterm"></a><div class="para">
+ The <code class="filename">/proc/self/</code> directory is a link to the currently running process. This allows a process to look at itself without having to know its process ID.
+ </div><div class="para">
+ Within a shell environment, a listing of the <code class="filename">/proc/self/</code> directory produces the same contents as listing the process directory for that process.
+ </div></div></div><div class="section" id="s2-proc-dir-bus"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.2. /proc/bus/ </h3></div></div></div><a id="idm124547520" class="indexterm"></a><div class="para">
+ This directory contains information specific to the various buses available on the system. For example, on a standard system containing PCI and USB buses, current data on each of these buses is available within a subdirectory within <code class="filename">/proc/bus/</code> by the same name, such as <code class="filename">/proc/bus/pci/</code>.
+ </div><div class="para">
+ The subdirectories and files available within <code class="filename">/proc/bus/</code> vary depending on the devices connected to the system. However, each bus type has at least one directory. Within these bus directories are normally at least one subdirectory with a numerical name, such as <code class="filename">001</code>, which contain binary files.
+ </div><div class="para">
+ For example, the <code class="filename">/proc/bus/usb/</code> subdirectory contains files that track the various devices on any USB buses, as well as the drivers required for them. The following is a sample listing of a <code class="filename">/proc/bus/usb/</code> directory:
+ </div><pre class="screen">
+total 0 dr-xr-xr-x 1 root root 0 May 3 16:25 001
+-r--r--r-- 1 root root 0 May 3 16:25 devices
+-r--r--r-- 1 root root 0 May 3 16:25 drivers
+</pre><div class="para">
+ The <code class="filename">/proc/bus/usb/001/</code> directory contains all devices on the first USB bus and the <code class="filename">devices</code> file identifies the USB root hub on the motherboard.
+ </div><div class="para">
+ The following is a example of a <code class="filename">/proc/bus/usb/devices</code> file:
+ </div><pre class="screen">
+T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
+B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
+D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
+P: Vendor=0000 ProdID=0000 Rev= 0.00
+S: Product=USB UHCI Root Hub
+S: SerialNumber=d400
+C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
+I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
+E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
+</pre></div><div class="section" id="s2-proc-pci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.3. /proc/bus/pci </h3></div></div></div><a id="idm81902160" class="indexterm"></a><a id="idm48226416" class="indexterm"></a><div class="para">
+ Later versions of the 2.6 Linux kernel have obsoleted the <code class="filename">/proc/pci</code> directory in favor of the <code class="filename">/proc/bus/pci</code> directory. Although you can get a list of all PCI devices present on the system using the command <code class="command">cat /proc/bus/pci/devices</code>, the output is difficult to read and interpret.
+ </div><div class="para">
+ For a human-readable list of PCI devices, run the following command:
+ </div><pre class="screen">~]# <code class="command">/sbin/lspci -vb</code>
+00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller
+ Subsystem: Hewlett-Packard Company Device 1308
+ Flags: bus master, fast devsel, latency 0
+ Capabilities: [e0] Vendor Specific Information <?>
+ Kernel driver in use: x38_edac
+ Kernel modules: x38_edac
+
+00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge (prog-if 00 [Normal decode])
+ Flags: bus master, fast devsel, latency 0
+ Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
+ I/O behind bridge: 00001000-00001fff
+ Memory behind bridge: f0000000-f2ffffff
+ Capabilities: [88] Subsystem: Hewlett-Packard Company Device 1308
+ Capabilities: [80] Power Management version 3
+ Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
+ Capabilities: [a0] Express Root Port (Slot+), MSI 00
+ Capabilities: [100] Virtual Channel <?>
+ Capabilities: [140] Root Complex Link <?>
+ Kernel driver in use: pcieport
+ Kernel modules: shpchp
+
+00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
+ Subsystem: Hewlett-Packard Company Device 1308
+ Flags: bus master, medium devsel, latency 0, IRQ 5
+ I/O ports at 2100
+ Capabilities: [50] PCI Advanced Features
+ Kernel driver in use: uhci_hcd
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em>
+</pre><div class="para">
+ The output is a sorted list of all IRQ numbers and addresses as seen by the cards on the PCI bus instead of as seen by the kernel. Beyond providing the name and version of the device, this list also gives detailed IRQ information so an administrator can quickly look for conflicts.
+ </div></div><div class="section" id="s2-proc-dir-driver"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.4. /proc/driver/ </h3></div></div></div><a id="idm84807488" class="indexterm"></a><div class="para">
+ This directory contains information for specific drivers in use by the kernel.
+ </div><div class="para">
+ A common file found here is <code class="filename">rtc</code> which provides output from the driver for the system's <em class="firstterm">Real Time Clock (RTC)</em>, the device that keeps the time while the system is switched off. Sample output from <code class="filename">/proc/driver/rtc</code> looks like the following:
+ </div><pre class="screen">
+rtc_time : 16:21:00
+rtc_date : 2004-08-31
+rtc_epoch : 1900
+alarm : 21:16:27
+DST_enable : no
+BCD : yes
+24hr : yes
+square_wave : no
+alarm_IRQ : no
+update_IRQ : no
+periodic_IRQ : no
+periodic_freq : 1024
+batt_status : okay
+</pre><div class="para">
+ For more information about the RTC, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/rtc.txt</code>.
+ </div></div><div class="section" id="s2-proc-dir-fs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.5. /proc/fs </h3></div></div></div><a id="idm71518848" class="indexterm"></a><div class="para">
+ This directory shows which file systems are exported. If running an NFS server, typing <code class="command">cat /proc/fs/nfsd/exports</code> displays the file systems being shared and the permissions granted for those file systems. For more on file system sharing with NFS, refer to the <em class="citetitle">Network File System (NFS)</em> chapter of the <em class="citetitle">Storage Administration Guide</em>.
+ </div></div><div class="section" id="s2-proc-dir-irq"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.6. /proc/irq/ </h3></div></div></div><a id="idm102735104" class="indexterm"></a><div class="para">
+ This directory is used to set IRQ to CPU affinity, which allows the system to connect a particular IRQ to only one CPU. Alternatively, it can exclude a CPU from handling any IRQs.
+ </div><div class="para">
+ Each IRQ has its own directory, allowing for the individual configuration of each IRQ. The <code class="filename">/proc/irq/prof_cpu_mask</code> file is a bitmask that contains the default values for the <code class="filename">smp_affinity</code> file in the IRQ directory. The values in <code class="filename">smp_affinity</code> specify which CPUs handle that particular IRQ.
+ </div><div class="para">
+ For more information about the <code class="filename">/proc/irq/</code> directory, refer to the following installed documentation:
+ </div><pre class="screen">
+/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" id="s2-proc-dir-net"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.7. /proc/net/ </h3></div></div></div><a id="idm114160944" class="indexterm"></a><div class="para">
+ This directory provides a comprehensive look at various networking parameters and statistics. Each directory and virtual file within this directory describes aspects of the system's network configuration. Below is a partial list of the <code class="filename">/proc/net/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">arp</code> — Lists the kernel's ARP table. This file is particularly useful for connecting a hardware address to an IP address on a system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">atm/</code> directory — The files within this directory contain <em class="firstterm">Asynchronous Transfer Mode (ATM)</em> settings and statistics. This directory is primarily used with ATM networking and ADSL cards.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dev</code> — Lists the various network devices configured on the system, complete with transmit and receive statistics. This file displays the number of bytes each interface has sent and received, the number of packets inbound and outbound, the number of errors seen, the number of packets dropped, and more.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dev_mcast</code> — Lists Layer2 multicast groups on which each device is listening.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">igmp</code> — Lists the IP multicast addresses which this system joined.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_conntrack</code> — Lists tracked network connections for machines that are forwarding IP connections.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_tables_names</code> — Lists the types of <code class="command">iptables</code> in use. This file is only present if <code class="command">iptables</code> is active on the system and contains one or more of the following values: <code class="filename">filter</code>, <code class="filename">mangle</code>, or <code class="filename">nat</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_mr_cache</code> — Lists the multicast routing cache.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_mr_vif</code> — Lists multicast virtual interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">netstat</code> — Contains a broad yet detailed collection of networking statistics, including TCP timeouts, SYN cookies sent and received, and much more.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">psched</code> — Lists global packet scheduler parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">raw</code> — Lists raw device statistics.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">route</code> — Lists the kernel's routing table.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rt_cache</code> — Contains the current routing cache.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">snmp</code> — List of Simple Network Management Protocol (SNMP) data for various networking protocols in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sockstat</code> — Provides socket statistics.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp</code> — Contains detailed TCP socket information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tr_rif</code> — Lists the token ring RIF routing table.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">udp</code> — Contains detailed UDP socket information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">unix</code> — Lists UNIX domain sockets currently in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wireless</code> — Lists wireless interface data.
+ </div></li></ul></div></div><div class="section" id="s2-proc-dir-scsi"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.8. /proc/scsi/ </h3></div></div></div><a id="idm100881440" class="indexterm"></a><div class="para">
+ The primary file in this directory is <code class="filename">/proc/scsi/scsi</code>, which contains a list of every recognized SCSI device. From this listing, the type of device, as well as the model name, vendor, SCSI channel and ID data is available.
+ </div><div class="para">
+ For example, if a system contains a SCSI CD-ROM, a tape drive, a hard drive, and a RAID controller, this file looks similar to the following:
+ </div><pre class="screen">
+Attached devices:
+Host: scsi1
+Channel: 00
+Id: 05
+Lun: 00
+Vendor: NEC
+Model: CD-ROM DRIVE:466
+Rev: 1.06
+Type: CD-ROM
+ANSI SCSI revision: 02
+Host: scsi1
+Channel: 00
+Id: 06
+Lun: 00
+Vendor: ARCHIVE
+Model: Python 04106-XXX
+Rev: 7350
+Type: Sequential-Access
+ANSI SCSI revision: 02
+Host: scsi2
+Channel: 00
+Id: 06
+Lun: 00
+Vendor: DELL
+Model: 1x6 U2W SCSI BP
+Rev: 5.35
+Type: Processor
+ANSI SCSI revision: 02
+Host: scsi2
+Channel: 02
+Id: 00
+Lun: 00
+Vendor: MegaRAID
+Model: LD0 RAID5 34556R
+Rev: 1.01
+Type: Direct-Access
+ANSI SCSI revision: 02
+</pre><div class="para">
+ Each SCSI driver used by the system has its own directory within <code class="filename">/proc/scsi/</code>, which contains files specific to each SCSI controller using that driver. From the previous example, <code class="filename">aic7xxx/</code> and <code class="filename">megaraid/</code> directories are present, since two drivers are in use. The files in each of the directories typically contain an I/O address range, IRQ information, and statistics for the SCSI controller using that driver. Each controller can report a different type and amount of information. The Adaptec AIC-7880 Ultra SCSI host adapter's file in this example system produces the following output:
+ </div><pre class="screen">
+Adaptec AIC7xxx driver version: 5.1.20/3.2.4
+Compile Options:
+TCQ Enabled By Default : Disabled
+AIC7XXX_PROC_STATS : Enabled
+AIC7XXX_RESET_DELAY : 5
+Adapter Configuration:
+SCSI Adapter: Adaptec AIC-7880 Ultra SCSI host adapter
+Ultra Narrow Controller PCI MMAPed
+I/O Base: 0xfcffe000
+Adapter SEEPROM Config: SEEPROM found and used.
+Adaptec SCSI BIOS: Enabled
+IRQ: 30
+SCBs: Active 0, Max Active 1, Allocated 15, HW 16, Page 255
+Interrupts: 33726
+BIOS Control Word: 0x18a6
+Adapter Control Word: 0x1c5f
+Extended Translation: Enabled
+Disconnect Enable Flags: 0x00ff
+Ultra Enable Flags: 0x0020
+Tag Queue Enable Flags: 0x0000
+Ordered Queue Tag Flags: 0x0000
+Default Tag Queue Depth: 8
+Tagged Queue By Device array for aic7xxx
+host instance 1: {255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
+Actual queue depth per device for aic7xxx host instance 1: {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
+Statistics:
+
+(scsi1:0:5:0) Device using Narrow/Sync transfers at 20.0 MByte/sec, offset 15
+Transinfo settings: current(12/15/0/0), goal(12/15/0/0), user(12/15/0/0)
+Total transfers 0 (0 reads and 0 writes)
+ < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
+Reads: 0 0 0 0 0 0 0 0
+Writes: 0 0 0 0 0 0 0 0
+
+(scsi1:0:6:0) Device using Narrow/Sync transfers at 10.0 MByte/sec, offset 15
+Transinfo settings: current(25/15/0/0), goal(12/15/0/0), user(12/15/0/0)
+Total transfers 132 (0 reads and 132 writes)
+ < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
+Reads: 0 0 0 0 0 0 0 0
+Writes: 0 0 0 1 131 0 0 0
+</pre><div class="para">
+ This output reveals the transfer speed to the SCSI devices connected to the controller based on channel ID, as well as detailed statistics concerning the amount and sizes of files read or written by that device. For example, this controller is communicating with the CD-ROM at 20 megabytes per second, while the tape drive is only communicating at 10 megabytes per second.
+ </div></div><div class="section" id="s2-proc-dir-sys"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.9. /proc/sys/ </h3></div></div></div><a id="idm129528960" class="indexterm"></a><a id="idm129526256" class="indexterm"></a><a id="idm82915712" class="indexterm"></a><a id="idm82912160" class="indexterm"></a><a id="idm82909936" class="indexterm"></a><a id="idm96225296" class="indexterm"></a><div class="para">
+ The <code class="filename">/proc/sys/</code> directory is different from others in <code class="filename">/proc/</code> because it not only provides information about the system but also allows the system administrator to immediately enable and disable kernel features.
+ </div><div class="warning"><div class="admonition_header"><h2>Be careful when changing the content of /proc/sys/</h2></div><div class="admonition"><div class="para">
+ Use caution when changing settings on a production system using the various files in the <code class="filename">/proc/sys/</code> directory. Changing the wrong setting may render the kernel unstable, requiring a system reboot.
+ </div><div class="para">
+ For this reason, be sure the options are valid for that file before attempting to change any value in <code class="filename">/proc/sys/</code>.
+ </div></div></div><div class="para">
+ A good way to determine if a particular file can be configured, or if it is only designed to provide information, is to list it with the <code class="option">-l</code> option at the shell prompt. If the file is writable, it may be used to configure the kernel. For example, a partial listing of <code class="filename">/proc/sys/fs</code> looks like the following:
+ </div><pre class="screen">
+-r--r--r-- 1 root root 0 May 10 16:14 dentry-state
+-rw-r--r-- 1 root root 0 May 10 16:14 dir-notify-enable
+-rw-r--r-- 1 root root 0 May 10 16:14 file-max
+-r--r--r-- 1 root root 0 May 10 16:14 file-nr
+</pre><div class="para">
+ In this listing, the files <code class="filename">dir-notify-enable</code> and <code class="filename">file-max</code> can be written to and, therefore, can be used to configure the kernel. The other files only provide feedback on current settings.
+ </div><div class="para">
+ Changing a value within a <code class="filename">/proc/sys/</code> file is done by echoing the new value into the file. For example, to enable the System Request Key on a running kernel, type the command:
+ </div><pre class="screen">
+echo 1 > /proc/sys/kernel/sysrq
+</pre><div class="para">
+ This changes the value for <code class="filename">sysrq</code> from <code class="computeroutput">0</code> (off) to <code class="computeroutput">1</code> (on).
+ </div><div class="para">
+ A few <code class="filename">/proc/sys/</code> configuration files contain more than one value. To correctly send new values to them, place a space character between each value passed with the <code class="command">echo</code> command, such as is done in this example:
+ </div><pre class="screen">
+echo 4 2 45 > /proc/sys/kernel/acct
+</pre><div class="note"><div class="admonition_header"><h2>Changes made using the echo command are not persistent</h2></div><div class="admonition"><div class="para">
+ Any configuration changes made using the <code class="command">echo</code> command disappear when the system is restarted. To make configuration changes take effect after the system is rebooted, refer to <a class="xref" href="#s1-proc-sysctl">「Using the sysctl Command」</a>.
+ </div></div></div><div class="para">
+ The <code class="filename">/proc/sys/</code> directory contains several subdirectories controlling different aspects of a running kernel.
+ </div><div class="section" id="s3-proc-sys-dev"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.1. /proc/sys/dev/ </h4></div></div></div><a id="idm68017984" class="indexterm"></a><div class="para">
+ This directory provides parameters for particular devices on the system. Most systems have at least two directories, <code class="filename">cdrom/</code> and <code class="filename">raid/</code>. Customized kernels can have other directories, such as <code class="filename">parport/</code>, which provides the ability to share one parallel port between multiple device drivers.
+ </div><div class="para">
+ The <code class="filename">cdrom/</code> directory contains a file called <code class="filename">info</code>, which reveals a number of important CD-ROM parameters:
+ </div><pre class="screen">
+CD-ROM information, Id: cdrom.c 3.20 2003/12/17
+drive name: hdc
+drive speed: 48
+drive # of slots: 1
+Can close tray: 1
+Can open tray: 1
+Can lock tray: 1
+Can change speed: 1
+Can select disk: 0
+Can read multisession: 1
+Can read MCN: 1
+Reports media changed: 1
+Can play audio: 1
+Can write CD-R: 0
+Can write CD-RW: 0
+Can read DVD: 0
+Can write DVD-R: 0
+Can write DVD-RAM: 0
+Can read MRW: 0
+Can write MRW: 0
+Can write RAM: 0
+</pre><div class="para">
+ This file can be quickly scanned to discover the qualities of an unknown CD-ROM. If multiple CD-ROMs are available on a system, each device is given its own column of information.
+ </div><div class="para">
+ Various files in <code class="filename">/proc/sys/dev/cdrom</code>, such as <code class="filename">autoclose</code> and <code class="filename">checkmedia</code>, can be used to control the system's CD-ROM. Use the <code class="command">echo</code> command to enable or disable these features.
+ </div><div class="para">
+ If RAID support is compiled into the kernel, a <code class="filename">/proc/sys/dev/raid/</code> directory becomes available with at least two files in it: <code class="filename">speed_limit_min</code> and <code class="filename">speed_limit_max</code>. These settings determine the acceleration of RAID devices for I/O intensive tasks, such as resyncing the disks.
+ </div></div><div class="section" id="s3-proc-sys-fs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.2. /proc/sys/fs/ </h4></div></div></div><a id="idm131245408" class="indexterm"></a><div class="para">
+ This directory contains an array of options and information concerning various aspects of the file system, including quota, file handle, inode, and dentry information.
+ </div><div class="para">
+ The <code class="filename">binfmt_misc/</code> directory is used to provide kernel support for miscellaneous binary formats.
+ </div><div class="para">
+ The important files in <code class="filename">/proc/sys/fs/</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">dentry-state</code> — Provides the status of the directory cache. The file looks similar to the following:
+ </div><pre class="screen">
+57411 52939 45 0 0 0
+</pre><div class="para">
+ The first number reveals the total number of directory cache entries, while the second number displays the number of unused entries. The third number tells the number of seconds between when a directory has been freed and when it can be reclaimed, and the fourth measures the pages currently requested by the system. The last two numbers are not used and display only zeros.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">file-max</code> — Lists the maximum number of file handles that the kernel allocates. Raising the value in this file can resolve errors caused by a lack of available file handles.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">file-nr</code> — Lists the number of allocated file handles, used file handles, and the maximum number of file handles.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overflowgid</code> and <code class="filename">overflowuid</code> — Defines the fixed group ID and user ID, respectively, for use with file systems that only support 16-bit group and user IDs.
+ </div></li></ul></div></div><div class="section" id="s3-proc-sys-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.3. /proc/sys/kernel/ </h4></div></div></div><a id="idm20589712" class="indexterm"></a><a id="idp355776" class="indexterm"></a><a id="idp357520" class="indexterm"></a><a id="idp359744" class="indexterm"></a><a id="idm80194608" class="indexterm"></a><div class="para">
+ This directory contains a variety of different configuration files that directly affect the operation of the kernel. Some of the most important files include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">acct</code> — Controls the suspension of process accounting based on the percentage of free space available on the file system containing the log. By default, the file looks like the following:
+ </div><pre class="screen">
+4 2 30
+</pre><div class="para">
+ The first value dictates the percentage of free space required for logging to resume, while the second value sets the threshold percentage of free space when logging is suspended. The third value sets the interval, in seconds, that the kernel polls the file system to see if logging should be suspended or resumed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ctrl-alt-del</code> — Controls whether <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> gracefully restarts the computer using <code class="command">init</code> (<code class="computeroutput">0</code>) or forces an immediate reboot without syncing the dirty buffers to disk (<code class="computeroutput">1</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">domainname</code> — Configures the system domain name, such as <code class="computeroutput">example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">exec-shield</code> — Configures the Exec Shield feature of the kernel. Exec Shield provides protection against certain types of buffer overflow attacks.
+ </div><div class="para">
+ There are two possible values for this virtual file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">0</code> — Disables Exec Shield.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">1</code> — Enables Exec Shield. This is the default value.
+ </div></li></ul></div><div class="important"><div class="admonition_header"><h2>Using Exec Shield</h2></div><div class="admonition"><div class="para">
+ If a system is running security-sensitive applications that were started while Exec Shield was disabled, these applications must be restarted when Exec Shield is enabled in order for Exec Shield to take effect.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname</code> — Configures the system hostname, such as <code class="computeroutput">www.example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hotplug</code> — Configures the utility to be used when a configuration change is detected by the system. This is primarily used with USB and Cardbus PCI. The default value of <code class="computeroutput">/sbin/hotplug</code> should not be changed unless testing a new program to fulfill this role.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">modprobe</code> — Sets the location of the program used to load kernel modules. The default value is <code class="computeroutput">/sbin/modprobe</code> which means <code class="command">kmod</code> calls it to load the module when a kernel thread calls <code class="command">kmod</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmax</code> — Sets the maximum size of any message sent from one process to another and is set to <code class="computeroutput">8192</code> bytes by default. Be careful when raising this value, as queued messages between processes are stored in non-swappable kernel memory. Any increase in <code class="filename">msgmax</code> would increase RAM requirements for the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmnb</code> — Sets the maximum number of bytes in a single message queue. The default is <code class="computeroutput">16384</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmni</code> — Sets the maximum number of message queue identifiers. The default is <code class="computeroutput">4008</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">osrelease</code> — Lists the Linux kernel release number. This file can only be altered by changing the kernel source and recompiling.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ostype</code> — Displays the type of operating system. By default, this file is set to <code class="computeroutput">Linux</code>, and this value can only be changed by changing the kernel source and recompiling.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overflowgid</code> and <code class="filename">overflowuid</code> — Defines the fixed group ID and user ID, respectively, for use with system calls on architectures that only support 16-bit group and user IDs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">panic</code> — Defines the number of seconds the kernel postpones rebooting when the system experiences a kernel panic. By default, the value is set to <code class="computeroutput">0</code>, which disables automatic rebooting after a panic.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">printk</code> — This file controls a variety of settings related to printing or logging error messages. Each error message reported by the kernel has a <em class="firstterm">loglevel</em> associated with it that defines the importance of the message. The loglevel values break down in this order:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">0</code> — Kernel emergency. The system is unusable.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">1</code> — Kernel alert. Action must be taken immediately.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">2</code> — Condition of the kernel is considered critical.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">3</code> — General kernel error condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">4</code> — General kernel warning condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">5</code> — Kernel notice of a normal but significant condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">6</code> — Kernel informational message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">7</code> — Kernel debug-level messages.
+ </div></li></ul></div><div class="para">
+ Four values are found in the <code class="filename">printk</code> file:
+ </div><pre class="screen">
+6 4 1 7
+</pre><div class="para">
+ Each of these values defines a different rule for dealing with error messages. The first value, called the <em class="firstterm">console loglevel</em>, defines the lowest priority of messages printed to the console. (Note that, the lower the priority, the higher the loglevel number.) The second value sets the default loglevel for messages without an explicit loglevel attached to them. The third value sets the lowest possible loglevel configuration for the console loglevel. The last value sets the default value for the console loglevel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">random/</code> directory — Lists a number of values related to generating random numbers for the kernel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sem</code> — Configures <em class="firstterm">semaphore</em> settings within the kernel. A semaphore is a System V IPC object that is used to control utilization of a particular process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmall</code> — Sets the total amount of shared memory that can be used at one time on the system, in bytes. By default, this value is <code class="computeroutput">2097152</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmmax</code> — Sets the largest shared memory segment size allowed by the kernel. By default, this value is <code class="computeroutput">33554432</code>. However, the kernel supports much larger values than this.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmmni</code> — Sets the maximum number of shared memory segments for the whole system. By default, this value is <code class="computeroutput">4096</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sysrq</code> — Activates the System Request Key, if this value is set to anything other than zero (<code class="computeroutput">0</code>), the default.
+ </div><div class="para">
+ The System Request Key allows immediate input to the kernel through simple key combinations. For example, the System Request Key can be used to immediately shut down or restart a system, sync all mounted file systems, or dump important information to the console. To initiate a System Request Key, type <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>SysRq</strong></span>+<span class="keycap"><strong> <em class="replaceable"><code>system request code</code></em> </strong></span> . Replace <em class="replaceable"><code>system request code</code></em> with one of the following system request codes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">r</code> — Disables raw mode for the keyboard and sets it to XLATE (a limited keyboard mode which does not recognize modifiers such as <span class="keycap"><strong>Alt</strong></span>, <span class="keycap"><strong>Ctrl</strong></span>, or <span class="keycap"><strong>Shift</strong></span> for all keys).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">k</code> — Kills all processes active in a virtual console. Also called <em class="firstterm">Secure Access Key</em> (<em class="firstterm">SAK</em>), it is often used to verify that the login prompt is spawned from <code class="command">init</code> and not a trojan copy designed to capture usernames and passwords.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">b</code> — Reboots the kernel without first unmounting file systems or syncing disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">c</code> — Crashes the system without first unmounting file systems or syncing disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">o</code> — Shuts off the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">s</code> — Attempts to sync disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">u</code> — Attempts to unmount and remount all file systems as read-only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">p</code> — Outputs all flags and registers to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">t</code> — Outputs a list of processes to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">m</code> — Outputs memory statistics to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">0</code> through <code class="command">9</code> — Sets the log level for the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">e</code> — Kills all processes except <code class="command">init</code> using SIGTERM.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">i</code> — Kills all processes except <code class="command">init</code> using SIGKILL.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">l</code> — Kills all processes using SIGKILL (including <code class="command">init</code>). <span class="emphasis"><em>The system is unusable after issuing this System Request Key code.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">h</code> — Displays help text.
+ </div></li></ul></div><div class="para">
+ This feature is most beneficial when using a development kernel or when experiencing system freezes.
+ </div><div class="warning"><div class="admonition_header"><h2>Be careful when enabling the System Request Key feature</h2></div><div class="admonition"><div class="para">
+ The System Request Key feature is considered a security risk because an unattended console provides an attacker with access to the system. For this reason, it is turned off by default.
+ </div></div></div><div class="para">
+ Refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysrq.txt</code> for more information about the System Request Key.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tainted</code> — Indicates whether a non-GPL module is loaded.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">0</code> — No non-GPL modules are loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">1</code> — At least one module without a GPL license (including modules with no license) is loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">2</code> — At least one module was force-loaded with the command <code class="command">insmod -f</code>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="filename">threads-max</code> — Sets the maximum number of threads to be used by the kernel, with a default value of <code class="computeroutput">2048</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">version</code> — Displays the date and time the kernel was last compiled. The first field in this file, such as <code class="computeroutput">#3</code>, relates to the number of times a kernel was built from the source base.
+ </div></li></ul></div></div><div class="section" id="s3-proc-sys-net"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.4. /proc/sys/net/ </h4></div></div></div><a id="idm122923024" class="indexterm"></a><a id="idm122919360" class="indexterm"></a><a id="idm122917648" class="indexterm"></a><a id="idm124985216" class="indexterm"></a><div class="para">
+ This directory contains subdirectories concerning various networking topics. Various configurations at the time of kernel compilation make different directories available here, such as <code class="filename">ethernet/</code>, <code class="filename">ipv4/</code>, <code class="filename">ipx/</code>, and <code class="filename">ipv6/</code>. By altering the files within these directories, system administrators are able to adjust the network configuration on a running system.
+ </div><div class="para">
+ Given the wide variety of possible networking options available with Linux, only the most common <code class="filename">/proc/sys/net/</code> directories are discussed.
+ </div><div class="para">
+ The <code class="filename">/proc/sys/net/core/</code> directory contains a variety of settings that control the interaction between the kernel and networking layers. The most important of these files are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">message_burst</code> — Sets the amount of time in tenths of a second required to write a new warning message. This setting is used to mitigate <em class="firstterm">Denial of Service</em> (<em class="firstterm">DoS</em>) attacks. The default setting is <code class="computeroutput">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">message_cost</code> — Sets a cost on every warning message. The higher the value of this file (default of <code class="computeroutput">5</code>), the more likely the warning message is ignored. This setting is used to mitigate DoS attacks.
+ </div><div class="para">
+ The idea of a DoS attack is to bombard the targeted system with requests that generate errors and fill up disk partitions with log files or require all of the system's resources to handle the error logging. The settings in <code class="filename">message_burst</code> and <code class="filename">message_cost</code> are designed to be modified based on the system's acceptable risk versus the need for comprehensive logging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">netdev_max_backlog</code> — Sets the maximum number of packets allowed to queue when a particular interface receives packets faster than the kernel can process them. The default value for this file is <code class="computeroutput">1000</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">optmem_max</code> — Configures the maximum ancillary buffer size allowed per socket.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rmem_default</code> — Sets the receive socket buffer default size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rmem_max</code> — Sets the receive socket buffer maximum size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wmem_default</code> — Sets the send socket buffer default size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wmem_max</code> — Sets the send socket buffer maximum size in bytes.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">/proc/sys/net/ipv4/</code> directory contains additional networking settings. Many of these settings, used in conjunction with one another, are useful in preventing attacks on the system or when using the system to act as a router.
+ </div><div class="warning"><div class="admonition_header"><h2>Be careful when changing these files</h2></div><div class="admonition"><div class="para">
+ An erroneous change to these files may affect remote connectivity to the system.
+ </div></div></div><div class="para">
+ The following is a list of some of the more important files within the <code class="filename">/proc/sys/net/ipv4/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">icmp_echo_ignore_all</code> and <code class="filename">icmp_echo_ignore_broadcasts</code> — Allows the kernel to ignore ICMP ECHO packets from every host or only those originating from broadcast and multicast addresses, respectively. A value of <code class="computeroutput">0</code> allows the kernel to respond, while a value of <code class="computeroutput">1</code> ignores the packets.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_default_ttl</code> — Sets the default <em class="firstterm">Time To Live (TTL)</em>, which limits the number of hops a packet may make before reaching its destination. Increasing this value can diminish system performance.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_forward</code> — Permits interfaces on the system to forward packets to one other. By default, this file is set to <code class="computeroutput">0</code>. Setting this file to <code class="computeroutput">1</code> enables network packet forwarding.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_local_port_range</code> — Specifies the range of ports to be used by TCP or UDP when a local port is needed. The first number is the lowest port to be used and the second number specifies the highest port. Any systems that expect to require more ports than the default 1024 to 4999 should use a range from 32768 to 61000.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_syn_retries</code> — Provides a limit on the number of times the system re-transmits a SYN packet when attempting to make a connection.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_retries1</code> — Sets the number of permitted re-transmissions attempting to answer an incoming connection. Default of <code class="computeroutput">3</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_retries2</code> — Sets the number of permitted re-transmissions of TCP packets. Default of <code class="computeroutput">15</code>.
+ </div></li></ul></div><div class="para">
+ The file called
+ </div><pre class="screen">
+<code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/ip-sysctl.txt</code>
+</pre><div class="para">
+ contains a complete list of files and options available in the <code class="filename">/proc/sys/net/ipv4/</code> directory.
+ </div><div class="para">
+ A number of other directories exist within the <code class="filename">/proc/sys/net/ipv4/</code> directory and each covers a different aspect of the network stack. The <code class="filename">/proc/sys/net/ipv4/conf/</code> directory allows each system interface to be configured in different ways, including the use of default settings for unconfigured devices (in the <code class="filename">/proc/sys/net/ipv4/conf/default/</code> subdirectory) and settings that override all special configurations (in the <code class="filename">/proc/sys/net/ipv4/conf/all/</code> subdirectory).
+ </div><div class="para">
+ The <code class="filename">/proc/sys/net/ipv4/neigh/</code> directory contains settings for communicating with a host directly connected to the system (called a network neighbor) and also contains different settings for systems more than one hop away.
+ </div><div class="para">
+ Routing over IPV4 also has its own directory, <code class="filename">/proc/sys/net/ipv4/route/</code>. Unlike <code class="filename">conf/</code> and <code class="filename">neigh/</code>, the <code class="filename">/proc/sys/net/ipv4/route/</code> directory contains specifications that apply to routing with any interfaces on the system. Many of these settings, such as <code class="filename">max_size</code>, <code class="filename">max_delay</code>, and <code class="filename">min_delay</code>, relate to controlling the size of the routing cache. To clear the routing cache, write any value to the <code class="filename">flush</code> file.
+ </div><div class="para">
+ Additional information about these directories and the possible values for their configuration files can be found in:
+ </div><pre class="screen">
+/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" id="s3-proc-sys-vm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.5. /proc/sys/vm/ </h4></div></div></div><a id="idm100029536" class="indexterm"></a><a id="idm100025984" class="indexterm"></a><a id="idm100024352" class="indexterm"></a><div class="para">
+ This directory facilitates the configuration of the Linux kernel's virtual memory (VM) subsystem. The kernel makes extensive and intelligent use of virtual memory, which is commonly referred to as swap space.
+ </div><div class="para">
+ The following files are commonly found in the <code class="filename">/proc/sys/vm/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">block_dump</code> — Configures block I/O debugging when enabled. All read/write and block dirtying operations done to files are logged accordingly. This can be useful if diagnosing disk spin up and spin downs for laptop battery conservation. All output when <code class="filename">block_dump</code> is enabled can be retrieved via <code class="command">dmesg</code>. The default value is <code class="computeroutput">0</code>.
+ </div><div class="note"><div class="admonition_header"><h2>Stopping the klogd daemon</h2></div><div class="admonition"><div class="para">
+ If <code class="filename">block_dump</code> is enabled at the same time as kernel debugging, it is prudent to stop the <code class="command">klogd</code> daemon, as it generates erroneous disk activity caused by <code class="filename">block_dump</code>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_background_ratio</code> — Starts background writeback of dirty data at this percentage of total memory, via a pdflush daemon. The default value is <code class="command">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_expire_centisecs</code> — Defines when dirty in-memory data is old enough to be eligible for writeout. Data which has been dirty in-memory for longer than this interval is written out next time a pdflush daemon wakes up. The default value is <code class="command">3000</code>, expressed in hundredths of a second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_ratio</code> — Starts active writeback of dirty data at this percentage of total memory for the generator of dirty data, via pdflush. The default value is <code class="command">20</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_writeback_centisecs</code> — Defines the interval between pdflush daemon wakeups, which periodically writes dirty in-memory data out to disk. The default value is <code class="command">500</code>, expressed in hundredths of a second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">laptop_mode</code> — Minimizes the number of times that a hard disk needs to spin up by keeping the disk spun down for as long as possible, therefore conserving battery power on laptops. This increases efficiency by combining all future I/O processes together, reducing the frequency of spin ups. The default value is <code class="computeroutput">0</code>, but is automatically enabled in case a battery on a laptop is used.
+ </div><div class="para">
+ This value is controlled automatically by the acpid daemon once a user is notified battery power is enabled. No user modifications or interactions are necessary if the laptop supports the ACPI (Advanced Configuration and Power Interface) specification.
+ </div><div class="para">
+ For more information, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/laptop-mode.txt</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">max_map_count</code> — Configures the maximum number of memory map areas a process may have. In most cases, the default value of <code class="computeroutput">65536</code> is appropriate.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">min_free_kbytes</code> — Forces the Linux VM (virtual memory manager) to keep a minimum number of kilobytes free. The VM uses this number to compute a <code class="filename">pages_min</code> value for each <code class="filename">lowmem</code> zone in the system. The default value is in respect to the total memory on the machine.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nr_hugepages</code> — Indicates the current number of configured <code class="filename">hugetlb</code> pages in the kernel.
+ </div><div class="para">
+ For more information, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/vm/hugetlbpage.txt</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nr_pdflush_threads</code> — Indicates the number of pdflush daemons that are currently running. This file is read-only, and should not be changed by the user. Under heavy I/O loads, the default value of two is increased by the kernel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overcommit_memory</code> — Configures the conditions under which a large memory request is accepted or denied. The following three modes are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">0</code> — The kernel performs heuristic memory over commit handling by estimating the amount of memory available and failing requests that are blatantly invalid. Unfortunately, since memory is allocated using a heuristic rather than a precise algorithm, this setting can sometimes allow available memory on the system to be overloaded. This is the default setting.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">1</code> — The kernel performs no memory over commit handling. Under this setting, the potential for memory overload is increased, but so is performance for memory intensive tasks (such as those executed by some scientific software).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">2</code> — The kernel fails requests for memory that add up to all of swap plus the percent of physical RAM specified in <code class="filename">/proc/sys/vm/overcommit_ratio</code>. This setting is best for those who desire less risk of memory overcommitment.
+ </div><div class="note"><div class="admonition_header"><h2>Using this setting</h2></div><div class="admonition"><div class="para">
+ This setting is only recommended for systems with swap areas larger than physical memory.
+ </div></div></div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="filename">overcommit_ratio</code> — Specifies the percentage of physical RAM considered when <code class="filename">/proc/sys/vm/overcommit_memory</code> is set to <code class="command">2</code>. The default value is <code class="command">50</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">page-cluster</code> — Sets the number of pages read in a single attempt. The default value of <code class="computeroutput">3</code>, which actually relates to 16 pages, is appropriate for most systems.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">swappiness</code> — Determines how much a machine should swap. The higher the value, the more swapping occurs. The default value, as a percentage, is set to <code class="computeroutput">60</code>.
+ </div></li></ul></div><div class="para">
+ All kernel-based documentation can be found in the following locally installed location:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/</code>, which contains additional information.
+ </div></div></div><div class="section" id="s2-proc-dir-sysvipc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.10. /proc/sysvipc/ </h3></div></div></div><a id="idm18539712" class="indexterm"></a><div class="para">
+ This directory contains information about System V IPC resources. The files in this directory relate to System V IPC calls for messages (<code class="filename">msg</code>), semaphores (<code class="filename">sem</code>), and shared memory (<code class="filename">shm</code>).
+ </div></div><div class="section" id="s2-proc-tty"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.11. /proc/tty/ </h3></div></div></div><a id="idm134268864" class="indexterm"></a><div class="para">
+ This directory contains information about the available and currently used <em class="firstterm">tty devices</em> on the system. Originally called <em class="firstterm">teletype devices</em>, any character-based data terminals are called tty devices.
+ </div><div class="para">
+ In Linux, there are three different kinds of tty devices. <em class="firstterm">Serial devices</em> are used with serial connections, such as over a modem or using a serial cable. <em class="firstterm">Virtual terminals</em> create the common console connection, such as the virtual consoles available when pressing <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong><F-key></strong></span> at the system console. <em class="firstterm">Pseudo terminals</em> create a two-way communication that is used by some higher level applications, such as XFree86. The <code class="filename">drivers</code> file is a list of the current tty devices in use, as in the following example:
+ </div><pre class="screen">
+serial /dev/cua 5 64-127 serial:callout
+serial /dev/ttyS 4 64-127 serial
+pty_slave /dev/pts 136 0-255 pty:slave
+pty_master /dev/ptm 128 0-255 pty:master
+pty_slave /dev/ttyp 3 0-255 pty:slave
+pty_master /dev/pty 2 0-255 pty:master
+/dev/vc/0 /dev/vc/0 4 0 system:vtmaster
+/dev/ptmx /dev/ptmx 5 2 system
+/dev/console /dev/console 5 1 system:console
+/dev/tty /dev/tty 5 0 system:/dev/tty
+unknown /dev/vc/%d 4 1-63 console
+</pre><div class="para">
+ The <code class="filename">/proc/tty/driver/serial</code> file lists the usage statistics and status of each of the serial tty lines.
+ </div><div class="para">
+ In order for tty devices to be used as network devices, the Linux kernel enforces <em class="firstterm">line discipline</em> on the device. This allows the driver to place a specific type of header with every block of data transmitted over the device, making it possible for the remote end of the connection to a block of data as just one in a stream of data blocks. SLIP and PPP are common line disciplines, and each are commonly used to connect systems to one other over a serial link.
+ </div></div><div class="section" id="s2-proc-pid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.12. /proc/<em class="replaceable"><code>PID</code></em>/ </h3></div></div></div><a id="idm116422464" class="indexterm"></a><div class="para">
+ Out of Memory (OOM) refers to a computing state where all available memory, including swap space, has been allocated. When this situation occurs, it will cause the system to panic and stop functioning as expected. There is a switch that controls OOM behavior in <code class="filename">/proc/sys/vm/panic_on_oom</code>. When set to <code class="filename">1</code> the kernel will panic on OOM. A setting of <code class="filename">0</code> instructs the kernel to call a function named <code class="filename">oom_killer</code> on an OOM. Usually, <code class="filename">oom_killer</code> can kill rogue processes and the system will survive.
+ </div><div class="para">
+ The easiest way to change this is to echo the new value to <code class="filename">/proc/sys/vm/panic_on_oom</code>.
+ </div><pre class="screen">
+# cat /proc/sys/vm/panic_on_oom
+1
+
+# echo 0 > /proc/sys/vm/panic_on_oom
+
+# cat /proc/sys/vm/panic_on_oom
+0
+</pre><div class="para">
+ It is also possible to prioritize which processes get killed by adjusting the <code class="filename">oom_killer</code> score. In <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> there are two tools labeled <code class="filename">oom_adj</code> and <code class="filename">oom_score</code>. Valid scores for <code class="filename">oom_adj</code> are in the range -16 to +15. To see the current <code class="filename">oom_killer</code> score, view the <code class="filename">oom_score</code> for the process. <code class="filename">oom_killer</code> will kill processes with the highest scores first.
+ </div><div class="para">
+ This example adjusts the oom_score of a process with a <em class="replaceable"><code>PID</code></em> of 12465 to make it less likely that <code class="filename">oom_killer</code> will kill it.
+ </div><pre class="screen">
+# cat /proc/12465/oom_score
+79872
+
+# echo -5 > /proc/12465/oom_adj
+
+# cat /proc/12465/oom_score
+78
+</pre><div class="para">
+ There is also a special value of -17, which disables <code class="filename">oom_killer</code> for that process. In the example below, <code class="filename">oom_score</code> returns a value of 0, indicating that this process would not be killed.
+ </div><pre class="screen">
+# cat /proc/12465/oom_score
+78
+
+# echo -17 > /proc/12465/oom_adj
+
+# cat /proc/12465/oom_score
+0
+</pre><div class="para">
+ A function called <code class="filename">badness()</code> is used to determine the actual score for each process. This is done by adding up 'points' for each examined process. The process scoring is done in the following way:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The basis of each process's score is its memory size.
+ </div></li><li class="listitem"><div class="para">
+ The memory size of any of the process's children (not including a kernel thread) is also added to the score
+ </div></li><li class="listitem"><div class="para">
+ The process's score is increased for 'niced' processes and decreased for long running processes.
+ </div></li><li class="listitem"><div class="para">
+ Processes with the <code class="filename">CAP_SYS_ADMIN</code> and <code class="filename">CAP_SYS_RAWIO</code> capabilities have their scores reduced.
+ </div></li><li class="listitem"><div class="para">
+ The final score is then bitshifted by the value saved in the <code class="filename">oom_adj</code> file.
+ </div></li></ol></div><div class="para">
+ Thus, a process with the highest <code class="filename">oom_score</code> value will most probably be a non-priviliged, recently started process that, along with its children, uses a large amount of memory, has been 'niced', and handles no raw I/O.
+ </div></div></div><div class="section" id="s1-proc-sysctl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.4. Using the sysctl Command</h2></div></div></div><a id="idm134032272" class="indexterm"></a><a id="idm134030528" class="indexterm"></a><a id="idm134028784" class="indexterm"></a><a id="idm89000496" class="indexterm"></a><a id="idm88996832" class="indexterm"></a><a id="idm88994608" class="indexterm"></a><div class="para">
+ The <code class="command">/sbin/sysctl</code> command is used to view, set, and automate kernel settings in the <code class="filename">/proc/sys/</code> directory.
+ </div><div class="para">
+ For a quick overview of all settings configurable in the <code class="filename">/proc/sys/</code> directory, type the <code class="command">/sbin/sysctl -a</code> command as root. This creates a large, comprehensive list, a small portion of which looks something like the following:
+ </div><pre class="screen">
+net.ipv4.route.min_delay = 2 kernel.sysrq = 0 kernel.sem = 250 32000 32 128
+</pre><div class="para">
+ This is the same information seen if each of the files were viewed individually. The only difference is the file location. For example, the <code class="filename">/proc/sys/net/ipv4/route/min_delay</code> file is listed as <code class="computeroutput">net.ipv4.route.min_delay</code>, with the directory slashes replaced by dots and the <code class="computeroutput">proc.sys</code> portion assumed.
+ </div><div class="para">
+ The <code class="command">sysctl</code> command can be used in place of <code class="command">echo</code> to assign values to writable files in the <code class="filename">/proc/sys/</code> directory. For example, instead of using the command
+ </div><pre class="screen">
+echo 1 > /proc/sys/kernel/sysrq
+</pre><div class="para">
+ use the equivalent <code class="command">sysctl</code> command as follows:
+ </div><pre class="screen">
+sysctl -w kernel.sysrq="1"
+kernel.sysrq = 1
+</pre><div class="para">
+ While quickly setting single values like this in <code class="filename">/proc/sys/</code> is helpful during testing, this method does not work as well on a production system as special settings within <code class="filename">/proc/sys/</code> are lost when the machine is rebooted. To preserve custom settings, add them to the <code class="filename">/etc/sysctl.conf</code> file.
+ </div><div class="para">
+ Each time the system boots, <code class="systemitem">systemd</code> executes <code class="command">sysctl</code> using the <code class="filename">/etc/sysctl.conf</code> configuration file to determine the values passed to the kernel. Any values added to <code class="filename">/etc/sysctl.conf</code> therefore take effect each time the system boots.
+ </div><div class="para">
+ Additionally, <code class="systemitem">systemd</code> determines the contents of several directories including <code class="filename">/etc/sysctl.d/</code> and reads values from any file with the <code class="filename">.conf</code> extension. The <code class="filename">/etc/sysctl.d/</code> directory can be used to organize values into different files, and also permits them to be disabled by changing the extension of the file. For a complete list of directories read by <code class="systemitem">systemd</code>, refer to the <span class="bold bold"><strong>sysctl.d</strong></span>(5) manual page.
+ </div></div><div class="section" id="s1-proc-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.5. 参考文献</h2></div></div></div><a id="idm90050448" class="indexterm"></a><div class="para">
+ Below are additional sources of information about <code class="filename">proc</code> file system.
+ </div><div class="simplesect" id="s2-proc-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h1 class="title">インストールされているドキュメント</h1></div></div></div><a id="idm90046256" class="indexterm"></a><div class="para">
+ Some of the best documentation about the <code class="filename">proc</code> file system is installed on the system by default.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt</code> — Contains assorted, but limited, information about all aspects of the <code class="filename">/proc/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysrq.txt</code> — An overview of System Request Key options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysctl/</code> — A directory containing a variety of <code class="command">sysctl</code> tips, including modifying values that concern the kernel (<code class="filename">kernel.txt</code>), accessing file systems (<code class="filename">fs.txt</code>), and virtual memory use (<code class="filename">vm.txt</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/ip-sysctl.txt</code> — A detailed overview of IP networking options.
+ </div></li></ul></div></div><div class="simplesect" id="s2-proc-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h1 class="title">役に立つ Web サイト</h1></div></div></div><a id="idm126600176" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.linuxhq.com/">http://www.linuxhq.com/</a> — This website maintains a complete database of source, patches, and documentation for various versions of the Linux kernel.
+ </div></li></ul></div></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-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="idm107444896"><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>サーバーオプション, <a class="indexterm" href="#s3-email-mda-fetchmail-configuration-server">サーバー オプション</a></dt><dt>ユーザーオプション, <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 /dev/oprofile/ </a></dt><dt>/dev/shm, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/etc/named.conf (参照 BIND)</dt><dt> /etc/sysconfig/ ディレクトリー (参照 sysconfig ディレクトリー)</dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="#idm122588480">サーバーの起動と停止</a></dt><dt> /proc/ directory (参照 proc file system)</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>イーサネット (参照 ネットワーク)</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="indexterm" 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_K
ernel">カーネルをアップグレードする</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><dt>グループ (参照 グループの設定)</dt><dd><dl><dt>GID, <a class="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" hre
f="#s1-users-tools">コマンドラインのツールを使う</a></dt><dt>system-config-users, <a class="indexterm" href="#s2-users-groups-private-groups">ユーザープライベートグループ</a></dt><dt>User Manager, <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="#s1-users-groups-additional-resources">その他のリソース</a></dt><dd><dl><dt>インストールされているドキュメント, <a class="indexterm" href="#s2-users-groups-documentation">インストールされているドキュメント</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="#s2-redhat-config-users-group-properties">グループのプロパティを変更する</a></dt><dt>グループのプロパティの変更, <a class="indexterm" href="#s2-redhat-config-users-group-properties">グループのプロパティを変更する</a></dt><dt>グループの追加, <a class="indexterm" href="#s2-redhat-config-users-group-new">新規グループを追加する</a></dt><dt>グループ一覧のフィルター, <a class="indexterm" href="#s2-redhat-config-users-list">ユーザーとグループを閲覧する</a></dt><dt>グループ一覧の表示, <a class="indexterm" href="#s1-users-configui">ユーザー管理のツールを使う</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 the 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>セカンダリãƒãƒ¼ãƒ サーãƒãƒ¼ (å‚ç…§ BIND)</dt><dt> ã‚»ã‚ュリティ プラグイン (å‚ç…§ ã‚»ã‚ュリティ)</dt><dt>ã‚»ã‚ュリティ関連ã®ãƒ‘ッケージ</dt><dd><dl><dt>ã‚»ã‚ュリティ関連ã®ãƒ‘ッケージ更新, <a class="indexterm" href="#sec-Updating_Packages">パッケージã®æ
›´æ–°</a></dt></dl></dd><dt>タイムゾーン, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Date_and_Time">日付ã¨æ™‚刻ã®è¨å®šãƒ„ールã®ä½¿ã„æ–¹</a></dt><dd><dl><dt>(å‚ç…§ 日付ã¨æ™‚刻)</dt></dl></dd><dt>ãƒãƒ£ãƒãƒ«ãƒ»ãƒœãƒ³ãƒ‡ã‚£ãƒ³ã‚°</dt><dd><dl><dt>インターフェース</dt><dd><dl><dt>è¨å®š, <a class="indexterm" href="#s2-networkscripts-interfaces-chan">ãƒãƒ£ãƒ³ãƒãƒ«ãƒ»ãƒœãƒ³ãƒ‡ã‚£ãƒ³ã‚°ãƒ»ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹</a></dt></dl></dd></dl></dd><dt>ツール</dt><dd><dl><dt> èªè¨¼ã®è¨å®šãƒ„ール , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool">èªè¨¼ã®è¨å®šãƒ„ール</a></dt></dl></dd><dt>ディレクトリサーãƒãƒ¼ (å‚ç…§ OpenLDAP)</dt><dt>ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯</dt><dd><dl><dt>インターフェース</dt><dd><dl><dt>イーサãƒãƒƒãƒˆ, <a class="indexterm" href="#s2-networkscripts-interfaces-eth0">イーサãƒãƒƒãƒˆ インターフェース</a></dt><dt>エイリアス, <a class="indexterm" href="#s2-net
workscripts-interfaces-alias">エイリアス ファイルとクローン ファイル</a></dt><dt>クローン, <a class="indexterm" href="#s2-networkscripts-interfaces-alias">エイリアス ファイルとクローン ファイル</a></dt><dt>ダイアルアップ, <a class="indexterm" href="#s2-networkscripts-interfaces-ppp0">ダイヤルアップ インターフェース</a></dt><dt>チャネル・ボンディング, <a class="indexterm" href="#s2-networkscripts-interfaces-chan">チャンネル・ボンディング・インターフェース</a></dt></dl></dd><dt>インターフェースの設定ファイル, <a class="indexterm" href="#s1-networkscripts-interfaces">インターフェース設定ファイル</a></dt><dt>コマンド</dt><dd><dl><dt> /sbin/ifdown , <a class="indexterm" href="#s1-networkscripts-control">インターフェース制御スクリプト</a></dt><dt> /sbin/ifup , <a class="indexterm" href="#s1-networkscripts-control">インターフェース制
御スクリプト</a></dt></dl></dd><dt>スクリプト, <a class="indexterm" href="#ch-Network_Interfaces">ネットワーク・インターフェース</a></dt><dt>機能, <a class="indexterm" href="#s1-networkscripts-functions">ネットワーク機能ファイル</a></dt><dt>設定, <a class="indexterm" href="#s1-networkscripts-interfaces">インターフェース設定ファイル</a></dt><dt>設定ファイル, <a class="indexterm" href="#s1-networkscripts-files">ネットワーク設定ファイル</a></dt><dt>追加リソース, <a class="indexterm" href="#s1-networkscripts-resources">その他のリソース</a></dt></dl></dd><dt>ネームサーバー (参照 DNS)</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>パッケージ</dt><dd><dl><dt>PackageKit を用いた Yum リポジトリーの表示, <a class="indexterm" href="#sec-Setting_preferences_for_software_sources">ソフトウェアソースの設定</a></dt><dt>PackageKit を用いたパッケージのアンインストール, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>PackageKit を用いたパッケージのインストール, <a class="indexterm" href="#ch-PackageKit">PackageKit</a>, <a class="indexterm" href="#sec-Installing_and_Removing_Packages_and_Dependencies">パッケージ（および依存するもの）のインストールおよび削除</a></dt><dd><dl><dt>依存性, <a class="indexterm" href="#sec-Installing_and_Removing_Package
s_and_Dependencies">パッケージ（ãŠã‚ˆã³ä¾å˜ã™ã‚‹ã‚‚ã®ï¼‰ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></dt></dl></dd><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®å‰Šé™¤, <a class="indexterm" href="#sec-Installing_and_Removing_Packages_and_Dependencies">パッケージ（ãŠã‚ˆã³ä¾å˜ã™ã‚‹ã‚‚ã®ï¼‰ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®æ›´æ–°, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dd><dl><dt>PolicyKit, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">ソフトウェアã®æ›´æ–°ã‚’用ã„ãŸãƒ‘ッケージã®æ›´æ–°</a></dt><dt>ソフトウェアã®æ›´æ–°, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">ソフトウェアã®æ›´æ–°ã‚’用ã„ãŸãƒ‘ッケージã®æ›
´æ–°</a></dt></dl></dd><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®ç®¡ç†, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®è¡¨ç¤º, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®è¨å®š</dt><dd><dl><dt>確èªã®é–“éš”, <a class="indexterm" href="#sec-Setting_preferences_for_checking_for_updates">æ›´æ–°ã®ç¢ºèªé–“éš”ã®è¨å®š</a></dt></dl></dd><dt>PackageKit を用ã„ãŸãƒ•ã‚£ãƒ«ã‚¿ãƒ¼, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dd><dl><dt>Free, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>インストール済, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>インストール済ã®ç‰©ã®ã¿, <a class="indexterm" href="
#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>エンドユーザーのファイルのみ, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>グラフィカルのみ, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>サブパッケージを隠す, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>ディストリ固有のパッケージのみ, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>フィルターをかけない, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>利用可能なもののみ, <a class="indexterm" href="#sec-Finding_Pack
ages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>最新パッケージのみ, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>開発, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt><dt>開発版のみ, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">フィルターを用いたパッケージの検索</a></dt></dl></dd><dt>PackageKit を用いた追加と削除, <a class="indexterm" href="#sec-Using_Add_Remove_Software">ソフトウェアの追加/削除の使用</a></dt><dt>RPM</dt><dd><dl><dt>アンインストール, <a class="indexterm" href="#s2-rpm-uninstalling">アンインストール</a></dt><dt>インストール済みのアップグレードの実行, <a class="indexterm" href="#s2-rpm-freshening">インストール済みのアップグレードの実行</a></dt><d
t>ティップス, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>削除, <a class="indexterm" href="#s2-rpm-uninstalling">アンインストール</a></dt><dt>検証, <a class="indexterm" href="#s2-rpm-verifying">検証</a></dt><dt>設定ファイルの変更, <a class="indexterm" href="#sec-Configuration_File_Changes">設定ファイルの変更</a></dt></dl></dd><dt>RPM のアップグレード, <a class="indexterm" href="#sec-Installing_and_Upgrading">インストールとアップグレード</a></dt><dt>RPM のインストール, <a class="indexterm" href="#sec-Installing_and_Upgrading">インストールとアップグレード</a></dt><dt>RPM パッケージの検索, <a class="indexterm" href="#s2-rpm-finding">RPM パッケージの検索</a></dt><dt>Yum を用いたインストール, <a class="indexterm" href="#sec-Installing">パッケージのインストール</a></dt><dt>Yum を用いたパッケージ グ
ループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="#sec-Installing">パッケージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«</a></dt><dt>Yum を用ã„ãŸãƒ‘ッケージ グループã®å‰Šé™¤, <a class="indexterm" href="#sec-Removing">パッケージã®å‰Šé™¤</a></dt><dt>Yum を用ã„ãŸãƒ‘ッケージã®ã‚¢ãƒ³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="#sec-Removing">パッケージã®å‰Šé™¤</a></dt><dt>Yum を用ã„ãŸãƒ‘ッケージã®ä¸€è¦§è¡¨ç¤º</dt><dd><dl><dt>yum grouplist, <a class="indexterm" href="#sec-Listing_Packages">パッケージã®ä¸€è¦§</a></dt><dt>yum list all, <a class="indexterm" href="#sec-Listing_Packages">パッケージã®ä¸€è¦§</a></dt><dt>yum list installed, <a class="indexterm" href="#sec-Listing_Packages">パッケージã®ä¸€è¦§</a></dt><dt>yum repolist, <a class="indexterm" href="#sec-Listing_Packages">パッケージã®ä¸€è¦§</a></dt><dt>yum search, <a class="indexterm" href="#sec-Listing_Packages">パッケージã®ä¸€è¦§</a></dt></dl></dd><dt>Yum ã‚’ç
”¨ã„ãŸãƒ‘ッケージã®æ¤œç´¢</dt><dd><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Packages">パッケージã®æ¤œç´¢</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージã®è¡¨ç¤º</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Displaying_Package_Information">ãƒ‘ãƒƒã‚±ãƒ¼ã‚¸æƒ…å ±ã®è¡¨ç¤º</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージ一覧</dt><dd><dl><dt> Glob 表記, <a class="indexterm" href="#sec-Listing_Packages">パッケージã®ä¸€è¦§</a></dt></dl></dd><dt>カーãƒãƒ« RPM, <a class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">カーãƒãƒ«ã‚’アップグレードã™ã‚‹</a></dt><dt>トランザクションãƒã‚°ã®è¡¨ç¤º, <a class="indexterm" href="#sec-Viewing_the_Transaction_Log">トランザクションãƒã‚°ã®è¡¨ç¤º</a></dt><dt>パッケージã¨ãƒ‘ッケージ グループ, <a class="indexterm" href="#sec-Packages_and_Package_Groups">パッケージã¨ãƒ‘ッケージ グループ</a></dt><dt>パッケージグルãƒ
¼ãƒ—ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤, <a class="indexterm" href="#sec-Installing_and_Removing_Package_Groups">パッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></dt><dt>ä¾å˜æ€§, <a class="indexterm" href="#s3-rpm-unresolved-dependency">未解決ã®ä¾å˜æ€§</a></dt><dt>削除, <a class="indexterm" href="#s2-rpm-uninstalling">アンインストール</a></dt><dt>ç¾åœ¨ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るパッケージã®æ›´æ–°</dt><dd><dl><dt>利用å¯èƒ½ãªæ›´æ–°, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">ソフトウェアã®æ›´æ–°ã‚’用ã„ãŸãƒ‘ッケージã®æ›´æ–°</a></dt></dl></dd></dl></dd><dt>パッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«</dt><dd><dl><dt>PackageKit を用ã„ãŸãƒ‘ッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="#sec-Installing_and_Removing_Package_Groups">パッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></dt></dl></dd><dt>パッケージグループã®å‰Šé™
¤</dt><dd><dl><dt>PackageKit を用ã„ãŸãƒ‘ッケージグループã®å‰Šé™¤, <a class="indexterm" href="#sec-Installing_and_Removing_Package_Groups">パッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</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="#sect-Preface-Feedback">フィードãƒãƒƒã‚¯</a></dt></dl></dd><dt>プライマリãƒãƒ¼ãƒ サーãƒãƒ¼ (å‚ç…§ BIND)</dt><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>User Manager, <a class="indexterm" href="#s1-users-tools">コマンドラインã®ãƒ„ールを使ã†</a></dt><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="#s1-users-groups-additional-resources">ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></dt><dd><dl><dt>インストールã•ã‚Œã¦ã„るドã‚ュメント, <a class="indexterm" href="#s2-users-groups-documentation">インストールã•ã‚Œã¦ã„るドã‚ュメント<
/a></dt></dl></dd></dl></dd><dt>ユーザー アカウント (参照 ユーザーの設定)</dt><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="#s2-redhat-config-users-user-properties">ユーザーのプロパティを変更する</a></dt><dt>フルネームの変更, <a class="indexterm" href="#s2-redhat-config-users-user-properties">ユーザーのプロパティを変更する</a></dt><dt>ホームディレクトリの変更, <a class="indexterm" href="#s2-redhat-config-users-user-properties">ユーザーのプロパティを変更する</a></dt><dt>ユーザーのグループの変更, <a class="indexterm" href="#s2-redhat-config-users-user-properties">ユーザーのプロパティを変更する</a></dt><dt>ユーザーの修正, <a class="indexterm" href="#s2-redhat-config-users-user-properties">ユーザーのプロパティを変更する</a></dt><dt>ユーザーの削除, <a class="indexterm" href="#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">ユーザーの削除</a></dt><dt>ユーザーの追加, <a class="indexterm" href="#sect-Managing_Users_and_Groups-User_Accounts-A
dding_a_New_User">新規ユーザーを追加する</a>, <a class="indexterm" href="#s2-redhat-config-users-user-new">新規ユーザーを追加する</a></dt><dt>ユーザー一覧のフィルター, <a class="indexterm" href="#s2-redhat-config-users-list">ユーザーとグループを閲覧する</a></dt><dt>ユーザー一覧の表示, <a class="indexterm" href="#sect-Managing_Users_and_Groups-User_Accounts">ユーザー アカウントのツールを使う</a>, <a class="indexterm" href="#s1-users-configui">ユーザー管理のツールを使う</a></dt><dt>ログインシェルの変更, <a class="indexterm" href="#s2-redhat-config-users-user-properties">ユーザーのプロパティを変更する</a></dt></dl></dd><dt>リソースレコード (参照 BIND)</dt><dt>ルートネームサーバー (参照 BIND)</dt><dt>ログファイル</dt><dd><dl><dt> rsyslogd デーモン , <a class="indexterm" href="#ch-Viewing_and_Managing_Log_Files">ログファイルの表示
ãŠã‚ˆã³ç®¡ç†</a></dt><dt>ãƒãƒ¼ãƒ†ãƒ¼ã‚·ãƒ§ãƒ³, <a class="indexterm" href="#s1-logfiles-locating">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’探ã™</a></dt><dt>監視, <a class="indexterm" href="#s1-logfiles-examining">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’監視ã™ã‚‹</a></dt><dt>表示, <a class="indexterm" href="#s1-logfiles-viewing">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º</a></dt><dt>説明, <a class="indexterm" href="#ch-Viewing_and_Managing_Log_Files">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤ºãŠã‚ˆã³ç®¡ç†</a></dt><dt>è¿½åŠ ãƒªã‚½ãƒ¼ã‚¹</dt><dd><dl><dt>インストールã•ã‚Œã¦ã„るドã‚ュメント, <a class="indexterm" href="#s2-log-files-installed-docs">インストールã•ã‚Œã¦ã„るドã‚ュメント</a></dt><dt>有用ãªã‚¦ã‚§ãƒ–サイト, <a class="indexterm" href="#s2-log-files-useful-websites">å½¹ã«ç«‹ã¤ Web サイト</a></dt></dl></dd></dl></dd><dt> ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ãƒ“ューアー </dt><dd><dl><dt>フィルター, <a class="indexterm" href="#s1-logfiles-viewing">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º</a></dt><dt>æ›´æ–°é
–“éš”, <a class="indexterm" href="#s1-logfiles-viewing">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º</a></dt><dt>検索, <a class="indexterm" href="#s1-logfiles-viewing">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º</a></dt><dt>監視, <a class="indexterm" href="#s1-logfiles-examining">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’監視ã™ã‚‹</a></dt></dl></dd><dt>å†å¸°ãƒãƒ¼ãƒ サーãƒãƒ¼ (å‚ç…§ BIND)</dt><dt>地域ã¨è¨€èªž</dt><dd><dl><dt>ã‚ーボードã®è¨å®š, <a class="indexterm" href="#sect-Configuring_the_Language_and_Keyboard-Layouts">ã‚ーボードã®ãƒ¬ã‚¤ã‚¢ã‚¦ãƒˆå¤‰æ›´</a></dt><dt>システム全体ã®è¨å®š, <a class="indexterm" href="#sect-Configuring_the_Language_and_Keyboard-System">ç¾åœ¨ã®è¨å®šã®è¡¨ç¤º</a></dt><dt>日付ã€æ™‚刻ãŠã‚ˆã³æ•°å—ã®ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã®è¨å®š, <a class="indexterm" href="#sect-Configuring_the_Language_and_Keyboard-Formats">日付ã€æ™‚刻ãŠã‚ˆã³æ•°å—ã®å½¢å¼ã®å¤‰æ›´</a></dt><dt>言語ã®è¨å®š, <a class="indexterm" href="#sect-Configuring_the_Language_and_Keyboard-Langu
age">言語の変更</a></dt></dl></dd><dt>完全修飾ドメイン名, <a class="indexterm" href="#s2-dns-introduction-zones">ネームサーバーゾーン</a></dt><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="#sect-Configuring_the_Date_and_Time-Date_and_Time">日付と時刻の設定ツールの使い方</a>, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">日付の変更方法</a></dt><dd><dl><dt>(参照 日付と時刻)</dt></dl></dd><dt>日付と時刻</dt><dd><dl><dt>システム日付, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Date_and_Time">日付と時刻の設定ツールの使い方</a></dt><dt>
システム時刻, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Date_and_Time">日付と時刻の設定ツールの使い方</a></dt><dt>タイムゾーンの設定, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Date_and_Time">日付と時刻の設定ツールの使い方</a></dt></dl></dd><dt>時刻, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Date_and_Time">日付と時刻の設定ツールの使い方</a>, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">日付の変更方法</a></dt><dd><dl><dt>(参照 日付と時刻)</dt></dl></dd><dt>権威ネームサーバー (参照 BIND)</dt><dt>現在インストールされているパッケージの更新</dt><dd><dl><dt>利用可能な更新, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">ソフトウェアの更新を用いたパッケージの更新</a></dt></dl></dd><dt>自動化タスク, <a class=
"indexterm" href="#ch-Automating_System_Tasks">システムタスクã®è‡ªå‹•åŒ–</a></dt><dt>言語ã®è¨å®š (å‚ç…§ 地域ã¨è¨€èªž)</dt><dt>è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®å¤‰æ›´, <a class="indexterm" href="#sec-Preserving_Configuration_File_Changes">è¨å®šãƒ•ã‚¡ã‚¤ãƒ«å¤‰æ›´ã®ä¿å˜</a></dt><dt>èªè¨¼</dt><dd><dl><dt> スマートカードèªè¨¼ã®ä½¿ç”¨ , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">高度ãªã‚ªãƒ—ション</a></dt><dt> 指紋サãƒãƒ¼ãƒˆã®ä½¿ç”¨ , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">高度ãªã‚ªãƒ—ション</a></dt><dt> èªè¨¼ã®è¨å®šãƒ„ール , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool">èªè¨¼ã®è¨å®šãƒ„ール</a></dt></dl></dd><dt> èªè¨¼ã®è¨å®šãƒ„ール </dt><dd><dl><dt> ãŠã‚ˆã³ Kerberos èªè¨¼ , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">è˜åˆ¥ã¨èªè¨¼</a></dt><dt> ãŠã‚ˆã
³ LDAP , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">è˜åˆ¥ã¨èªè¨¼</a></dt><dt> ãŠã‚ˆã³ NIS , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">è˜åˆ¥ã¨èªè¨¼</a></dt><dt> ãŠã‚ˆã³ NIS èªè¨¼ , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">è˜åˆ¥ã¨èªè¨¼</a></dt><dt> ãŠã‚ˆã³ Winbind , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">è˜åˆ¥ã¨èªè¨¼</a></dt><dt> ãŠã‚ˆã³ Winbind èªè¨¼ , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">è˜åˆ¥ã¨èªè¨¼</a></dt></dl></dd><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><dd><dl><dt>IMAP, <a class="indexterm" href="#s3-email-protocols-imap">IMAP</a></dt><dt>POP, <a class="indexte
rm" 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>歴史, <a class="indexterm" href="#ch-Mail_Servers">メールサーバー</a></dt><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="indext
erm" 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>Access Control</dt><dd><dl><dt>configuring in SSSD, <a class="indexterm" href="#idm115611856">Configuring Access Control</a></dt><dt>in SSSD, rules, <a class="indexterm" href="#idm121783856">The Simple Access Provider</a></dt></dl></dd><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>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>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 class="indexterm" href="#s3-apache-httpdconf-directives">一般的な httpd.conf ディレクティブ</a></dt><dt>AddLanguage, <a class="indexterm" href="#s3-apache-httpdconf-directi
ves">一般的な 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.conf ディレクティブ</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-direct
ives">一般的な 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">一般的な httpd.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-directives">一般的な 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">一般的な httpd.conf ディレクティブ</a></dt><dt>Order, <a class="indexterm" href="#s3-apache-httpdconf-directives">一般的な httpd.conf ディレクティブ</a></dt><dt>PidFile, <a clas
s="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">一般的な htt
pd.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-apac
he-httpdconf-directives">一般的な httpd.conf ディレクティブ</a></dt></dl></dd><dt>バージョン 2.2</dt><dd><dl><dt>バージョン 2.0 からのアップグレード, <a class="indexterm" href="#s2-apache-version2-migrating">設定の更新</a></dt><dt>変更点, <a class="indexterm" href="#s2-apache-version2-changes">注目すべき変更</a></dt><dt>特徴, <a class="indexterm" href="#s2-apache-version2-features">新機能</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>/e
tc/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>de
veloping, <a class="indexterm" href="#s3-apache-dso-writing">モジュールの書き込み方法</a></dt><dt>loading, <a class="indexterm" href="#s3-apache-dso-loading">モジュールの読み込み方法</a></dt><dt>mod_asis, <a class="indexterm" href="#s2-apache-version2-changes">注目すべき変更</a></dt><dt>mod_cache, <a class="indexterm" href="#s2-apache-version2-features">新機能</a></dt><dt>mod_cern_meta, <a class="indexterm" href="#s2-apache-version2-changes">注目すべき変更</a></dt><dt>mod_disk_cache, <a class="indexterm" href="#s2-apache-version2-features">新機能</a></dt><dt>mod_ext_filter, <a class="indexterm" href="#s2-apache-version2-changes">注目すべき変更</a></dt><dt>mod_proxy_balancer, <a class="indexterm" href="#s2-apache-version2-features">新機能</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-apac
he-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">サービスの状態確認</a></dt><dt>設定の確認, <a class="indexterm" href="#s2-apache-editing">設定ファイルの編集</a></dt><dt>追加のリソース</dt><dd><dl><dt>有用なウェブサイト, <a class="indexterm" href="#s3-apache-resources-web">役に立つ Web サイト</a></dt></dl></dd><dt>追加リソース</dt><dd><dl><dt>インストールされているドキュメント, <a class="indexterm" href="#s3-apache-resources-installed">インストールされているドキュメント</a></dt></dl></dd><dt>開始, <a c
lass="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><dt> authconfig (参照 認証の設定ツール )</dt><dd><dl><dt> コマンド , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">コマンドライン版</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>Berkeley Internet Name Domain (参照 BIND)</dt><dt>BIND</dt><dd><dl><dt>zones</dt><dd><dl><dt>$INCLUDE ディレクティブ, <
a class="indexterm" href="#s3-bind-zone-directives">一般的なディレクティブ</a></dt><dt>$ORIGIN ディレクティブ, <a class="indexterm" href="#s3-bind-zone-directives">一般的なディレクティブ</a></dt><dt>$TTL ディレクティブ, <a class="indexterm" href="#s3-bind-zone-directives">一般的なディレクティブ</a></dt><dt>A (Address) リソースレコード, <a class="indexterm" href="#s4-bind-zone-rr">Common Resource Records</a></dt><dt>CNAME (Canonical Name) リソースレコード, <a class="indexterm" href="#s4-bind-zone-rr">Common Resource Records</a></dt><dt>MX (Mail Exchange) リソースレコード, <a class="indexterm" href="#s4-bind-zone-rr">Common Resource Records</a></dt><dt>NS (Nameserver) リソースレコード, <a class="indexterm" href="#s4-bind-zone-rr">Common Resource Records</a></dt><dt>PTR (Pointer) リソースレコード, <a class="indexterm" href="#s4-bind-zone-rr">Common Resource Records</a></dt><dt>SOA (Start of A
uthority) リソースレコード, <a class="indexterm" href="#s4-bind-zone-rr">Common Resource Records</a></dt><dt>コメントタグ, <a class="indexterm" href="#s3-bind-zone-comm">コメントタグ</a></dt><dt>使用例, <a class="indexterm" href="#s4-bind-zone-examples-basic">簡単なゾーンファイル</a>, <a class="indexterm" href="#s3-bind-configuration-zone-reverse">逆引き名前解決ゾーンファイル</a></dt></dl></dd><dt>ゾーン</dt><dd><dl><dt>説明, <a class="indexterm" href="#s2-dns-introduction-zones">ネームサーバーゾーン</a></dt></dl></dd><dt>ディレクトリ</dt><dd><dl><dt>/etc/named/, <a class="indexterm" href="#s2-bind-namedconf">named サービスの設定</a></dt><dt>/var/named/, <a class="indexterm" href="#s2-bind-zone">ゾーンファイルの編集</a></dt><dt>/var/named/data/, <a class="indexterm" href="#s2-bind-zone">ゾーンファイルの編集</a></dt><dt>/var/named/dynamic/, <a class="indexterm" href="#s2-bind-zone">
ゾーンファイルの編集</a></dt><dt>/var/named/slaves/, <a class="indexterm" href="#s2-bind-zone">ゾーンファイルの編集</a></dt></dl></dd><dt>ファイル</dt><dd><dl><dt>/etc/named.conf, <a class="indexterm" href="#s2-bind-namedconf">named サービスの設定</a>, <a class="indexterm" href="#s3-bind-rndc-configuration">ユーティリティの設定法</a></dt><dt>/etc/rndc.conf, <a class="indexterm" href="#s3-bind-rndc-configuration">ユーティリティの設定法</a></dt><dt>/etc/rndc.key, <a class="indexterm" href="#s3-bind-rndc-configuration">ユーティリティの設定法</a></dt></dl></dd><dt>ユーティリティ</dt><dd><dl><dt>dig, <a class="indexterm" href="#s2-dns-introduction-bind">ネームサーバーとしての BIND</a>, <a class="indexterm" href="#s2-bind-dig">dig ユーティリティの使用</a>, <a class="indexterm" href="#s3-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>named, <a class="indexterm" href="#s2-
dns-introduction-bind">ネームサーバーとしての BIND</a>, <a class="indexterm" href="#s2-bind-namedconf">named サービスの設定</a></dt><dt>rndc, <a class="indexterm" href="#s2-dns-introduction-bind">ネームサーバーとしての BIND</a>, <a class="indexterm" href="#s2-bind-rndc">rndc ユーティリティの使用法</a></dt></dl></dd><dt>リソースレコード, <a class="indexterm" href="#s2-dns-introduction-zones">ネームサーバーゾーン</a></dt><dt>一般的な誤り, <a class="indexterm" href="#s2-bind-mistakes">よくある間違いを避けるために</a></dt><dt>機能</dt><dd><dl><dt>Automatic Zone Transfer (AXFR), <a class="indexterm" href="#s3-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>DNS Security Extensions (DNSSEC), <a class="indexterm" href="#s3-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>Incremental Zone Transfer (IXFR), <a class="indexterm" href="#s3-bind-features-ixfr">Incremental Zo
ne Transfers (IXFR)</a></dt><dt>Internet Protocol version 6 (IPv6), <a class="indexterm" href="#s3-bind-features-ipv6">インターãƒãƒƒãƒˆãƒ—ãƒãƒˆã‚³ãƒ«ãƒ»ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 6 (IPv6: Internet Protocol version 6)</a></dt><dt>multiple views, <a class="indexterm" href="#s3-bind-features-views">複数ビュー</a></dt><dt>Transaction SIGnature (TSIG), <a class="indexterm" href="#s3-bind-features-tsig">Transaction SIGnatures (TSIG)</a></dt></dl></dd><dt>種別</dt><dd><dl><dt>セカンダリ（スレーブ）ãƒãƒ¼ãƒ サーãƒãƒ¼, <a class="indexterm" href="#s2-dns-introduction-zones">ãƒãƒ¼ãƒ サーãƒãƒ¼ã‚¾ãƒ¼ãƒ³</a>, <a class="indexterm" href="#s2-dns-introduction-nameservers">ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚¤ãƒ—</a></dt><dt>プライマリ（マスター）ãƒãƒ¼ãƒ サーãƒãƒ¼, <a class="indexterm" href="#s2-dns-introduction-zones">ãƒãƒ¼ãƒ サーãƒãƒ¼ã‚¾ãƒ¼ãƒ³</a>, <a class="indexterm" href="#s2-dns-introduction-nameservers">ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚¤ãƒ—</a></dt><dt>å†å¸
°ãƒãƒ¼ãƒ サーãƒãƒ¼, <a class="indexterm" href="#s2-dns-introduction-nameservers">ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚¤ãƒ—</a></dt><dt>権å¨ãƒãƒ¼ãƒ サーãƒãƒ¼, <a class="indexterm" href="#s2-dns-introduction-nameservers">ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚¤ãƒ—</a></dt></dl></dd><dt>è¨å®š</dt><dd><dl><dt>acl ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state">一般的ãªã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®ã‚¿ã‚¤ãƒ—</a></dt><dt>controls ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>include ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state">一般的ãªã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®ã‚¿ã‚¤ãƒ—</a></dt><dt>key ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>logging ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>opti
ons ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state">一般的ãªã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®ã‚¿ã‚¤ãƒ—</a></dt><dt>server ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>trusted-keys ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>view ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>zone ステートメント, <a class="indexterm" href="#s3-bind-namedconf-state">一般的ãªã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®ã‚¿ã‚¤ãƒ—</a></dt><dt>コメントタグ, <a class="indexterm" href="#s3-bind-namedconf-comm">コメントタグ</a></dt></dl></dd><dt>è¿½åŠ ã®ãƒªã‚½ãƒ¼ã‚¹</dt><dd><dl><dt>インストールã•ã‚Œã¦ã„るドã‚ュメント, <a class="indexterm" href="#s3-bind-installed-docs">インストールã•ã‚Œã¦ã„るドã‚ュメãƒ
³ãƒˆ</a></dt><dt>有用ãªã‚¦ã‚§ãƒ–サイト, <a class="indexterm" href="#s3-bind-useful-websites">å½¹ã«ç«‹ã¤ Web サイト</a></dt><dt>関連書ç±, <a class="indexterm" href="#s3-bind-related-books">関連書ç±</a></dt></dl></dd></dl></dd><dt>blkid, <a class="indexterm" href="#s2-sysinfo-filesystems-blkid">Using the blkid Command</a></dt><dt>block devices, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt><dd><dl><dt>(å‚ç…§ /proc/devices )</dt><dt>definition of, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt></dl></dd><dt>bonding (å‚ç…§ channel bonding)</dt><dt>boot loader</dt><dd><dl><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>全体オプション, <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>channel bonding</dt><dd><dl><dt>configuration, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>description, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>channel bonding interface (参照 kernel module)</dt><dt>character devices, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt><dd><dl><dt>(参照 /proc/devices )</dt><dt>definition of, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt></dl></dd><dt>CPU usage, <a
class="indexterm" href="#s1-sysinfo-cpu">Viewing CPU Usage</a></dt><dt>crash</dt><dd><dl><dt>analyzing the dump</dt><dd><dl><dt>message buffer, <a class="indexterm" href="#s2-kdump-crash-log">Displaying the Message Buffer</a></dt><dt>open files, <a class="indexterm" href="#s2-kdump-crash-files">Displaying Open Files</a></dt><dt>processes, <a class="indexterm" href="#s2-kdump-crash-processes">Displaying a Process Status</a></dt><dt>stack trace, <a class="indexterm" href="#s2-kdump-crash-backtrace">Displaying a Backtrace</a></dt><dt>virtual memory, <a class="indexterm" href="#s2-kdump-crash-memory">Displaying Virtual Memory Information</a></dt></dl></dd><dt>opening the dump image, <a class="indexterm" href="#s2-kdump-crash-running">Running the crash Utility</a></dt><dt>system requirements, <a class="indexterm" href="#s1-kdump-crash">Analyzing the Core Dump</a></dt></dl></dd><dt>Cron, <a class="indexterm" href="#ch-Automating_System_Tasks">システムタスクの自動化</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>deleting cache files</dt><dd><dl><dt>in SSSD, <a class="indexterm" href="#sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">Support for Multiple Domains</a></dt></dl></dd><dt>Denial of Service attack, <a class="indexterm" href="#s3-proc-sys-net"> /proc/sys/net/ </a></dt><dd><dl><dt>(参照 /proc/sys/net/ directory
)</dt><dt>definition of, <a class="indexterm" href="#s3-proc-sys-net"> /proc/sys/net/ </a></dt></dl></dd><dt>desktop environments (参照 X)</dt><dt>df, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>DHCP, <a class="indexterm" href="#ch-DHCP_Servers">DHCP サーバー</a></dt><dd><dl><dt>dhcpd.conf, <a class="indexterm" href="#config-file">設定ファイル</a></dt><dt> dhcpd.leases , <a class="indexterm" href="#idm122588480">サーバーの起動と停止</a></dt><dt>dhcpd6.conf, <a class="indexterm" href="#s1-dhcp_for_ipv6_dhcpv6">IPv6 向け DHCP (DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm" href="#s1-dhcp_for_ipv6_dhcpv6">IPv6 向け DHCP (DHCPv6)</a></dt><dt> dhcrelay , <a class="indexterm" href="#dhcp-relay-agent">DHCP リレーエージェント</a></dt><dt>group, <a class="indexterm" href="#config-file">設定ファイル</a></dt><dt> shared-network , <a class="indexterm" href="#config-file">設定ファイル</a></dt><dt
>subnet, <a class="indexterm" href="#config-file">設定ファイル</a></dt><dt>オプション, <a class="indexterm" href="#config-file">設定ファイル</a></dt><dt>クライアント設定, <a class="indexterm" href="#s1-dhcp-configuring-client">DHCP クライアントの設定</a></dt><dt>コマンドラインオプション, <a class="indexterm" href="#idm122588480">サーバーの起動と停止</a></dt><dt>サーバーの停止方法, <a class="indexterm" href="#idm122588480">サーバーの起動と停止</a></dt><dt>サーバーの開始方法, <a class="indexterm" href="#idm122588480">サーバーの起動と停止</a></dt><dt>サーバー設定, <a class="indexterm" href="#s1-dhcp-configuring-server">DHCP サーバーの設定</a></dt><dt>リレーエージェント, <a class="indexterm" href="#dhcp-relay-agent">DHCP リレーエージェント</a></dt><dt>使用する理由, <a class="indexterm" href="#s1-dhcp-why">DHCP を使用する理由</a></dt><dt>全体
パラメーター, <a class="indexterm" href="#config-file">設定ファイル</a></dt><dt>接続, <a class="indexterm" href="#s1-dhcp-configuring-client">DHCP クライアントの設定</a></dt><dt>追加のリソース, <a class="indexterm" href="#s1-dhcp-additional-resources">その他のリソース</a></dt></dl></dd><dt>dhcpd.conf, <a class="indexterm" href="#config-file">設定ファイル</a></dt><dt>dhcpd.leases, <a class="indexterm" href="#idm122588480">サーバーの起動と停止</a></dt><dt> dhcrelay , <a class="indexterm" href="#dhcp-relay-agent">DHCP リレーエージェント</a></dt><dt>dig (参照 BIND)</dt><dt>DNS</dt><dd><dl><dt>定義, <a class="indexterm" href="#ch-DNS_Servers">DNS サーバー</a></dt><dd><dl><dt>(参照 BIND)</dt></dl></dd></dl></dd><dt>documentation</dt><dd><dl><dt>finding installed, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt></dl></dd><dt>DoS attack (参照 Denial of Service
attack)</dt><dt>drivers (å‚ç…§ kernel module)</dt><dt>DSA ã‚ー</dt><dd><dl><dt>生æˆ, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">éµãƒšã‚¢ã®ç”Ÿæˆ</a></dt></dl></dd><dt>du, <a class="indexterm" href="#s2-sysinfo-filesystems-du">Using the du Command</a></dt><dt>Dynamic Host Configuration Protocol (å‚ç…§ DHCP)</dt></dl></div><div class="indexdiv"><h3>E</h3><dl><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="indexterm" 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><dt>epoch, <a class="indexterm" href="#s2-proc-stat"> /proc/stat </a></dt><dd><dl><dt>(å‚ç…§ /proc/stat )</dt><dt>definition of, <a class="indexterm" href="#s2-proc-stat"> /proc/stat </a></dt></dl></dd><dt> exec-shield </dt><dd><dl><dt>enabling, <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt>introducing, <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt></dl></dd><dt>execution domains, <a class="indexterm" href="#s2-proc-execdomains"> /proc/execdomains </a></dt><dd><dl><dt>(å‚ç…§ /proc/execdomains )</dt><dt>definition of, <a class="indexterm" href="#s2-proc-execdomains"> /proc/execdomains </a></dt></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-fet
chmail">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 clas
s="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>file system</dt><dd><dl><dt>virtual (å‚ç…§ proc file system)</dt></dl></dd><dt>files, proc file system</dt><dd><dl><dt>changing, <a class="indexterm" href="#s2-proc-change">Changing Virtual Files</a>, <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt><dt>viewing, <a class="indexterm" href="#s2-proc-viewing">Viewing Virtual Files</a>, <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt></dl></dd><dt>findmnt, <a class="indexterm" href="#s2-sysinfo-filesystems-findmnt">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>FQDN (å‚ç…§ 完全修飾ドメインå)</dt><dt>frame buffer device, <a class="indexterm" href="#s2-proc-fb"> /proc/fb </a></dt><dd><dl><dt>(å‚ç…§ /proc/fb )</dt></dl></dd><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, <a class="indexterm" href="#s2-x-clients-desktop">デスクトップ環境</a></dt><dd><dl><dt>(å‚ç…§ X)</dt></dl></dd><dt> gnome-system-log (å‚ç…§ Log File Viewer )</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">Usin
g the System Monitor Tool</a></dt><dt>GnuPG</dt><dd><dl><dt>checking RPM package signatures, <a class="indexterm" href="#s1-check-rpm-sig">パッケージã®ç½²åを確èªã™ã‚‹</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></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>HTTP サーãƒãƒ¼ (å‚ç…§ Apache HTTP Server)</dt><dt>httpd (å‚ç…§ Apache HTTP Server)</dt><dt>hugepages</dt><dd><dl><dt>configuration of, <a class="indexterm" href="#s3-proc-sys-vm"> /proc/sys/vm/ </a></dt></dl></dd></dl></div><div class="indexdiv"><h3>I</h3><dl><dt> ifdown , <a class="indexterm" href="#s1-networkscripts-control">インターフェース制御スクリプト</a></dt><dt> ifup , <a class="indexterm" href="#s1-networkscripts-control">ã‚
¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹åˆ¶å¾¡ã‚¹ã‚¯ãƒªãƒ—ト</a></dt><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>KDE, <a class="indexterm" href="#s2-x-clients-desktop">デスクトップ環境</a></dt><dd><dl><dt>(å‚ç…§ X)</dt></dl></dd><dt>kdump</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documents, <a class="i
ndexterm" href="#s2-kdump-resources-installed">インストールされているドキュメント</a></dt><dt>manual pages, <a class="indexterm" href="#s2-kdump-resources-installed">インストールされているドキュメント</a></dt><dt>websites, <a class="indexterm" href="#s2-kdump-resources-online">役に立つ Web サイト</a></dt></dl></dd><dt>analyzing the dump (参照 crash)</dt><dt>configuring the service</dt><dd><dl><dt>default action, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-action">Changing the Default Action</a></dt><dt>dump image compression, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-filtering">Configuring the Core Collector</a></dt><dt>filtering level, <a class="indexterm" href="#s3-kdump-configuration-gui-filtering">The Filtering Settings Tab<
/a>, <a class="indexterm" href="#s3-kdump-configuration-cli-filtering">Configuring the Core Collector</a></dt><dt>initial RAM disk, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>kernel image, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>kernel options, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>memory usage, <a class="indexterm" href="#s3-kdump-configuration-firstboot-memory">Configuring the Memory Usage</a>, <a class="indexterm" href="#s3-kdump-configuration-gui-basic">The Basic Settings Tab</a>, <a class="indexterm" href="#s3-k
dump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>supported targets, <a class="indexterm" href="#s3-kdump-configuration-gui-target">The Target Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-target">Configuring the Target Type</a></dt><dt>target location, <a class="indexterm" href="#s3-kdump-configuration-gui-target">The Target Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-target">Configuring the Target Type</a></dt></dl></dd><dt>enabling the service, <a class="indexterm" href="#s3-kdump-configuration-firstboot-enable">サービスの有効化</a>, <a class="indexterm" href="#s3-kdump-configuration-gui-enable">サービスの有効化</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-enable">サービスの有効化</a></dt><dt>installing, <a class="indexterm" href="#s1-kdump-installation">Installing the kdump Service</a></dt><dt>running the service, <a class="indexterm" href="#s3-kdump-confi
guration-cli-enable">サービスã®æœ‰åŠ¹åŒ–</a></dt><dt>system requirements, <a class="indexterm" href="#s1-kdump-configuration">Configuring the kdump Service</a></dt><dt>testing the configuration, <a class="indexterm" href="#s2-kdump-configuration-testing">Testing the Configuration</a></dt></dl></dd><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 Dump Configuration (å‚ç…§ kdump)</dt><dt>kernel module</dt><dd><dl><dt>bonding module, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dd><dl><dt>description, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>definition, <a class="indexterm" href="#ch-Working_with_Kernel_Modules">Working with Kernel Modules</a></dt><dt>directories</dt><dd><dl><dt> /etc/sysconfig/modules/ , <a class="indexterm" href="#sec-Pers
istent_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>Ethernet module</dt><dd><dl><dt>supporting multiple cards, <a class="indexterm" href="#sec-Using_Multiple_Ethernet_Cards">複数のイーサネットカードの使用</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">Persisten
t 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>bonding module parameters, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt><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-doc</dt><dd><dl><dt>documentation files, <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-pack
ages">カーネルパッケージの概要</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> kwin , <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマネージャ</a></dt><dd><dl><dt>(参照 X)</dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LDAP (参照 OpenLDAP)</dt><dt>log files, <a class="indexterm" href="#ch-Viewing_and_Managing_Log_Files">ログファイルの表示および管理</a></dt><dd><dl><dt>(参照 ログビューアー )</dt><dt>locating, <a class="indexterm" href="#s1-logfiles-locating">ログファイルを探す</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-l
scpu">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>, <a class="indexterm" href="#s2-proc-pci"> /proc/bus/pci </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> metacity , <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマネージャ</a></dt><dd><dl><dt>(参照 X)</dt></dl></dd><dt> modinfo , <a class="indexterm" hr
ef="#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" href="#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><dt>Multihomed DHCP</dt><dd><
dl><dt>server configuration, <a class="indexterm" href="#sect-Configuring_a_Multihomed_DHCP_Server">Configuring a Multihomed DHCP Server</a></dt><dt>ホストの設定, <a class="indexterm" href="#sect-dns_Host_Configuration">ホストの設定</a></dt></dl></dd><dt>multiple domains</dt><dd><dl><dt>specifying in SSSD, <a class="indexterm" href="#sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">Support for Multiple Domains</a></dt></dl></dd><dt> mwm , <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマネージャ</a></dt><dd><dl><dt>(参照 X)</dt></dl></dd></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>named (参照 BIND)</dt><dt> net program, <a class="indexterm" href="#s2-samba-programs">Samba ディストリビューションプログラム</a></dt><dt>network</dt><dd><dl><dt>bridge</dt><dd><dl><dt>bridging, <a class="indexterm" href="#s2-networkscripts-interfaces_network-bridge">ネットワークブリッジ</a></dt></dl></dd><d
t>interfaces</dt><dd><dl><dt>802.1q, <a class="indexterm" href="#s2-networkscripts-interfaces_802.1q-vlan-tagging">Setting up 802.1q VLAN tagging</a></dt><dt>VLAN, <a class="indexterm" href="#s2-networkscripts-interfaces_802.1q-vlan-tagging">Setting up 802.1q VLAN tagging</a></dt></dl></dd></dl></dd><dt>Network Time Protocol, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol の設定</a></dt><dd><dl><dt>ntpd, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol の設定</a></dt><dt>ntpdate, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol の設定</a></dt></dl></dd><dt>NIC</dt><dd><dl><dt>binding into single channel, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt></dl></dd><dt> nmblooku
p program, <a class="indexterm" href="#s2-samba-programs">Samba ディストリビューションプログラム</a></dt><dt>NTP (参照 Network Time Protocol)</dt><dt>ntpd, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol の設定</a></dt><dt>ntpdate, <a class="indexterm" href="#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol の設定</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>インストール, <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" h
ref="#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></dt><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></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-start
ing">サービスの開始</a></dt><dt>機能, <a class="indexterm" href="#s3-ldap-features">OpenLDAP 機能</a></dt><dt>状態の確認, <a class="indexterm" href="#s3-ldap-running-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>DSA キー</dt><dd><dl><dt>生成, <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>RSA バージョン 1 キー</dt><dd><dl><dt>生成, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">鍵ペアの生成</a></dt></dl></dd><dt> ssh-add , <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">ssh-agent の設定</a></dt><dt> ssh-agent , <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">ssh-agent の設定</a></dt><dt>ssh-keygen</dt><dd><dl><dt>DSA, <a class="indexterm" href="#s3-ssh-configur
ation-keypairs-generating">éµãƒšã‚¢ã®ç”Ÿæˆ</a></dt><dt>RSA, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">éµãƒšã‚¢ã®ç”Ÿæˆ</a></dt><dt>RSA ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 1, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">éµãƒšã‚¢ã®ç”Ÿæˆ</a></dt></dl></dd><dt>ã‚ーèªè¨¼ã®ä½¿ç”¨, <a class="indexterm" href="#s2-ssh-configuration-keypairs">ã‚ーèªè¨¼ã®ä½¿ç”¨</a></dt><dt>クライアント, <a class="indexterm" href="#s1-ssh-clients">OpenSSH クライアント</a></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>サーãƒãƒ¼, <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 /dev/oprofile/ </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</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-support">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</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</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</a></dt><dd><dl><dt>log file, <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</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</a></dt><dt>starting, <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</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>Packag
eKit, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dd><dl><dt>PolicyKit</dt><dd><dl><dt>認証, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">ソフトウェアの更新を用いたパッケージの更新</a></dt></dl></dd><dt>アーキテクチャー, <a class="indexterm" href="#sec-PackageKit_Architecture">PackageKit アーキテクチャー</a></dt><dt>トランザクションログの表示, <a class="indexterm" href="#sec-Viewing_the_Transaction_Log">トランザクションログの表示</a></dt><dt>パッケージの, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>パッケージのアンインストール, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>パッケージの更新, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>パッケージの管理, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>パッケージの表示, <a class="indexterm" href=
"#ch-PackageKit">PackageKit</a></dt><dt>パッケージグループのインストールおよび削除, <a class="indexterm" href="#sec-Installing_and_Removing_Package_Groups">パッケージグループのインストールおよび削除</a></dt><dt>追加と削除, <a class="indexterm" href="#sec-Using_Add_Remove_Software">ソフトウェアの追加/削除の使用</a></dt></dl></dd><dt>PackageKit を用いたパッケージの更新</dt><dd><dl><dt>PolicyKit, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">ソフトウェアの更新を用いたパッケージの更新</a></dt></dl></dd><dt>packages</dt><dd><dl><dt>determining file ownership with, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>finding deleted files from, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>iFedora installation media, <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>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 headers and makefiles, <a class="indexterm" href="#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>kernel-doc</dt><dd><dl><dt>documentation files, <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>locating documentatio
n for, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>obtaining list of files, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</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-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>RPM, <a class="indexterm" href="#ch-RPM">RPM</a></dt><dd><dl><dt>already installed, <a class="indexterm" href="#s3-rpm-errors">すでにインストールされているパッケージ</a></dt><dt>conflict, <a class="indexterm" href="#s3-rpm-conflicting-files">ファイルの競合</a></dt><dt>failed dependencies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">未解決の依存性</a></dt><dt>pristine sources, <a class="indexterm" href="#s1-rpm-design">RPM の設計目
標</a></dt><dt>querying, <a class="indexterm" href="#s2-rpm-querying">問い合わせ</a></dt><dt>source and binary packages, <a class="indexterm" href="#ch-RPM">RPM</a></dt></dl></dd><dt>Yum instead of RPM, <a class="indexterm" href="#ch-RPM">RPM</a></dt><dt>Yum を用いたパッケージのアンインストール</dt><dd><dl><dt>yum remove package_name, <a class="indexterm" href="#sec-Removing">パッケージの削除</a></dt></dl></dd><dt>Yum を用いたパッケージの一覧表示</dt><dd><dl><dt>yum list available, <a class="indexterm" href="#sec-Listing_Packages">パッケージの一覧</a></dt></dl></dd><dt>パッケージの表示</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Displaying_Package_Information">パッケージ情報の表示</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>PolicyKit, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">ソフトウェアの更新を用いたパッケージの更新</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">IPP プリンタの追加</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_Prin
ter">ローカルプリンタの追加</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="#idm104518544">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> proc file system</dt><dd><dl><dt> /proc/buddyinfo , <a class="indexterm" href="#s2-proc-buddyinfo"> /proc/buddyinfo </a></dt><dt> /proc/bus/ directory, <a class="indexterm" href="#s2-proc-dir-bus"> /proc/bus/ </a></dt><dt> /proc/bus/pci </dt><dd><dl><dt>viewing using lspci , <a class="indexterm" href="#s2-proc-pci"> /proc/bus/pci </a></dt></dl></dd><dt> /proc/cmdline , <a class="indexterm" h
ref="#s2-proc-cmdline"> /proc/cmdline </a></dt><dt> /proc/cpuinfo , <a class="indexterm" href="#s2-proc-cpuinfo"> /proc/cpuinfo </a></dt><dt> /proc/crypto , <a class="indexterm" href="#s2-proc-crypto"> /proc/crypto </a></dt><dt> /proc/devices </dt><dd><dl><dt>block devices, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt><dt>character devices, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt></dl></dd><dt> /proc/dma , <a class="indexterm" href="#s2-proc-dma"> /proc/dma </a></dt><dt> /proc/driver/ directory, <a class="indexterm" href="#s2-proc-dir-driver"> /proc/driver/ </a></dt><dt> /proc/execdomains , <a class="indexterm" href="#s2-proc-execdomains"> /proc/execdomains </a></dt><dt> /proc/fb , <a class="indexterm" href="#s2-proc-fb"> /proc/fb </a></dt><dt> /proc/filesystems , <a class="indexterm" href="#s2-proc-filesystems"> /proc/filesystems </a></dt><dt> /proc/fs/ directory, <a class="indexterm" href="#s2-proc-dir-fs"> /proc/fs </a>
</dt><dt> /proc/interrupts , <a class="indexterm" href="#s2-proc-interrupts"> /proc/interrupts </a></dt><dt> /proc/iomem , <a class="indexterm" href="#s2-proc-iomem"> /proc/iomem </a></dt><dt> /proc/ioports , <a class="indexterm" href="#s2-proc-ioports"> /proc/ioports </a></dt><dt> /proc/irq/ directory, <a class="indexterm" href="#s2-proc-dir-irq"> /proc/irq/ </a></dt><dt> /proc/kcore , <a class="indexterm" href="#s2-proc-kcore"> /proc/kcore </a></dt><dt> /proc/kmsg , <a class="indexterm" href="#s2-proc-kmsg"> /proc/kmsg </a></dt><dt> /proc/loadavg , <a class="indexterm" href="#s2-proc-loadavg"> /proc/loadavg </a></dt><dt> /proc/locks , <a class="indexterm" href="#s2-proc-locks"> /proc/locks </a></dt><dt> /proc/mdstat , <a class="indexterm" href="#s2-proc-mdstat"> /proc/mdstat </a></dt><dt> /proc/meminfo , <a class="indexterm" href="#s2-proc-meminfo"> /proc/meminfo </a></dt><dt> /proc/misc , <a class="indexterm" href="#s2-proc-misc"> /proc/misc </a></dt><dt> /proc/modules ,
<a class="indexterm" href="#s2-proc-modules"> /proc/modules </a></dt><dt> /proc/mounts , <a class="indexterm" href="#s2-proc-mounts"> /proc/mounts </a></dt><dt> /proc/mtrr , <a class="indexterm" href="#s2-proc-mtrr"> /proc/mtrr </a></dt><dt> /proc/net/ directory, <a class="indexterm" href="#s2-proc-dir-net"> /proc/net/ </a></dt><dt> /proc/partitions , <a class="indexterm" href="#s2-proc-partitions"> /proc/partitions </a></dt><dt> /proc/PID/ directory, <a class="indexterm" href="#s2-proc-pid"> /proc/PID/ </a></dt><dt> /proc/scsi/ directory, <a class="indexterm" href="#s2-proc-dir-scsi"> /proc/scsi/ </a></dt><dt> /proc/self/ directory, <a class="indexterm" href="#s3-proc-self"> /proc/self/ </a></dt><dt> /proc/slabinfo , <a class="indexterm" href="#s2-proc-slabinfo"> /proc/slabinfo </a></dt><dt> /proc/stat , <a class="indexterm" href="#s2-proc-stat"> /proc/stat </a></dt><dt> /proc/swaps , <a class="indexterm" href="#s2-proc-swaps"> /proc/swaps </a></dt><dt> /proc/sys/ directory
, <a class="indexterm" href="#s2-proc-dir-sys"> /proc/sys/ </a>, <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt><dd><dl><dt>(参照 sysctl )</dt><dt> /proc/sys/dev/ directory, <a class="indexterm" href="#s3-proc-sys-dev"> /proc/sys/dev/ </a></dt><dt> /proc/sys/fs/ directory, <a class="indexterm" href="#s3-proc-sys-fs"> /proc/sys/fs/ </a></dt><dt> /proc/sys/kernel/ directory, <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt> /proc/sys/kernel/exec-shield , <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt>/proc/sys/kernel/sysrq (参照 system request key)</dt><dt> /proc/sys/net/ directory, <a class="indexterm" href="#s3-proc-sys-net"> /proc/sys/net/ </a></dt><dt> /proc/sys/vm/ directory, <a class="indexterm" href="#s3-proc-sys-vm"> /proc/sys/vm/ </a></dt></dl></dd><dt> /proc/sysrq-trigger , <a class="indexterm" href="#s2-proc-sysrq-trigger"> /proc/sysrq-trigger </a></dt><dt> /proc/sysvi
pc/ directory, <a class="indexterm" href="#s2-proc-dir-sysvipc"> /proc/sysvipc/ </a></dt><dt> /proc/tty/ directory, <a class="indexterm" href="#s2-proc-tty"> /proc/tty/ </a></dt><dt> /proc/uptime , <a class="indexterm" href="#s2-proc-uptime"> /proc/uptime </a></dt><dt> /proc/version , <a class="indexterm" href="#s2-proc-version"> /proc/version </a></dt><dt>additional resources, <a class="indexterm" href="#s1-proc-additional-resources">参考文献</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-proc-installed-documentation">インストールされているドキュメント</a></dt><dt>useful websites, <a class="indexterm" href="#s2-proc-useful-websites">役に立つ Web サイト</a></dt></dl></dd><dt>changing files within, <a class="indexterm" href="#s2-proc-change">Changing Virtual Files</a>, <a class="indexterm" href="#s2-proc-dir-sys"> /proc/sys/ </a>, <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt><dt>files wit
hin, top-level, <a class="indexterm" href="#s1-proc-topfiles">Top-level Files within the proc File System</a></dt><dt>introduced, <a class="indexterm" href="#ch-proc">The proc File System</a></dt><dt>process directories, <a class="indexterm" href="#s2-proc-processdirs">Process Directories</a></dt><dt>subdirectories within, <a class="indexterm" href="#s1-proc-directories">Directories within /proc/</a></dt><dt>viewing files within, <a class="indexterm" href="#s2-proc-viewing">Viewing Virtual Files</a></dt></dl></dd><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-sys
tem-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>rndc (å‚ç…§ BIND)</dt><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-errors">ã™ã§ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るパッケージ</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">パッケージã®ç½²åを確èªã
™ã‚‹</a></dt><dt>configuration file changes</dt><dd><dl><dt>conf.rpmsave, <a class="indexterm" href="#sec-Configuration_File_Changes">è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®å¤‰æ›´</a></dt></dl></dd><dt>conflicts, <a class="indexterm" href="#s3-rpm-conflicting-files">ファイルã®ç«¶åˆ</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-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>failed dependencies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">未解決ã®ä¾å˜æ€§</a></dt><dt>file name, <a class="indexterm" href="#sec-Installing_and_Upgrading">インストールã¨ã‚¢ãƒƒãƒ—グレード</a></dt><dt>finding deleted
files with, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>GnuPG, <a class="indexterm" href="#s1-check-rpm-sig">パッケージの署名を確認する</a></dt><dt>md5sum, <a class="indexterm" href="#s1-check-rpm-sig">パッケージの署名を確認する</a></dt><dt>querying, <a class="indexterm" href="#s2-rpm-querying">問い合わせ</a></dt><dt>querying uninstalled packages, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>RPM パッケージの検索, <a class="indexterm" href="#s2-rpm-finding">RPM パッケージの検索</a></dt><dt>アップグレード, <a class="indexterm" href="#sec-Installing_and_Upgrading">インストールとアップグレード</a></dt><dt>アンインストール, <a class="indexterm" href="#s2-rpm-uninstalling">アンインストール</a></dt><dt>インストール, <a class="indexterm" href="#sec-Installing_and_Upgrading">イン
ストールとアップグレード</a></dt><dt>インストール済みのアップグレードの実行, <a class="indexterm" href="#s2-rpm-freshening">インストール済みのアップグレードの実行</a></dt><dt>ウェブサイト, <a class="indexterm" href="#s2-rpm-useful-websites">役に立つ Web サイト</a></dt><dt>ティップス, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>ドキュメント, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>ファイルの競合</dt><dd><dl><dt>解決, <a class="indexterm" href="#s3-rpm-conflicting-files">ファイルの競合</a></dt></dl></dd><dt>ファイル一覧の問い合わせ, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>依存性, <a class="indexterm" href="#s3-rpm-unresolved-dependency">未解決の依存性</a></dt><dt>書籍について, <a cl
ass="indexterm" href="#s2-rpm-related-books">関連書籍</a></dt><dt>検証, <a class="indexterm" href="#s2-rpm-verifying">検証</a></dt><dt>設定ファイルの変更, <a class="indexterm" href="#sec-Configuration_File_Changes">設定ファイルの変更</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>RSA バージョン 1 キー</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-printer">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 Controller, <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-s
amba-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 Member 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-passwords">æš—åˆåŒ–ã•ã‚ŒãŸãƒ‘スワード</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="index
term" 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-stopping-spam">スパムの停止</a></dt><dt>デフォルトインストール, <a class="indexterm" href="#s3-email-mta-sendmail-default">Sendmail のデフォルトインストール</a></dt><dt>マスカレード, <a class="indexterm" href="#s
3-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>slab pools (参照 /proc/slabinfo )</dt><dt>slapd (参照 OpenLDAP)</dt><dt> smbcacls program, <a class="indexterm" href="#s2-samba-programs">Samba ディストリビューションプログラム</a></dt><dt> smbclient , <a class="indexterm" href="#s3-samba-connect-share-cmdline">コマンドライン</a></dt><dt> smbclient progra
m, <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>SpamAssassin</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><d
t>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><d
d><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-add , <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">ssh-agent の設定</a></dt><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>SSSD</dt><dd><dl><dt>Configuring a Microsoft Active Directory Domain for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">Configuring a Microsoft Active Directory Domain</a></dt><dt>Configuring a proxy domain for, <a class="indexterm" href="#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">Configuring a Proxy Domain</a></dt><dt>Configuring an LDAP domain for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt><dt>Selecting an LDAP schema for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an
LDAP Domain</a></dt><dt>Setting Up Kerberos authentication for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">Setting Up Kerberos Authentication</a></dt><dt>Specifying timeout values for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt></dl></dd><dt> stunnel , <a class="indexterm" href="#s3-email-security-servers">安全な電子クライアント通信</a></dt><dt> sysconfig directory</dt><dd><dl><dt> /etc/sysconfig/apm-scripts/ directory, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/arpwatch , <a class="indexterm" href="#s2-sysconfig-arpwatch"> /etc/sysconfig/arpwatch </a></dt><dt> /etc/sysconfig/authconfig , <a class="indexterm" href="#s2-sysconfig-authconfig"> /etc/sysconfig/authconfig </a></dt><dt> /etc/sysconfig/autofs , <a class="indexter
m" href="#s2-sysconfig-autofs"> /etc/sysconfig/autofs </a></dt><dt> /etc/sysconfig/cbq/ directory, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/clock , <a class="indexterm" href="#s2-sysconfig-clock"> /etc/sysconfig/clock </a></dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="#s2-sysconfig-dhcpd"> /etc/sysconfig/dhcpd </a></dt><dt> /etc/sysconfig/firstboot , <a class="indexterm" href="#s2-sysconfig-firewall"> /etc/sysconfig/firstboot </a></dt><dt> /etc/sysconfig/init , <a class="indexterm" href="#s2-sysconfig-init"> /etc/sysconfig/init </a></dt><dt> /etc/sysconfig/ip6tables-config , <a class="indexterm" href="#s2-sysconfig-ip6tables"> /etc/sysconfig/ip6tables-config </a></dt><dt> /etc/sysconfig/keyboard , <a class="indexterm" href="#s2-sysconfig-kybd"> /etc/sysconfig/keyboard </a></dt><dt> /etc/sysconfig/ldap , <a class="indexterm" href="#s2-sysconfig-ldap"> /etc/sysconfig/ldap </a>
</dt><dt> /etc/sysconfig/named , <a class="indexterm" href="#s2-sysconfig-named"> /etc/sysconfig/named </a></dt><dt> /etc/sysconfig/network , <a class="indexterm" href="#s2-sysconfig-network">/etc/sysconfig/network</a></dt><dt> /etc/sysconfig/network-scripts/ directory, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dd><dl><dt>(参照 network)</dt></dl></dd><dt> /etc/sysconfig/networking/ directory, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/ntpd , <a class="indexterm" href="#s2-sysconfig-ntpd"> /etc/sysconfig/ntpd </a></dt><dt> /etc/sysconfig/quagga , <a class="indexterm" href="#s2-sysconfig-quagga"> /etc/sysconfig/quagga </a></dt><dt> /etc/sysconfig/radvd , <a class="indexterm" href="#s2-sysconfig-radvd"> /etc/sysconfig/radvd </a></dt><dt> /etc/sysconfig/samba , <a class="indexterm" href="#s2-sysconfig-samba"> /etc/sysconfig
/samba </a></dt><dt> /etc/sysconfig/selinux , <a class="indexterm" href="#s2-sysconfig-selinux"> /etc/sysconfig/selinux </a></dt><dt> /etc/sysconfig/sendmail , <a class="indexterm" href="#s2-sysconfig-sendmail"> /etc/sysconfig/sendmail </a></dt><dt> /etc/sysconfig/spamassassin , <a class="indexterm" href="#s2-sysconfig-spamd"> /etc/sysconfig/spamassassin </a></dt><dt> /etc/sysconfig/squid , <a class="indexterm" href="#s2-sysconfig-squid"> /etc/sysconfig/squid </a></dt><dt> /etc/sysconfig/system-config-users , <a class="indexterm" href="#s2-sysconfig-rcu"> /etc/sysconfig/system-config-users </a></dt><dt> /etc/sysconfig/vncservers , <a class="indexterm" href="#s2-sysconfig-vncservers"> /etc/sysconfig/vncservers </a></dt><dt> /etc/sysconfig/xinetd , <a class="indexterm" href="#s2-sysconfig-xinetd"> /etc/sysconfig/xinetd </a></dt><dt>additional resources, <a class="indexterm" href="#s1-sysconfig-additional-resources">その他のリソース</a></dt><dd><dl><dt>installed documen
tation, <a class="indexterm" href="#s2-sysconfig-installed-documentation">インストールされているドキュメント</a></dt></dl></dd><dt>directories in, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt></dl></dd><dt>sysconfig ディレクトリー</dt><dd><dl><dt> /etc/sysconfig/network-scripts/ ディレクトリー, <a class="indexterm" href="#ch-Network_Interfaces">ネットワーク・インターフェース</a></dt><dt>含まれるファイル, <a class="indexterm" href="#s1-sysconfig-files">Files in the /etc/sysconfig/ Directory</a></dt><dt>追加情報, <a class="indexterm" href="#ch-The_sysconfig_Directory">sysconfig ディレクトリー</a></dt></dl></dd><dt> sysctl </dt><dd><dl><dt>configuring with /etc/sysctl.conf , <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt><dt>controlling /proc/sys/ , <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a>
</dt></dl></dd><dt>SysRq (参照 system request key)</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 request key</dt><dd><dl><dt>enabling, <a class="indexterm" href="#s2-proc-dir-sys"> /proc/sys/ </a></dt></dl></dd><dt>System Request Key</dt><dd><dl><dt>definition of, <a class="indexterm" href="#s2-proc-dir-sys"> /proc/sys/ </a></dt><dt>setting timing for, <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt></dl></dd><dt> system-config-authentication (参照 認証の設定ツール )</dt><dt>system-config-kdump (参照 kdump)</dt><dt>system-config-users (参照 ユーザーの設定およびグループの設定)</dt><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>TLB cache (参照 hugepages)</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><dt> twm , <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマネージャ</a></dt><dd><dl><dt>(参照 X)</dt></dl></dd></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>User Manager (参照 ユーザーの設定)</dt><dt>useradd コマンド</dt><dd><dl><dt>ユーザーアカウント作成, <a class="indexterm" href="#s2-users-tools-users-add">新規ユーザーを追加する</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>virtual file system (参照 proc file system)</dt><dt>virtual files (参照 proc file system)</dt><dt>virtual host (参照 Apache HTTP Server)</dt><dt> vsft
pd , <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">vsftpd 設定オプション</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>window managers (参照 X)</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="in
dexterm" href="#s3-samba-encrypted-passwords">暗合化されたパスワード</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>X</dt><dd><dl><dt> /etc/X11/xorg.conf </dt><dd><dl><dt>boolean values for, <a class="indexterm" href="#s2-x-server-config-xorg.conf-struct">The Structure of the Configuration</a></dt><dt> Device , <a class="indexterm" href="#s3-x-server-config-xorg.conf-device">The Device section</a></dt><dt> DRI , <a class="indexterm" href="#s3-x-server-config-xorg.conf-dri">The DRI section</a></dt><dt> Files section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-files">The Files section</a></dt><dt> InputDevice section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-inputd">The InputDevice section</a></dt><dt>introducing, <a class="indexterm" href="#s2-x-server-config-xorg.conf.d">The xorg.conf.d Directory</a>, <a class="indexterm" href="#s2-x-server-config-xorg.conf">The xorg.conf File</a></dt><dt> Monitor , <a class="ind
exterm" href="#s3-x-server-config-xorg.conf-monitor">The Monitor section</a></dt><dt> Screen , <a class="indexterm" href="#s3-x-server-config-xorg.conf-screen">The Screen section</a></dt><dt> Section tag, <a class="indexterm" href="#s2-x-server-config-xorg.conf-struct">The Structure of the Configuration</a></dt><dt> ServerFlags section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-serverf">The ServerFlags section</a></dt><dt> ServerLayout section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-serverl">ServerLayout</a></dt><dt>structure of, <a class="indexterm" href="#s2-x-server-config-xorg.conf-struct">The Structure of the Configuration</a></dt></dl></dd><dt>additional resources, <a class="indexterm" href="#s1-x-additional-resources">その他のリソース</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-x-installed-documentation">インストールされているドキュメント</a></dt><dt>useful websites, <a class="in
dexterm" href="#s2-x-useful-websites">役に立つ Web サイト</a></dt></dl></dd><dt>configuration directory</dt><dd><dl><dt> /etc/X11/xorg.conf.d , <a class="indexterm" href="#s2-x-server-config-xorg.conf.d">The xorg.conf.d Directory</a></dt></dl></dd><dt>configuration files</dt><dd><dl><dt> /etc/X11/ directory, <a class="indexterm" href="#s1-x-server-configuration">X サーバー設定ファイル</a></dt><dt> /etc/X11/xorg.conf , <a class="indexterm" href="#s2-x-server-config-xorg.conf">The xorg.conf File</a></dt><dt>options within, <a class="indexterm" href="#s1-x-server-configuration">X サーバー設定ファイル</a></dt><dt>server options, <a class="indexterm" href="#s2-x-server-config-xorg.conf.d">The xorg.conf.d Directory</a>, <a class="indexterm" href="#s2-x-server-config-xorg.conf">The xorg.conf File</a></dt></dl></dd><dt>desktop environments</dt><dd><dl><dt>GNOME, <a class="indexterm" href="#s2-x-clients-desktop">デスクトップ環境</a></dt><dt>KDE, <a
class="indexterm" href="#s2-x-clients-desktop">デスクトップ環境</a></dt></dl></dd><dt>fonts</dt><dd><dl><dt>Fontconfig, <a class="indexterm" href="#s1-x-fonts">フォント</a></dt><dt>Fontconfig, adding fonts to, <a class="indexterm" href="#s3-x-fonts-fontconfig-add">Fontconfig ã¸ã®ãƒ•ã‚©ãƒ³ãƒˆã®è¿½åŠ </a></dt><dt>FreeType, <a class="indexterm" href="#s1-x-fonts">フォント</a></dt><dt>introducing, <a class="indexterm" href="#s1-x-fonts">フォント</a></dt><dt>Xft, <a class="indexterm" href="#s1-x-fonts">フォント</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="#ch-The_X_Window_System">X Window System</a></dt><dt>window managers</dt><dd><dl><dt> kwin , <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマãƒãƒ¼ã‚¸ãƒ£</a></dt><dt> metacity , <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマãƒãƒ¼ã‚¸ãƒ£</a></dt><dt> mwm , <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマãƒãƒ¼ã‚¸ã
ƒ£</a></dt><dt> twm , <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマãƒãƒ¼ã‚¸ãƒ£</a></dt></dl></dd><dt>X clients, <a class="indexterm" href="#ch-The_X_Window_System">X Window System</a>, <a class="indexterm" href="#s1-x-clients">デスクトップ環境ã¨ã‚¦ã‚£ãƒ³ãƒ‰ã‚¦ãƒžãƒãƒ¼ã‚¸ãƒ£</a></dt><dd><dl><dt>desktop environments, <a class="indexterm" href="#s2-x-clients-desktop">デスクトップ環境</a></dt><dt>window managers, <a class="indexterm" href="#s2-x-clients-winmanagers">ウィンドウマãƒãƒ¼ã‚¸ãƒ£</a></dt></dl></dd><dt>X server, <a class="indexterm" href="#ch-The_X_Window_System">X Window System</a></dt><dd><dl><dt>features of, <a class="indexterm" href="#s1-x-server">The X Server</a></dt></dl></dd></dl></dd><dt>X Window System (å‚ç…§ X)</dt><dt>X.500 (å‚ç…§ OpenLDAP)</dt><dt>X.500 Lite (å‚ç…§ OpenLDAP)</dt><dt>Xorg (å‚ç…§ Xorg)</dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>Yum</dt><dd><dl><dt>Yum 㨠Yum リãƒã‚¸ãƒˆãƒªã
ƒ¼ã®è¨å®š, <a class="indexterm" href="#sec-Configuring_Yum_and_Yum_Repositories">Yum 㨠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¨å®š</a></dt><dt>Yum を用ã„ãŸã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="#sec-Installing">パッケージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«</a></dt><dt>Yum を用ã„ãŸãƒ‘ッケージ グループã®ã‚¢ãƒ³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="#sec-Removing">パッケージã®å‰Šé™¤</a></dt><dt>Yum を用ã„ãŸãƒ‘ッケージã®ã‚¢ãƒ³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="#sec-Removing">パッケージã®å‰Šé™¤</a></dt><dd><dl><dt>yum remove package_name, <a class="indexterm" href="#sec-Removing">パッケージã®å‰Šé™¤</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージã®ä¸€è¦§è¡¨ç¤º</dt><dd><dl><dt>yum grouplist, <a class="indexterm" href="#sec-Listing_Packages">パッケージã®ä¸€è¦§</a></dt><dt>yum list, <a class="indexterm" href="#sec-Listing_Packages">パッケージã®ä¸€è¦§</a></dt><dt>yum list all, <a class="indexterm" href="#sec-List
ing_Packages">パッケージの一覧</a></dt><dt>yum list available, <a class="indexterm" href="#sec-Listing_Packages">パッケージの一覧</a></dt><dt>yum list installed, <a class="indexterm" href="#sec-Listing_Packages">パッケージの一覧</a></dt><dt>yum repolist, <a class="indexterm" href="#sec-Listing_Packages">パッケージの一覧</a></dt></dl></dd><dt>Yum を用いたパッケージの検索</dt><dd><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Packages">パッケージの検索</a></dt></dl></dd><dt>Yum を用いたパッケージの表示</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Displaying_Package_Information">パッケージ情報の表示</a></dt></dl></dd><dt>Yum を用いたパッケージグループのインストール, <a class="indexterm" href="#sec-Installing">パッケージのインストール</a></dt><dt>Yum を用いたパッケージ一覧</dt><dd><dl><dt>Glob 表記, <a class="indexterm" href="#sec-Lis
ting_Packages">パッケージã®ä¸€è¦§</a></dt></dl></dd><dt>Yum プラグイン, <a class="indexterm" href="#sec-Yum_Plugins">Yum プラグイン</a></dt><dt>Yum リãƒã‚¸ãƒˆãƒªãƒ¼</dt><dd><dl><dt>Yum 㨠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¨å®š, <a class="indexterm" href="#sec-Configuring_Yum_and_Yum_Repositories">Yum 㨠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¨å®š</a></dt></dl></dd><dt>[main] オプションã®è¨å®š, <a class="indexterm" href="#sec-Setting_main_Options">[main] オプションã®è¨å®š</a></dt><dt>[repository] オプションã®è¨å®š, <a class="indexterm" href="#sec-Setting_repository_Options">[repository] オプションã®è¨å®š</a></dt><dt>パッケージã¨ãƒ‘ッケージ グループ, <a class="indexterm" href="#sec-Packages_and_Package_Groups">パッケージã¨ãƒ‘ッケージ グループ</a></dt><dt>パッケージã®è¡¨ç¤º</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Displaying_Package_Information">ãƒ‘ãƒƒã‚±ãƒ¼ã‚¸æƒ…å ±ã®è¡¨ç¤º</a></dt></dl></dd><dt>ã
ƒ—ラグイン</dt><dd><dl><dt>fs-snapshot, <a class="indexterm" href="#sec-Plugin_Descriptions">プラグインã®èª¬æ˜Ž</a></dt><dt>presto, <a class="indexterm" href="#sec-Plugin_Descriptions">プラグインã®èª¬æ˜Ž</a></dt><dt>refresh-packagekit, <a class="indexterm" href="#sec-Plugin_Descriptions">プラグインã®èª¬æ˜Ž</a></dt><dt>rhnplugin, <a class="indexterm" href="#sec-Plugin_Descriptions">プラグインã®èª¬æ˜Ž</a></dt><dt>security, <a class="indexterm" href="#sec-Plugin_Descriptions">プラグインã®èª¬æ˜Ž</a></dt></dl></dd><dt>プラグインã®æœ‰åŠ¹åŒ–, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Yum プラグインã®ç„¡åŠ¹åŒ–ã€æœ‰åŠ¹åŒ–ã€è¨å®š</a></dt><dt>プラグインã®ç„¡åŠ¹åŒ–, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Yum プラグインã®ç„¡åŠ¹åŒ–ã€æœ‰åŠ¹åŒ–ã€è¨å®š</a></dt><dt>プラグインã®è¨å®š, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disab
ling_Yum_Plugins">Yum プラグインã®ç„¡åŠ¹åŒ–ã€æœ‰åŠ¹åŒ–ã€è¨å®š</a></dt><dt>リãƒã‚¸ãƒˆãƒªãƒ¼, <a class="indexterm" href="#sec-Managing_Yum_Repositories">Yum リãƒã‚¸ãƒˆãƒªã®è¿½åŠ ・有効化ãŠã‚ˆã³ç„¡åŠ¹åŒ–</a>, <a class="indexterm" href="#sec-Creating_a_Yum_Repository">Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®ä½œæˆ</a></dt><dt>変数, <a class="indexterm" href="#sec-Using_Yum_Variables">Yum 変数ã®ä½¿ã„æ–¹</a></dt><dt>è¿½åŠ ãƒªã‚½ãƒ¼ã‚¹, <a class="indexterm" href="#sec-Additional_Resources">ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></dt></dl></dd><dt>Yum ã§ã®æ›´æ–°</dt><dd><dl><dt>ã‚»ã‚ュリティ関連ã®ãƒ‘ッケージ更新, <a class="indexterm" href="#sec-Updating_Packages">パッケージã®æ›´æ–°</a></dt><dt>パッケージã®æ›´æ–°, <a class="indexterm" href="#sec-Updating_Packages">パッケージã®æ›´æ–°</a></dt><dt>全パッケージã¨ä¾å˜æ€§ã®æ›´æ–°, <a class="indexterm" href="#sec-Updating_Packages">パッケージã®æ›´æ–°</a></dt><dt>å˜ä¸€ãƒ‘ッケージã®æ›´æ–
°, <a class="indexterm" href="#sec-Updating_Packages">パッケージã®æ›´æ–°</a></dt><dt>æ›´æ–°ã®ç¢ºèª, <a class="indexterm" href="#sec-Checking_For_Updates">æ›´æ–°ã®ç¢ºèª</a></dt></dl></dd><dt>Yum リãƒã‚¸ãƒˆãƒªãƒ¼</dt><dd><dl><dt>PackageKit を用ã„㟠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¡¨ç¤º, <a class="indexterm" href="#sec-Setting_preferences_for_software_sources">ソフトウェアソースã®è¨å®š</a></dt></dl></dd></dl></div></div></div></div></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/common.css b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/css/default.css b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/lang.css b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/overrides.css b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/css/print.css b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/1.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/1.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/10.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/10.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/10.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/11.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/11.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/11.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/12.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/12.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/12.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/13.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/13.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/13.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/14.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/14.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/14.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/15.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/15.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/15.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/16.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/16.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/16.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/17.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/17.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/17.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/18.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/18.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/18.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/19.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/19.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/19.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/2.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/2.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/2.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/20.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/20.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/20.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/21.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/21.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/21.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/22.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/22.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/22.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/23.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/23.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/23.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/24.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/24.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/24.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/25.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/25.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/25.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/26.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/26.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/26.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/27.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/27.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/27.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/28.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/28.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/28.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/29.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/29.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/29.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/3.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/30.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/30.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/30.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/31.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/31.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/31.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/32.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/32.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/32.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/33.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/33.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/33.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/34.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/34.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/34.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/35.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/35.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/35.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/36.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/36.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/36.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/37.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/37.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/37.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/38.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/38.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/38.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/39.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/39.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/39.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/4.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/4.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/4.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/40.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/40.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/40.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/5.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/5.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/5.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/6.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/6.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/6.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/7.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/7.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/7.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/8.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/8.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/8.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/9.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/9.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/9.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/documentation.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/dot.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/dot2.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/green.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/green.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/h1-bg.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/image_left.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/image_right.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/important.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/important.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/important.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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"
+ 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/17/html/System_Administrators_Guide/Common_Content/images/logo.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/note.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/note.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/note.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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"
+ 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/17/html/System_Administrators_Guide/Common_Content/images/red.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/red.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/shade.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/shine.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/stock-go-back.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/stock-go-forward.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/stock-go-up.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/stock-home.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/title_logo.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/title_logo.svg b/public_html/ja-JP/Fedora/17/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/17/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/17/html/System_Administrators_Guide/Common_Content/images/warning.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/warning.svg b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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"
+ 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/17/html/System_Administrators_Guide/Common_Content/images/watermark-draft.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/Common_Content/images/yellow.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/app-Revision_History.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/app-Revision_History.html
new file mode 100644
index 0000000..913e600
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/app-Revision_History.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>付録F 改訂履歴</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s1-proc-additional-resources.html" title="E.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-proc-additional-resources.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><stron
g>次へ</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-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-proc-additional-resources.html"><strong>戻る</strong>E.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/17/html/System_Administrators_Guide/appe-Consistent_Network_Device_Naming.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/appe-Consistent_Network_Device_Naming.html
new file mode 100644
index 0000000..e3968dc
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/appe-Consistent_Network_Device_Naming.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>付録A Consistent Network Device Naming</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s2-kdump-resources-online.html" title="23.4.2. 役に立つ Web サイト" /><link rel="next" href="sect-Consistent_Network_Device_Naming-System_Requirements.html" title="A.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-kdump-resources-online.html"><strong>
戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Consistent_Network_Device_Naming-System_Requirements.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="appendix" id="appe-Consistent_Network_Device_Naming" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">Consistent Network Device Naming</h1></div></div></div><div class="para">
+ Fedora 17 provides consistent network device naming for network interfaces. This feature changes the name of network interfaces on a system in order to make locating and differentiating the interfaces easier.
+ </div><div class="para">
+ Traditionally, network interfaces in Linux are enumerated as <code class="interfacename">eth[0123…]</code>, but these names do not necessarily correspond to actual labels on the chassis. Modern server platforms with multiple network adapters can encounter non-deterministic and counter-intuitive naming of these interfaces. This affects both network adapters embedded on the motherboard (<em class="firstterm">Lan-on-Motherboard</em>, or <em class="firstterm"><acronym class="acronym">LOM</acronym></em>) and add-in (single and multiport) adapters.
+ </div><div class="para">
+ The new naming convention assigns names to network interfaces based on their physical location, whether embedded or in PCI slots. By converting to this naming convention, system administrators will no longer have to guess at the physical location of a network port, or modify each system to rename them into some consistent order.
+ </div><div class="para">
+ This feature, implemented via the <span class="application"><strong>biosdevname</strong></span> program, will change the name of all embedded network interfaces, PCI card network interfaces, and virtual function network interfaces from the existing <code class="interfacename">eth[0123…]</code> to the new naming convention as shown in <a class="xref" href="appe-Consistent_Network_Device_Naming.html#tabl-Consistent_Network_Device_Naming">表A.1「The new naming convention」</a>.
+ </div><div class="table" id="tabl-Consistent_Network_Device_Naming"><h6>表A.1 The new naming convention</h6><div class="table-contents"><table summary="The new naming convention" border="1"><colgroup><col width="35%" class="device" /><col width="15%" class="old" /><col width="50%" class="new" /></colgroup><thead><tr><th class="">
+ デバイス（Device）
+ </th><th class="">
+ Old Name
+ </th><th class="">
+ New Name
+ </th></tr></thead><tbody><tr><td class="">
+ Embedded network interface (LOM)
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">em[1234…]</code><a href="#ftn.idm60928400" class="footnote"><sup class="footnote" id="idm60928400">[a]</sup></a>
+ </td></tr><tr><td class="">
+ PCI card network interface
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">p<<em class="replaceable"><code>slot</code></em>>p<<em class="replaceable"><code>ethernet port</code></em>></code><a href="#ftn.idm66546528" class="footnote"><sup class="footnote" id="idm66546528">[b]</sup></a>
+ </td></tr><tr><td class="">
+ Virtual function
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">p<<em class="replaceable"><code>slot</code></em>>p<<em class="replaceable"><code>ethernet port</code></em>>_<<em class="replaceable"><code>virtual interface</code></em>></code><a href="#ftn.idm48642656" class="footnote"><sup class="footnote" id="idm48642656">[c]</sup></a>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div id="ftn.idm60928400" class="footnote"><div class="para"><a href="#idm60928400" class="para"><sup class="para">[a] </sup></a>
+ New enumeration starts at <code class="literal">1</code>.
+ </div></div><div id="ftn.idm66546528" class="footnote"><div class="para"><a href="#idm66546528" class="para"><sup class="para">[b] </sup></a>
+ For example: <code class="interfacename">p3p4</code>
+ </div></div><div id="ftn.idm48642656" class="footnote"><div class="para"><a href="#idm48642656" class="para"><sup class="para">[c] </sup></a>
+ For example: <code class="interfacename">p3p4_1</code>
+ </div></div></td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ System administrators may continue to write rules in <code class="filename">/etc/udev/rules.d/70-persistent-net.rules</code> to change the device names to anything desired; those will take precedence over this physical location naming convention.
+ </div><div class="section" id="sect-Consistent_Network_Device_Naming-Affected_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.1. Affected Systems</h2></div></div></div><div class="para">
+ Consistent network device naming is enabled by default for all systems that meet the requirements in <a class="xref" href="sect-Consistent_Network_Device_Naming-System_Requirements.html">「システム要求」</a>.
+ </div><div class="para">
+ Regardless of the type of system, Fedora guests will not have devices renamed unless the virtual machine BIOS provides the SMBIOS information outlined in <a class="xref" href="sect-Consistent_Network_Device_Naming-System_Requirements.html">「システム要求」</a>. Also, upgrades from prior releases that did not use this naming convention (that is, Fedora 14 and older) are unaffected, and the old naming convention will continue to be used.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-resources-online.html"><strong>戻る</strong>23.4.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="sect-Consistent_Network_Device_Naming-System_Requirements.html"><strong>次へ</strong>A.2. システム要求</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Automating_System_Tasks.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Automating_System_Tasks.html
new file mode 100644
index 0000000..be9938b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Automating_System_Tasks.html
@@ -0,0 +1,146 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Monitoring_and_Automation.html" title="パート VI. 監視および自動化" /><link rel="prev" href="s2-log-files-useful-websites.html" title="18.6.2. 役に立つ Web サイト" /><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="s2-log-files-usefu
l-websites.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><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#s2-autotasks-cron-service">19.1.1. サービスの起動と停止</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">19.1.2. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">19.1.3. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="ch-A
utomating_System_Tasks.html#s2-autotasks-cron-access">19.1.4. Cron へのアクセスの制御</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">19.1.5. Black/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#s2-autotasks-at-configuring">19.2.1. At ジョブの設定</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">19.2.2. batch ジョブの設定</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">19.2.3. 保留ジョブの表示</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">19.2.4. その他のコマンドラインオプション</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-c
ontrolling-access.html">19.2.5. at と batch へのアクセスの制御</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-service.html">19.2.6. サービスの起動と停止</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">19.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">19.3.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a id="idm46938096" class="indexterm"></a><div class="para">
+ In Linux, tasks, which are 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 is below a specified number. Fedora is pre-configured to run important system tasks to keep the system updated. For example, the slocate 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 more.
+ </div><div class="para">
+ Fedora comes with several automated tasks utilities: <code class="command">cron</code>, <code class="command">at</code>, and <code class="command">batch</code>.
+ </div><a id="idm20493360" class="indexterm"></a><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="idm56931744" class="indexterm"></a><a id="idm73444336" class="indexterm"></a><div class="para">
+ Both, Cron and Anacron, are daemons that can be used to schedule the execution of recurring tasks according to a combination of the time, day of the month, month, day of the week, and week.
+ </div><div class="para">
+ Cron assumes that the system is on continuously. If the system is not on when a job is scheduled, it is not executed. Cron allows jobs to be run as often as every minute. Anacron does not assume the system is always on, remembers every scheduled job, and executes it the next time the system is up. However, Anacron can only run a job once a day. To schedule recurring jobs, refer to <a class="xref" href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">「Configuring Anacron Jobs」</a> or <a class="xref" href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">「Configuring Cron Jobs」</a>. To schedule one-time jobs, refer to <a class="xref" href="s1-autotasks-at-batch.html">「at コマンドと batch コマンド」</a>.
+ </div><div class="para">
+ To use the cron service, the <code class="filename">cronie</code> RPM package must be installed and the <code class="command">crond</code> service must be running. <code class="filename">anacron</code> is a sub-package of <code class="filename">cronie</code>. To determine if these packages are installed, use the <code class="command">rpm -q cronie cronie-anacron</code> command.
+ </div><div class="section" id="s2-autotasks-cron-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.1.1. サービスの起動と停止</h3></div></div></div><div class="para">
+ To determine if the service is running, use the following command:
+ </div><pre class="screen"><code class="command">systemctl is-active crond.service</code></pre><div class="para">
+ To start the cron service, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl start crond.service</code></pre><div class="para">
+ To stop the service, run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl stop crond.service</code></pre><div class="para">
+ It is recommended that you start the service at boot time. To do so, use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl enable crond.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </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.2. Configuring Anacron Jobs</h3></div></div></div><a id="idm48024304" class="indexterm"></a><a id="idm48022704" class="indexterm"></a><a id="idm43765952" class="indexterm"></a><a id="idm43764320" class="indexterm"></a><div class="para">
+ The main configuration file to schedule jobs is <code class="filename">/etc/anacrontab</code> (only <code class="systemitem">root</code> is allowed to modify this file), which contains the following lines:
+ </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
+ at monthly 45 cron.monthly nice run-parts /etc/cron.monthly</pre><div class="para">
+ The first three lines are variables used to configure the environment in which the anacron tasks are run. The <code class="computeroutput">SHELL</code> variable tells the system which shell environment to use (in this example the bash shell). The <code class="computeroutput">PATH</code> variable defines the path used to execute commands. The output of the anacron jobs are emailed to the username defined with the <code class="computeroutput">MAILTO</code> variable. If the <code class="computeroutput">MAILTO</code> variable is not defined, (i.e. is empty, <code class="computeroutput">MAILTO=</code>), email is not sent.
+ </div><div class="para">
+ The next two lines are variables that modify the time for each scheduled job. The <code class="computeroutput">RANDOM_DELAY</code> variable denotes the maximum number of minutes that will be added to the <code class="filename">delay in minutes</code> variable which is specified for each job. The minimum delay value is set, by default, to 6 minutes. A <code class="computeroutput">RANDOM_DELAY</code> set to 12 would therefore add, randomly, between 6 and 12 minutes to the <code class="filename">delay in minutes</code> for each job in that particular anacrontab. <code class="computeroutput">RANDOM_DELAY</code> can also be set to a value below 6, or even 0. When set to 0, 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. The <code class="computeroutput">START_HOURS_RANGE</code> variable defines an interval (in hours) when scheduled jobs can be run. In case this time
interval is missed, for example, due to a power down, then scheduled jobs are not executed that day.
+ </div><div class="para">
+ The rest of the lines in the <code class="filename">/etc/anacrontab</code> file represent scheduled jobs and have the following format:
+ </div><pre class="programlisting">period in days delay in minutes job-identifier command</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">period in days</code> — specifies the frequency of execution of a job in days. This variable can be represented by an integer or a macro (<code class="computeroutput">@daily</code>, <code class="computeroutput">@weekly</code>, <code class="computeroutput">@monthly</code>), where <code class="computeroutput">@daily</code> denotes the same value as the integer 1, <code class="computeroutput">@weekly</code> the same as 7, and <code class="computeroutput">@monthly</code> specifies that the job is run once a month, independent on the length of the month.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">delay in minutes</code> — specifies the number of minutes anacron waits, if necessary, before executing a job. This variable is represented by an integer where 0 means no delay.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">job-identifier</code> — specifies a unique name of a job which is used in the log files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">command</code> — specifies the command to execute. The command can either be a command such as <code class="computeroutput">ls /proc >> /tmp/proc</code> or a command to execute 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.2.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
+ at 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. Thus, the first defined job will run anywhere between 16:26 and 16:50 every day. The command specified for this job will execute all present programs in the <code class="filename">/etc/cron.daily</code> directory (using the <code class="command">run-parts</code> script which takes a directory as a command-line argument and sequentially executes every program within that directory). The second specified job will be executed once a week and will execute the <code class="filename">weeklyjob.bash</code> script in the <code class="filename">/etc</code> directory. The third job is executed once a month and runs a command to write the contents of the <code class="filename">/proc</code> to the <code class="filename">/tmp/proc</code> file (e.g. <code class="computeroutput">ls /proc >> /tmp/proc</code>).
+ </div><div class="section" id="s3-disabling-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">19.1.2.1.1. Disabling Anacron</h5></div></div></div><div class="para">
+ In case your system is continuously on and you do not require anacron to run your scheduled jobs, you may uninstall the <code class="filename">cronie-anacron</code> package. Thus, you will be able to define jobs using crontabs only.
+ </div></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.3. Configuring Cron Jobs</h3></div></div></div><a id="idm16353472" class="indexterm"></a><a id="idm60678176" class="indexterm"></a><a id="idm60676544" class="indexterm"></a><a id="idm65265296" class="indexterm"></a><div class="para">
+ The configuration file to configure cron jobs, <code class="filename">/etc/crontab</code> (only <code class="systemitem">root</code> is allowed to modify this file), contains the following lines:
+ </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 command to be executed</pre><div class="para">
+ The first three lines contain the same variables as an <code class="filename">anacrontab</code> file, <code class="computeroutput">SHELL</code>, <code class="computeroutput">PATH</code> and <code class="computeroutput">MAILTO</code>. For more information about these variables, refer to <a class="xref" href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">「Configuring Anacron Jobs」</a>. The fourth line contains the <code class="computeroutput">HOME</code> variable. The <code class="computeroutput">HOME</code> variable can be used to set the home directory to use when executing commands or scripts.
+ </div><div class="para">
+ The rest of the lines in the <code class="filename">/etc/crontab</code> file represent scheduled jobs and have the following format:
+ </div><pre class="programlisting">minute hour day month day of week user command</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">minute</code> — any integer from 0 to 59
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">hour</code> — any integer from 0 to 23
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">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="computeroutput">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="computeroutput">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><li class="listitem"><div class="para">
+ <code class="computeroutput">user</code> — specifies the user under which the jobs are run
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">command</code> — the command to execute (the command can either be a command such as <code class="command">ls /proc >> /tmp/proc</code> or the command to execute a custom script)
+ </div></li></ul></div><div class="para">
+ 上記のいずれの値にも、アスタリスク （*） を使用すると、すべての有効な値が指定されます。たとえば、月の値にアスタリスクを使用すると、コマンドはその他の値による制約の範囲内で毎月実行されます。
+ </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 those four specific integers.
+ </div><div class="para">
+ The forward slash (/) can be used to specify step values. The value of an integer can be skipped within a range by following the range with <strong class="userinput"><code>/<em class="replaceable"><code>integer</code></em></code></strong>. For example, <strong class="userinput"><code>0-59/2</code></strong> can be used to define every other minute in the minute field. Step values can also be used with an asterisk. For instance, the value <strong class="userinput"><code>*/3</code></strong> can be used in the month field to run the task 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 by using the <code class="command">crontab</code> utility. All user-defined crontabs are stored in the <code class="filename">/var/spool/cron/</code> directory and are executed using the usernames of the users that created them. To create a crontab as a user, login as that user and type the command <code class="command">crontab -e</code> to edit the user's crontab using the editor specified by 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 username and written to the file <code class="filename">/var/spool/cron/<em class="replaceable"><code>username</code></em> </code>. To list the contents of your own personal crontab file, use the <code class="command">crontab -l</code> com
mand.
+ </div><div class="note"><div class="admonition_header"><h2>Do not specify a user</h2></div><div class="admonition"><div class="para">
+ When using the <code class="command">crontab</code> utility, there is no need to specify a user when defining a job.
+ </div></div></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 any changes. If any changes are found, they are loaded into memory. Thus, the daemon does not need to be restarted if an anacrontab or a crontab file is 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.4. Cron へのアクセスの制御</h3></div></div></div><div class="para">
+ The <code class="filename">/etc/cron.allow</code> and <code class="filename">/etc/cron.deny</code> files are used to restrict access to cron. The format of both access control files is one username on each line. Whitespace is not permitted in either file. The cron daemon (<code class="command">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 usernames listed in the access control files.
+ </div><div class="para">
+ If the file <code class="filename">cron.allow</code> exists, only users listed in it are allowed to use cron, and the <code class="filename">cron.deny</code> file is ignored.
+ </div><div class="para">
+ If <code class="filename">cron.allow</code> does not exist, users listed in <code class="filename">cron.deny</code> are not allowed to use cron.
+ </div><div class="para">
+ Access can also be controlled through Pluggable Authentication Modules (PAM). These settings are stored in <code class="filename">/etc/security/access.conf</code>. For example, adding the following line in this file forbids creating crontabs for all users except the <code class="systemitem">root</code> user:
+ </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 “crontab -e”, returned to the standard output. For more information, refer to <code class="filename">access.conf.5</code> (i.e. <code class="command">man 5 access.conf</code>).
+ </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.5. Black/White Listing of Cron Jobs</h3></div></div></div><div class="para">
+ Black/White listing of jobs is used to omit parts of the defined jobs that do not need to be executed. When calling the <code class="command">run-parts</code> script on a cron folder, such as <code class="filename">/etc/cron.daily</code>, we can define which of the programs in this folder will not be executed by <code class="command">run-parts</code>.
+ </div><div class="para">
+ To define a black list, create a <code class="filename">jobs.deny</code> file in the folder that <code class="command">run-parts</code> will be executing from. For example, if we need to omit a particular program from /etc/cron.daily, then, a file <code class="filename">/etc/cron.daily/jobs.deny</code> has to be created. In this file, specify the names of the omitted programs from the same directory. These will not be executed when a command, such as <code class="computeroutput">run-parts /etc/cron.daily</code>, is executed by a specific job.
+ </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="s2-log-files-useful-websites.html"><strong>戻る</strong>18.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="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/17/html/System_Administrators_Guide/ch-Configuring_Authentication.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Configuring_Authentication.html
new file mode 100644
index 0000000..7dd2c4f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Configuring_Authentication.html
@@ -0,0 +1,428 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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章 認証の設定</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Infrastructure_Services.html" title="パート IV. インフラストラクチャーサービス" /><link rel="prev" href="s2-services-additional-resources-books.html" title="8.3.2. 関連書籍" /><link rel="next" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesske
y="p" href="s2-services-additional-resources-books.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Introduction.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="chapter" id="ch-Configuring_Authentication" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第9章 認証の設定</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">9.1. 認証の設定ツール</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">9.1.1. 識別と認証</a></span></dt><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">9.1.2. 高度なオプション</a></span></dt><dt><span class="section"><a href="ch-Configuring_Auth
entication.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">9.1.3. コマンドライン版</a></span></dt></dl></dd><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">9.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html#sect-SSSD_User_Guide-Introduction-What_is_SSSD">9.2.1. SSIDとは?</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html">9.2.2. SSIDの特徴</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Setting_Up_SSSD.html">9.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Services.html">9.2.4. サービスの設定</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Domains.html">9.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-C
onfiguring_Domains-Setting_up_Kerberos_Authentication.html">9.2.6. Setting Up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html">9.2.7. Configuring a Proxy Domain</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Troubleshooting.html">9.2.8. トラブルシューティング</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">9.2.9. SSSD Configuration File Format</a></span></dt></dl></dd></dl></div><div class="section" id="sect-The_Authentication_Configuration_Tool"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.1. 認証の設定ツール</h2></div></div></div><a id="idm39595296" class="indexterm"></a><a id="idm39596896" class="indexterm"></a><div class="para">
+ ユーザーが Fedora システムにログインするとき、ユーザー名とパスワードの組み合わせが有効かつアクティブなユーザーとして検証または<em class="firstterm">認証</em>されなければいけません。ときどき、ユーザーを検証するための情報はローカルシステムに置かれます。それ以外の場合、システムは認証をリモートシステムにあるユーザーデータベースに従います。
+ </div><div class="para">
+ <span class="application"><strong>認証の設定ツール</strong></span>は、<em class="firstterm">Lightweight Directory Access Protocol</em> (LDAP), <em class="firstterm"> Network Information Service</em> (NIS), および <em class="firstterm">Winbind</em> ユーザーアカウントデータベースから取り出したユーザー情報を設定するためのグラフィカルインターフェースを提供します。このツールは LDAP または NIS を使用しているとき、認証プロトコルとして Kerberos を使用するようにも設定できます。
+ </div><div class="note"><div class="admonition_header"><h2>中高セキュリティレベルの使用</h2></div><div class="admonition"><div class="para">
+ インストール中に中間または高セキュリティレベルを設定すると (または<span class="application"><strong>セキュリティレベル設定ツール</strong></span>)、ファイアウォールが NIS 認証を妨害します。ファイアウォールに関する詳細は、Fedora 17 <em class="citetitle">セキュリティガイド</em> の <em class="citetitle">"ファイアウォール"</em> セクションを参照してください。
+ </div></div></div><a id="idm55430864" class="indexterm"></a><a id="idm55432624" class="indexterm"></a><div class="para">
+ デスクトップから<span class="application"><strong>認証の設定</strong></span>のグラフィカル版を起動するには、<span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>その他</strong></span> → <span class="guimenuitem"><strong>認証</strong></span>を選択します、または（たとえば <span class="application"><strong>XTerm</strong></span> や <span class="application"><strong>GNOME</strong></span> 端末において）シェルプロンプトにコマンド <code class="command">system-config-authentication</code> を入力します。
+ </div><div class="important"><div class="admonition_header"><h2>変更は即座に適用されます</h2></div><div class="admonition"><div class="para">
+ 認証プログラムを終了した後、あらゆる変更は即座に反映されます。
+ </div></div></div><div class="section" id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.1. 識別と認証</h3></div></div></div><div class="para">
+ <span class="guilabel"><strong>識別と認証</strong></span>タブにより、どのようにユーザーが認証されるかを設定できます。また、それぞれの認証方式に対するいくつかのオプションがあります。どのユーザーアカウントデータベースが使用されるべきかを選択するには、ドロップダウンリストからオプションを選択します。
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject" align="center" id="mediaobj-authconfig_LDAP_kerb"><img src="images/authconfig_LDAP_kerb.png" align="middle" alt="識別と認証：ユーザーアカウントデータベースのドロップダウンにおいてオプションを変更すると、タブの内容が変更されます" /></div></div><h6>図9.1 識別と認証：ユーザーアカウントデータベースのドロップダウンにおいてオプションを変更すると、タブの内容が変更されます</h6></div><br class="figure-break" /><div class="para">
+ 以下の一覧は各オプションの説明です。
+ </div><h4 id="idm46803744">LDAP</h4><a id="idm46804272" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>LDAP</strong></span> オプションはシステムが LDAP 経由でユーザー情報を取得するよう指示します。以下の指定を含みます:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP 検索のベース DN</strong></span> — ユーザー情報が一覧化された識別名 (DN: Distinguished Name) を使用して取得されるよう指定します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP Server</strong></span> — <code class="systemitem">LDAP</code> サーバーのアドレスを指定します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>暗号化通信のために TLS を使用する</strong></span> — 有効になっているとき、<code class="systemitem">LDAP</code> サーバーに送信されるパスワードを暗号化するために <code class="systemitem">Transport Layer Security</code> (TLS) が使用されます。<span class="guibutton"><strong>CA 証明書のダウンロード</strong></span> オプションにより、有効な <em class="firstterm">認証局の証明書</em> (CA: Certificate Authority) をダウンロードする URL を指定できます。有効な CA 証明書は <em class="firstterm">Privacy Enhanced Mail</em> (PEM) 形式である必要があります。
+ </div><div class="important"><div class="admonition_header"><h2>LDAP サーバー項目における ldaps:// の使用法</h2></div><div class="admonition"><div class="para">
+ <code class="systemitem">ldaps://</code> サーバーアドレスが <span class="guilabel"><strong>LDAP サーバー</strong></span> の項目に指定されていると、<span class="guilabel"><strong>暗号化通信のために TLS を使用する</strong></span>オプションをチェックする必要がありません。
+ </div></div></div><div class="para">
+ CA 証明書の詳細は<a class="xref" href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">「証明書とセキュリティの概要」</a>を参照してください。
+ </div></li></ul></div><div class="para">
+ <code class="filename">openldap-clients</code> パッケージはこのオプションが機能するためにインストールする必要があります。
+ </div><div class="para">
+ LDAP の詳細は<a class="xref" href="ch-Directory_Servers.html#s1-OpenLDAP">「OpenLDAP」</a>を参照してください。
+ </div><div class="para">
+ LDAP は次の認証方法を提供します。
+ </div><div class="itemizedlist"><ul><li class="listitem"><a id="idm47566208" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Kerberos パスワード</strong></span> — このオプションは Kerberos 認証を有効にします。以下の指定を含みます:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>レルム</strong></span> — Kerberos サーバーのレルムを設定します。レルムは Kerberos を使用するネットワークです。一つかそれ以上の KDC および潜在的に大規模なクライアントから構成されます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>KDC</strong></span> — 鍵配布センター (KDC: Key Distribution Centers) を定義します、これは Kerberos チケットを発行するサーバーです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>管理サーバー</strong></span> — <code class="command">kadmind</code> を実行して管理サーバーを指定します。
+ </div></li></ul></div>
+
+ </div><div class="para">
+ <span class="guimenu"><strong>Kerberos 設定</strong></span> ダイアログにより、ホストをレルムに名前解決するため、およびレルムに対する KDC の位置を決めるために、DNS を使用できます。
+ </div><div class="para">
+ このオプションが動作するためには <code class="filename">krb5-libs</code> および <code class="filename">krb5-workstation</code> パッケージがインストールされている必要があります。Kerberos の詳細は、Fedora 17 <em class="citetitle">Managing Single Sign-On and Smart Cards</em> ガイドのセクション <em class="citetitle">Using Kerberos</em> を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP パスワード</strong></span> — このオプションにより、標準的な PAM 対応アプリケーションが LDAP のユーザーアカウント設定において指定されたオプションを用いて LDAP 認証を使用するよう指示します。このオプションを使用するとき、 <code class="systemitem">ldaps://</code> サーバーアドレスを提供する、または LDAP 認証の TLS をしようする必要があります。
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>SSSD サービスの設定</h2></div><div class="admonition"><div class="para">
+ SSSD サービスが LDAP および Kerberos サーバーに対するクライアントとして使用されます。このように、オフラインログインが有効化され、標準でサポートされます。ユーザーの対話が <span class="application"><strong>認証設定ツール</strong></span> で SSSD サービスをセットアップする必要がありません。SSSD サービスに関する詳細は<a class="xref" href="chap-SSSD_User_Guide-Introduction.html">「The System Security Services Daemon (SSSD)」</a>を参照してください。
+ </div></div></div><h4 id="idm20564752">NIS</h4><a id="idm58034320" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>NIS</strong></span> オプションは、ユーザーとパスワードの認証のために NIS サーバーに (NIS クライアント) として接続するよう、システムを設定します。このオプションを設定するには、NIS ドメインと NIS サーバーを指定します。NIS サーバーが指定されていないと、デーモンがブロードキャストにより発見しようとします。
+ </div><div class="para">
+ <span class="package">ypbind</span> パッケージがこのオプションの正常動作のためにインストールされている必要があります。NIS ユーザーアカウントデータベースが使用されていると、<code class="systemitem">portmap</code> および <code class="systemitem">ypbind</code> サービスが起動され、ブート時の起動を有効化する必要があります。
+ </div><div class="para">
+ NIS の詳細は、Fedora <em class="citetitle">セキュリティガイド</em> のセクション <em class="citetitle">"NIS のセキュア化"</em> を参照してください。
+ </div><div class="para">
+ NIS は次の認証方法を提供します。
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Kerberos パスワード</strong></span> — このオプションにより Kerberos 認証が有効化されます。Kerberos 認証方法の設定に関する詳細は、LDAP に関する前のセクションを参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <a id="idm58029824" class="indexterm"></a>
+ <span class="guilabel"><strong>NIS パスワード</strong></span> — このオプションは NIS 認証を有効にします。NIS はユーザーを認証するために認証情報を外部のプロセスに提供できます。
+ </div></li></ul></div><h4 id="idm58032832">Winbind</h4><a id="idm58033520" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Winbind</strong></span> オプションはシステムが Windows Active Directory または Windows ドメインコントローラーに接続するよう設定します。指定されたディレクトリーまたはドメインコントローラーからのユーザー情報がアクセスされます。また、サーバー認証オプションが設定できます。以下の仕様が含まれます:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind ドメイン</strong></span> — 接続する Windows Active Directory またはドメインコントローラーを指定します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>セキュリティモデル</strong></span> — Samba クライアントの動作モードを設定する、セキュリティモデルを選択できます。ドロップダウンリストは、以下のどれかを選択できます:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ads</strong></span> — このモードは Active Directory Server (ADS) レルムにおいてドメインメンバーとして動作するよう Samba に指示します。このモードにおいて動作するには、<code class="filename">krb5-server</code> パッケージがインストールされている必要があります。また、Kerberos が正しく設定されている必要があります。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>domain</strong></span> — このモードでは、Windows NT サーバーと同じように、Samba は Windows NT プライマリまたはバックアップドメインコントローラーを通して認証することにより、ユーザー名とパスワードを検証しようとします。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>server</strong></span> — このモードでは、Samba は他の SMB サーバー (たとえば、Windows NT Server) を通して認証することにより、ユーザー名・パスワードを検証しようとします。これに失敗すると、代わりに <span class="guilabel"><strong>user</strong></span> モードが効果を持ちます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>user</strong></span> — これが標準のモードです。このレベルのセキュリティを用いると、クライアントはまず有効なユーザー名とパスワードでログインします。暗号化されたパスワードはこのセキュリティモードにおいても使用できます。
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind ADS Realm</strong></span> — <span class="guilabel"><strong>ads</strong></span> セキュリティモデルが選択されたとき、Samba サーバーがドメインのメンバーとして動作する ADS レルムを指定できます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind Domain Controllers</strong></span> — <code class="command">winbind</code> が使用するドメインコントローラーを指定するために、このオプションを使用します。ドメインコントローラーに関する詳細は、<a class="xref" href="ch-File_and_Print_Servers.html#s3-samba-domain-controller">「Domain Controller」</a>を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>テンプレートシェル</strong></span> — Windows NT ユーザーの情報を記入するとき、<code class="command">winbindd</code> デーモンがユーザーのログインシェルを指定するために、ここで選択された値を使用します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>オフラインログインを許可する</strong></span> — このオプションをチェックすることにより、認証情報を (SSSD により提供される) ローカルキャッシュに保存できるようになります。オフラインの間にユーザーが認証を試行したときに、この情報が使用されます。
+ </div></li></ul></div><div class="para">
+ <code class="command">winbindd</code> サービスに関する詳細は <a class="xref" href="ch-File_and_Print_Servers.html#s2-samba-daemons">「Samba デーモンと関連サービス」</a> を参照してください。
+ </div><a id="idm69466816" class="indexterm"></a><div class="para">
+ Winbind は一つの認証方式 <span class="guilabel"><strong>Winbind パスワード</strong></span>のみを提供します。この方式の認証は、Windows Active Directory または Windows ドメインコントローラーに接続するために、Winbind のユーザーアカウント設定において指定されたオプションを使用します。
+ </div></div><div class="section" id="sect-The_Authentication_Configuration_Tool-Advanced_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.2. 高度なオプション</h3></div></div></div><div class="para">
+ このタブにより、以下にあるような高度なオプションを設定できます。
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject" align="center" id="mediaobj-authconfig_advanced"><img src="images/authconfig_advanced.png" align="middle" width="444" alt="高度なオプション" /></div></div><h6>図9.2 高度なオプション</h6></div><br class="figure-break" /><h4 id="idm69475040">ローカルの認証オプション</h4><div class="itemizedlist"><ul><li class="listitem"><a id="idm62001216" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>指紋読み取り装置のサポートの有効化</strong></span> — このオプションをチェックすることにより、指紋読み取り装置を用いて指紋を読み取ることによりログインするために、指紋認証を有効化します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ローカルアクセス制御を有効化する</strong></span> — 有効にされたとき、ユーザーの認証のために <code class="filename">/etc/security/access.conf</code> が参照されます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>パスワードハッシュ化アルゴリズム</strong></span> — このオプションにより、ローカルに保存されるパスワードを暗号化するために使用されるハッシュ化または暗号化アルゴリズムを指定できます。
+ </div></li></ul></div><h4 id="idm62009056">その他の認証オプション</h4><div class="para">
+ <span class="guilabel"><strong>初回ログイン時にホームディレクトリーを作成する</strong></span> — 有効にされているとき、ユーザーがログインしたときにホームディレクトリーが存在しないと、自動的に作成されます。
+ </div><h4 id="idm62011104">スマート カードの認証オプション</h4><a id="idm62011632" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>スマートカードのサポートの有効化</strong></span> — このオプションによりスマートカード認証が有効化されます。スマートカード認証により、スマートカードと関連した証明書およびキーを使用してログインできます。
+ </div><div class="para">
+ <span class="guilabel"><strong>スマートカードのサポートの有効化</strong></span> オプションがチェックされているとき、以下のオプションが指定できます:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>カード抜き取り動作</strong></span> — このオプションは、カードが有効な間にカードリーダーから抜き取られたときに、システムが実行する動作を定義します。2 つの代替が利用可能です:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Ignore</strong></span> — カードの取り出しが無視され、システムは通常どおり動作し続けます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Lock</strong></span> — 現在のセッションがただちにロックされます。
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>スマートカードログインの要求</strong></span> — ユーザーにスマートカードを用いたログインと認証をするよう要求します。本質的に他の種類のパスワード認証を無効化します。このオプションは、スマートカードを使用して正常にログインした後、選択されません。
+ </div></li></ul></div>
+
+ </div><div class="para">
+ <span class="package">pam_pkcs11</span> および <span class="package">coolkey</span> パッケージはこのオプションが機能するためにインストールされている必要があります。スマートカードに関する詳細は Red Hat Enterprise Linux 6 <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Managing_Smart_Cards/enabling-smart-card-login.html">Managing Single Sign-On and Smart Cards Guide</a> を参照してください。
+ <div class="note"><div class="admonition_header"><h2>前の設定を復元するには Revert をクリックする</h2></div><div class="admonition"><div class="para">
+ <span class="guibutton"><strong>復元</strong></span>をクリックすることにより、<span class="application"><strong>認証設定ツール</strong></span>において指定されたオプションを前に設定した内容にすべて復元できます。
+ </div></div></div>
+
+ </div></div><div class="section" id="sect-The_Authentication_Configuration_Tool-Command_Line_Version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.3. コマンドライン版</h3></div></div></div><a id="idm28152864" class="indexterm"></a><div class="para">
+ <span class="application"><strong>認証設定</strong></span>ツールはコマンドラインインターフェースもサポートします。コマンドラインのバージョンは、設定スクリプトまたは kickstart スクリプトにおいて使用できます。認証オプションは<a class="xref" href="ch-Configuring_Authentication.html#tb-authconfig-cmd-line">表9.1「コマンドラインのオプション」</a>にまとめられています。
+ </div><div class="note"><div class="admonition_header"><h2>サポートされる認証オプションの一覧取得方法</h2></div><div class="admonition"><div class="para">
+ これらのオプションは、<code class="command">authconfig</code> マニュアルページ、またはシェルプロンプトにおいて <code class="command">authconfig --help</code> と入力することにより、参照できます。
+ </div></div></div><div class="table" id="tb-authconfig-cmd-line"><h6>表9.1 コマンドラインのオプション</h6><div class="table-contents"><table summary="コマンドラインのオプション" border="1"><colgroup><col width="60%" class="option" /><col width="40%" class="description" /></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">--enableshadow, --useshadow</code>
+ </td><td class="">
+ シャドウパスワードを有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disableshadow</code>
+ </td><td class="">
+ シャドウパスワードを解除する
+ </td></tr><tr><td class="">
+ <code class="command">--passalgo=<em class="replaceable"><code>descrypt|bigcrypt|md5|sha256|sha512</code></em></code>
+ </td><td class="">
+ 使用されるハッシュ/暗号アルゴリズム
+ </td></tr><tr><td class="">
+ <code class="command">--enablenis</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの NIS を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablenis</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの NIS を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--nisdomain=<em class="replaceable"><code>domain</code></em> </code>
+ </td><td class="">
+ NIS ドメインを指定する
+ </td></tr><tr><td class="">
+ <code class="command">--nisserver=<em class="replaceable"><code>server</code></em> </code>
+ </td><td class="">
+ NIS サーバーを指定する
+ </td></tr><tr><td class="">
+ <code class="command">--enableldap</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの LDAP を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disableldap</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの LDAP を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enableldaptls</code>
+ </td><td class="">
+ LDAP で TLS の使用を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disableldaptls</code>
+ </td><td class="">
+ LDAP で TLS の使用を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablerfc2307bis</code>
+ </td><td class="">
+ LDAP ユーザー情報の検索のために RFC-2307bis スキーマの使用を有効にします
+ </td></tr><tr><td class="">
+ <code class="command">--disablerfc2307bis</code>
+ </td><td class="">
+ LDAP ユーザー情報の検索のために RFC-2307bis スキーマの使用を無効にします
+ </td></tr><tr><td class="">
+ <code class="command">--enableldapauth</code>
+ </td><td class="">
+ 認証の LDAP を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disableldapauth</code>
+ </td><td class="">
+ 認証の LDAP を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--ldapserver=<em class="replaceable"><code>server</code></em> </code>
+ </td><td class="">
+ LDAP サーバーを指定する
+ </td></tr><tr><td class="">
+ <code class="command">--ldapbasedn=<em class="replaceable"><code>dn</code></em> </code>
+ </td><td class="">
+ LDAP ベース DN (Distinguished Name) を指定します
+ </td></tr><tr><td class="">
+ <code class="command">--ldaploadcacert=<em class="replaceable"><code>URL</code></em> </code>
+ </td><td class="">
+ 指定された CA 証明書を読み込みます
+ </td></tr><tr><td class="">
+ <code class="command">--enablekrb5</code>
+ </td><td class="">
+ 認証のために Kerberos を有効にします
+ </td></tr><tr><td class="">
+ <code class="command">--disablekrb5</code>
+ </td><td class="">
+ 認証のために Kerberos を無効にします
+ </td></tr><tr><td class="">
+ <code class="command">--krb5kdc=<em class="replaceable"><code>server</code></em> </code>
+ </td><td class="">
+ Kerberos KDC サーバーを指定します
+ </td></tr><tr><td class="">
+ <code class="command">--krb5adminserver=<em class="replaceable"><code>server</code></em> </code>
+ </td><td class="">
+ Kerberos の管理サーバーを指定する
+ </td></tr><tr><td class="">
+ <code class="command">--krb5realm=<em class="replaceable"><code>realm</code></em> </code>
+ </td><td class="">
+ Kerberos の realm を指定する
+ </td></tr><tr><td class="">
+ <code class="command">--enablekrb5kdcdns</code>
+ </td><td class="">
+ Kerberos KDC の検索に DNS の使用を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablekrb5kdcdns</code>
+ </td><td class="">
+ Kerberos KDC の検索に DNS の使用を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablekrb5realmdns</code>
+ </td><td class="">
+ Kerberos realm の検索に DNS の使用を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablekrb5realmdns</code>
+ </td><td class="">
+ Kerberos realm の検索に DNS の使用を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablewinbind</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの winbind を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablewinbind</code>
+ </td><td class="">
+ ユーザー アカウント設定向けの winbind を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablewinbindauth</code>
+ </td><td class="">
+ 認証で winbindauth を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablewinbindauth</code>
+ </td><td class="">
+ 認証で winbindauth を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--winbindseparator=<em class="replaceable"><code>\</code></em> </code>
+ </td><td class="">
+ <code class="command">winbindusedefaultdomain</code> が有効になっていない場合に、winbind ユーザー名のドメイン部分とユーザー部分を分離するために使用する文字です
+ </td></tr><tr><td class="">
+ <code class="command">--winbindtemplatehomedir=<em class="replaceable"><code>/home/%D/%U</code></em> </code>
+ </td><td class="">
+ winbind ユーザーがホームとするディレクトリ
+ </td></tr><tr><td class="">
+ <code class="command">--winbindtemplateprimarygroup=<em class="replaceable"><code>nobody</code></em> </code>
+ </td><td class="">
+ winbind ユーザーが最初のグループとするグループ
+ </td></tr><tr><td class="">
+ <code class="command">--winbindtemplateshell=<em class="replaceable"><code>/bin/false</code></em> </code>
+ </td><td class="">
+ winbind ユーザーがログインシェルの初期値とするシェル
+ </td></tr><tr><td class="">
+ <code class="command">--enablewinbindusedefaultdomain</code>
+ </td><td class="">
+ ユーザー名にドメインのないユーザーはドメイン ユーザーであると winbind に仮定させる
+ </td></tr><tr><td class="">
+ <code class="command">--disablewinbindusedefaultdomain</code>
+ </td><td class="">
+ ユーザー名にドメインのないユーザーはドメイン ユーザーではないと winbind に仮定させる
+ </td></tr><tr><td class="">
+ <code class="command">--winbindjoin=<em class="replaceable"><code>Administrator</code></em> </code>
+ </td><td class="">
+ 指定された管理者として winbind ドメインまたは ADS レルムに参加します。
+ </td></tr><tr><td class="">
+ <code class="command">--enablewinbindoffline</code>
+ </td><td class="">
+ オフライン ログインを許可する winbind の設定
+ </td></tr><tr><td class="">
+ <code class="command">--disablewinbindoffline</code>
+ </td><td class="">
+ オフライン ログインを防ぐ winbind の設定
+ </td></tr><tr><td class="">
+ <code class="command">--smbsecurity=<em class="replaceable"><code>user|server|domain|ads</code></em></code>
+ </td><td class="">
+ Samba および Winbind サービスに対して使用するセキュリティモードです
+ </td></tr><tr><td class="">
+ <code class="command">--smbrealm=<em class="replaceable"><code>realm</code></em></code>
+ </td><td class="">
+ <span class="guilabel"><strong>security</strong></span> が <span class="guimenuitem"><strong>ads</strong></span> に設定されているとき、Samba および Winbind サービスの初期レルムです。
+ </td></tr><tr><td class="">
+ <code class="command">--enablewins</code>
+ </td><td class="">
+ ホスト名解決で Wins を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablewins</code>
+ </td><td class="">
+ ホスト名解決で Wins を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablesssd</code>
+ </td><td class="">
+ ユーザー情報の SSSD を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablesssd</code>
+ </td><td class="">
+ ユーザー情報の SSSD を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablecache</code>
+ </td><td class="">
+ <code class="command">nscd</code> を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablecache</code>
+ </td><td class="">
+ <code class="command">nscd</code> を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablelocauthorize</code>
+ </td><td class="">
+ ローカル認証はローカルユーザーに対して十分です。
+ </td></tr><tr><td class="">
+ <code class="command">--disablelocauthorize</code>
+ </td><td class="">
+ ローカルユーザーはリモートサービスを用いても認証されます。
+ </td></tr><tr><td class="">
+ <code class="command">--enablesysnetauth</code>
+ </td><td class="">
+ ネットワーク サービスでシステム アカウントを認証する
+ </td></tr><tr><td class="">
+ <code class="command">--disablesysnetauth</code>
+ </td><td class="">
+ ローカルのファイルのみでシステム アカウントを認証する
+ </td></tr><tr><td class="">
+ <code class="command">--enablepamaccess</code>
+ </td><td class="">
+ アカウントの認可中に <code class="filename">/etc/security/access.conf</code> をチェックします
+ </td></tr><tr><td class="">
+ <code class="command">--disablepamaccess</code>
+ </td><td class="">
+ アカウント認可中に <code class="filename">/etc/security/access.conf</code> を確認しません
+ </td></tr><tr><td class="">
+ <code class="command">--enablemkhomedir</code>
+ </td><td class="">
+ 初回ログイン時にユーザーのホームディレクトリーを作成します
+ </td></tr><tr><td class="">
+ <code class="command">--disablemkhomedir</code>
+ </td><td class="">
+ 初回ログイン時にユーザーのホームディレクトリーを作成しません
+ </td></tr><tr><td class="">
+ <code class="command">--enablesmartcard</code>
+ </td><td class="">
+ スマートカードでの認証を有効にする
+ </td></tr><tr><td class="">
+ <code class="command">--disablesmartcard</code>
+ </td><td class="">
+ スマートカードでの認証を無効にする
+ </td></tr><tr><td class="">
+ <code class="command">--enablerequiresmartcard</code>
+ </td><td class="">
+ 認証にスマートカードを要求する
+ </td></tr><tr><td class="">
+ <code class="command">--disablerequiresmartcard</code>
+ </td><td class="">
+ 認証にスマートカードを要求しない
+ </td></tr><tr><td class="">
+ <code class="command">--smartcardmodule=<em class="replaceable"><code>module</code></em></code>
+ </td><td class="">
+ 標準でスマートカードを使う
+ </td></tr><tr><td class="">
+ <code class="command">--smartcardaction=<em class="replaceable"><code>0=ロック|1=無視</code></em></code>
+ </td><td class="">
+ スマートカードの抜き取りを検知したときのアクションです
+ </td></tr><tr><td class="">
+ <code class="command">--enablefingerprint</code>
+ </td><td class="">
+ 指紋認証を有効にします
+ </td></tr><tr><td class="">
+ <code class="command">--disablefingerprint</code>
+ </td><td class="">
+ 指紋認証を無効にします
+ </td></tr><tr><td class="">
+ <code class="command">--nostart</code>
+ </td><td class="">
+ <code class="command">portmap</code>, <code class="command">ypbind</code>, または <code class="command">nscd</code> サービスが設定されているときでも、それらを開始または停止しません
+ </td></tr><tr><td class="">
+ <code class="command">--test</code>
+ </td><td class="">
+ 新しい設定の表示のみで設定ファイルの更新をしない
+ </td></tr><tr><td class="">
+ <code class="command">--update, --kickstart</code>
+ </td><td class="">
+ <code class="command">--test</code> と反対に、変更された設定で設定ファイルを更新します
+ </td></tr><tr><td class="">
+ <code class="command">--updateall</code>
+ </td><td class="">
+ 全設定ファイルを更新する
+ </td></tr><tr><td class="">
+ <code class="command">--probe</code>
+ </td><td class="">
+ ネットワークデフォルトを調査して表示する
+ </td></tr><tr><td class="">
+ <code class="command">--savebackup=<em class="replaceable"><code>name</code></em></code>
+ </td><td class="">
+ 全設定ファイルのバックアップを保存する
+ </td></tr><tr><td class="">
+ <code class="command">--restorebackup=<em class="replaceable"><code>name</code></em></code>
+ </td><td class="">
+ 全設定ファイルのバックアップを復元する
+ </td></tr><tr><td class="">
+ <code class="command">--restorelastbackup</code>
+ </td><td class="">
+ これまでの設定変更の前に保存された設定ファイルのバックアップを復元します
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-services-additional-resources-books.html"><strong>戻る</strong>8.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="chap-SSSD_User_Guide-Introduction.html"><strong>次へ</strong>9.2. The System Security Services Daemon (SSSD)</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html
new file mode 100644
index 0000000..b089727
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.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>第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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-Configuring_the_Language_and_Keyboard-System.html" title="1.4. 現在の設定の表示" /><link rel="next" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html" title="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="sect-Configuring_the_Language_and_Keyboard-System.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.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">第2章 日付と時刻の設定</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">2.1. 日付と時刻の設定ツールの使い方</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html">2.2. コマンドラインツールの使用</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html#sect-Configuring_the_Date_and_Tim
e-Command_Line_Configuration-Date">2.2.1. 日付の変更方法</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html">2.2.2. 時刻の変更方法</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html">2.2.3. Network Time Protocol の設定</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Additional_Resources.html">2.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Additional_Resources.html#sect-Configuring_the_Date_and_Time-Additional_Resources-Installed_Documentation">2.3.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><div class="para">
+ 本章は Fedora においてシステムの日付と時刻を設定することについて取り扱いします。手動による方法と Network Time Protocol (<abbr class="abbrev">NTP</abbr>) を用いる方法どちらもです。また、適切なタイムゾーンを設定することも取り扱います。どちらの方法も、<span class="application"><strong>日付と時刻</strong></span>の設定ツールを用いて日付と時刻を設定する方法と同じことをコマンドラインにおいて実行する方法を取り扱います。
+ </div><div class="section" id="sect-Configuring_the_Date_and_Time-Date_and_Time"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. 日付と時刻の設定ツールの使い方</h2></div></div></div><div class="para">
+ Fedora 17 ã¯<span class="application"><strong>日付ã¨æ™‚刻</strong></span>è¨å®šãƒ„ールをåŒæ¢±ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ã‚·ã‚¹ãƒ†ãƒ ã®æ—¥ä»˜ã¨æ™‚刻を変更ã™ã‚‹ã€ã‚·ã‚¹ãƒ†ãƒ ã«ã‚ˆã‚Šä½¿ç”¨ã•ã‚Œã‚‹ã‚¿ã‚¤ãƒ ゾーンをè¨å®šã™ã‚‹ã€ãŠã‚ˆã³æ™‚刻サーãƒãƒ¼ã¨ã‚·ã‚¹ãƒ†ãƒ クãƒãƒƒã‚¯ã‚’åŒæœŸã™ã‚‹ãŸã‚ã« NTP (Network Time Protocol) デーモンをセットアップã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ツールを起動ã™ã‚‹ã«ã¯ã€<span class="guimenu"><strong>アクティビティ</strong></span>メニューã‹ã‚‰<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>システムè¨å®š</strong></span>ã‚’é¸æŠžã—ã¦<span class="guimenuitem"><strong>日付ã¨æ™‚刻</strong></span>アイコンをé¸æŠžã™ã‚‹ã‹ã€ãƒ‰ãƒãƒƒãƒ—ダウンメニューã‹ã‚‰<span class="guibutton"><strong>日付ã¨æ™‚刻ã®è¨å®š</strong></span>ã‚’é
¸æŠžã—ã¾ã™ã€‚
+ </div><div class="figure" id="fig-Configuring_the_Date_and_Time-Date_and_Time"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-settings.png" alt="日付と時刻の設定ツール" /><div class="longdesc"><div class="para">
+ 日付と時刻の設定ツール
+ </div></div></div></div><h6>図2.1 日付と時刻の設定ツール</h6></div><br class="figure-break" /><div class="para">
+ デフォルトで、ツールは現在の設定を表示することのみできます。<code class="systemitem">root</code> のみがシステムの日付と時刻を設定できるからです。変更するために設定ツールをロック解除するには、ウィンドウの右上角にある<span class="guibutton"><strong>解除</strong></span>ボタンをクリックして、プロンプトが出たときに正しいパスワードを入力します。
+ </div><a id="idm31075392" class="indexterm"></a><a id="idm35154992" class="indexterm"></a><div class="para">
+ システムの現在の時刻を変更するには、<span class="guilabel"><strong>ネットワーク時刻</strong></span>スイッチをクリックすることによりネットワーク上で同期するようシステムを設定するか、または数字の上と下にある上下の矢印をクリックすることにより手動で設定します。24時間形式を有効または無効にするために、<span class="guilabel"><strong>24時間</strong></span>または <span class="guilabel"><strong>AM/PM</strong></span> を選択できます。
+ </div><a id="idm44208304" class="indexterm"></a><a id="idm44206736" class="indexterm"></a><div class="para">
+ タイムゾーンを変更するには、地図をクリックするか、<span class="guilabel"><strong>地域</strong></span>および<span class="guilabel"><strong>都市</strong></span>のドロップダウンリストから地域と都市を選択してください。
+ </div><a id="idm59289152" class="indexterm"></a><a id="idm59287552" class="indexterm"></a><div class="para">
+ システムの現在の日付を変更するには、時刻の下にあるドロップダウンリストから月を選択して、日と年を選択するために上下の矢印を使用します。
+ </div><div class="para">
+ この変更は直ちに反映されます。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Language_and_Keyboard-System.html"><strong>戻る</strong>1.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-Configuring_the_Date_and_Time-Command_Line_Configuration.html"><strong>次へ</strong>2.2. コマンドラインツールの使用</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Configuring_the_Language_and_Keyboard.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Configuring_the_Language_and_Keyboard.html
new file mode 100644
index 0000000..85b0441
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Configuring_the_Language_and_Keyboard.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>第1章 言語とキーボードの設定</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="sect-Configuring_the_Language_and_Keyboard-Formats.html" title="1.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-Basic_System_Configuration.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_the_Language_and_Keyboard-Formats.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="chapter" id="ch-Configuring_the_Language_and_Keyboard" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第1章 言語とキーボードの設定</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Configuring_the_Language_and_Keyboard.html#sect-Configuring_the_Language_and_Keyboard-Language">1.1. 言語の変更</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Language_and_Keyboard-Formats.html">1.2. 日付、時刻および数字の形式の変更</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Language_and_Keyboard-Layouts.html">1.3. キーボードのレイアウト変更</a></span></dt><dt><span class="section"><a
href="sect-Configuring_the_Language_and_Keyboard-System.html">1.4. 現在の設定の表示</a></span></dt></dl></div><div class="para">
+ Fedora 17 は<span class="application"><strong>地域と言語</strong></span>設定ツールを同梱しています。これは、キーボード配置、デスクトップ環境の言語、および他の地域の設定をできます。ツールを開始するには、<span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>システム設定</strong></span>を選択することにより<span class="application"><strong>システム設定</strong></span>ウィンドウを開き、<span class="guimenuitem"><strong>地域と言語</strong></span>をクリックします。
+ </div><div class="section" id="sect-Configuring_the_Language_and_Keyboard-Language"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. 言語の変更</h2></div></div></div><a id="idm42266240" class="indexterm"></a><a id="idm45396544" class="indexterm"></a><div class="para">
+ デスクトップの言語を設定するには、<span class="application"><strong>地域と言語</strong></span>アプリケーションの<span class="guilabel"><strong>言語</strong></span>タブを選択します。一般的な言語の簡単な一覧が表示されます。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Language"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-language.png" alt="言語の変更" /><div class="longdesc"><div class="para">
+ 言語の変更
+ </div></div></div></div><h6>図1.1 言語の変更</h6></div><br class="figure-break" /><div class="para">
+ デフォルトで、このリストはいくつかの利用可能な言語のみを含みます。他の言語を追加するには、リストの下にある <span class="guibutton"><strong>+</strong></span> (プラス記号) ボタンをクリックします。ダイアログウィンドウが表示され、希望する言語を選択できます。ダイアログウィンドウの下部にある入力フィールドを使用して、そこに言語名の最初の数文字を入力すると表示される言語を減らすことができるようになります（たとえば、スロバキア語には <span class="quote">「<span class="quote">slov</span>」</span> です）。言語を選択すると、選んだものを確認するために<span class="guibutton"><strong>選択</strong></span>ボタンをクリックします。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Language-Add"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-language-add.png" alt="他の言語の追加" /><div class="longdesc"><div class="para">
+ Adding a language
+ </div></div></div></div><h6>図1.2 他の言語の追加</h6></div><br class="figure-break" /><div class="para">
+ 一覧の中から特定の言語を選択するには、その名前をクリックします。変更は次回ログイン時に有効になります。
+ </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="sect-Configuring_the_Language_and_Keyboard-Formats.html"><strong>次へ</strong>1.2. 日付、時刻および数字の形式の変更</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-DHCP_Servers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-DHCP_Servers.html
new file mode 100644
index 0000000..fabd905
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-DHCP_Servers.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章 DHCP サーバー</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Servers.html" title="パート V. サーバー" /><link rel="prev" href="part-Servers.html" title="パート V. サーバー" /><link rel="next" href="s1-dhcp-configuring-server.html" title="11.2. DHCP サーバーの設定" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accessk
ey="n" href="s1-dhcp-configuring-server.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="chapter" id="ch-DHCP_Servers" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第11章 DHCP サーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-DHCP_Servers.html#s1-dhcp-why">11.1. DHCP を使用する理由</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">11.2. DHCP サーバーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-configuring-server.html#config-file">11.2.1. 設定ファイル</a></span></dt><dt><span class="section"><a href="lease-database.html">11.2.2. リースデータベース</a></span></dt><dt><span class="section"><a href="ch11s02s03.html">11.2.3. サーバーの起動と停止</a></span></dt><dt><span class="section"><a href="dhcp-relay-agent.html">11.2.4. DHCP リレーエージェント</a></span></dt></dl></dd><dt><span cla
ss="section"><a href="s1-dhcp-configuring-client.html">11.3. DHCP クライアントの設定</a></span></dt><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html">11.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configuration">11.4.1. ホストの設定</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">11.5. IPv6 向け DHCP (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">11.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">11.6.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a id="idm55326128" class="indexterm"></a><a id="idm57378192" class="indexterm"></a><div class="para">
+ <acronym class="acronym">DHCP</acronym> (Dynamic Host Configuration Protocol) は、クライアントマシンに自動的に TCP/IP 情報を割り当てるネットワークプロトコルです。各 DHCP クライアントは、中央に配置された DHCP サーバーに接続し、このサーバーが IP アドレス、ゲートウェイ、 DNS サーバーなどクライアントのネットワーク設定情報 (IP アドレス、ゲートウェイ、 DNS サーバーを含む) を返します。
+ </div><div class="section" id="s1-dhcp-why"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.1. DHCP を使用する理由</h2></div></div></div><a id="idm45718816" class="indexterm"></a><div class="para">
+ DHCP はクライアントのネットワークインターフェースを自動で設定するのに便利です。クライアントシステムを設定するとき DHCP を選択すれば、 IP アドレス、ネットマスク、ゲートウェイ、 DNS サーバーを入力する必要がありません。クライアントはこれらの情報を DHCP サーバーから受け取ります。また、管理者が多数のシステムの IP アドレスを変更する場合も DHCP は便利です。すべてのシステムの再設定を行う代わりに、サーバー上の DHCP 設定ファイルを編集することによって、新規の IP アドレスセットを設定できます。組織の DNS サーバーが変更された場合は、 DHCP クライアントで変更を行うのではなく、 DHCP サーバーで変更を行います。クライアントでネットワークが再起動 （またはクライアントがリブート） されると、変
更が反映されます。
+ </div><div class="para">
+ 組織が、機能中の DHCP サーバーをネットワークに正しく接続している場合、ラップトップや他の携帯コンピュータの使用者はそのようなデバイスをオフィスからオフィスへと移動して使用できます。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Servers.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-dhcp-configuring-server.html"><strong>次へ</strong>11.2. DHCP サーバーの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-DNS_Servers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-DNS_Servers.html
new file mode 100644
index 0000000..b970040
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-DNS_Servers.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>第12章 DNS サーバー</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Servers.html" title="パート V. サーバー" /><link rel="prev" href="s1-dhcp-additional-resources.html" title="11.6. その他のリソース" /><link rel="next" href="s1-BIND.html" title="12.2. BIND" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-dhcp-additional-resources.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n"
href="s1-BIND.html"><strong>次ã¸</strong></a></li></ul><div xml:lang="ja-JP" class="chapter" id="ch-DNS_Servers" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第12ç« DNS サーãƒãƒ¼</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-DNS_Servers.html#s1-Introduction_to_DNS">12.1. DNS ã®æ¦‚è¦</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DNS_Servers.html#s2-dns-introduction-zones">12.1.1. ãƒãƒ¼ãƒ サーãƒãƒ¼ã‚¾ãƒ¼ãƒ³</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">12.1.2. ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚¤ãƒ—</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#s2-dns-introduction-bind">12.1.3. ãƒãƒ¼ãƒ サーãƒãƒ¼ã¨ã—ã¦ã® BIND</a></span></dt></dl></dd><dt><span class="section"><a href="s1-BIND.html">12.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="s1-BIND.html#s2-bind-namedconf">12.2.1. named サービスã®è¨å®
š</a></span></dt><dt><span class="section"><a href="s2-bind-zone.html">12.2.2. ゾーンファイルã®ç·¨é›†</a></span></dt><dt><span class="section"><a href="s2-bind-rndc.html">12.2.3. rndc ユーティリティã®ä½¿ç”¨æ³•</a></span></dt><dt><span class="section"><a href="s2-bind-dig.html">12.2.4. dig ユーティリティã®ä½¿ç”¨</a></span></dt><dt><span class="section"><a href="s2-bind-features.html">12.2.5. BIND ã®é«˜åº¦ãªæ©Ÿèƒ½</a></span></dt><dt><span class="section"><a href="s2-bind-mistakes.html">12.2.6. よãã‚ã‚‹é–“é•ã„ã‚’é¿ã‘ã‚‹ãŸã‚ã«</a></span></dt><dt><span class="section"><a href="s2-bind-additional-resources.html">12.2.7. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt></dl></dd></dl></div><a id="idm58401520" class="indexterm"></a><a id="idm26718928" class="indexterm"></a><div class="para">
+ <code class="systemitem">DNS</code> (Domain Name System) は、<em class="firstterm">ネームサーバー</em>としても知られ、ホスト名とそれぞれの IP アドレスを関連づけるネットワークシステムです。ユーザーにとって、ネットワークにあるマシンを名前で参照できるという利便性があります。通常これは数値のネットワークアドレスよりも記憶しやすいです。システム管理者にとって、ネームサーバーを使用することにより、名前に基づいた問い合わせに影響を与えることなくホストの IP アドレスを変更したり、どのマシンがこれらの問い合わせを処理するかを決めたりできるようになります。
+ </div><div class="section" id="s1-Introduction_to_DNS"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.1. DNS の概要</h2></div></div></div><a id="idm58399536" class="indexterm"></a><div class="para">
+ DNS は、集中化されたドメインに対して権威のある、1つか複数の集中化されたサーバーを使用して実装されます。クライアントホストがネームサーバーから情報を要求するとき、通常ポート 53 に接続します。そして、ネームサーバーは要求された名前を解決しようとします。権威のある回答を持たなければ、または以前の問い合わせからキャッシュされた回答をすでに持っていなければ、どのネームサーバーが問い合わせにある名前に対して権威があるかを決めるために、<em class="firstterm">ルートネームサーバー</em>と呼ばれる他のネームサーバーに問い合わせます。そして、要求された名前を取得するためにそのサーバーに問い合わせます。
+ </div><div class="section" id="s2-dns-introduction-zones"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.1. ネームサーバーゾーン</h3></div></div></div><a id="idm58403728" class="indexterm"></a><a id="idm58404384" class="indexterm"></a><a id="idm58406624" class="indexterm"></a><a id="idm58407584" class="indexterm"></a><div class="para">
+ BIND のような DNS サーバーにおいて、すべての情報は<em class="firstterm">リソースレコード</em> (RR) と呼ばれる基本的なデータ要素に保存されます。リソースレコードは通常ホストの <em class="firstterm">fully qualified domain name</em> (FQDN) です。そして、ツリー構造の階層の中に整理された複数のセクションに分解されます。この階層は、主幹、一次分岐、二次分岐などから構成されます。以下はリソースレコードの例です:
+ </div><pre class="programlisting">bob.sales.example.com</pre><a id="idm58410880" class="indexterm"></a><div class="para">
+ 階層の各レベルはピリオド（つまり、<code class="literal">.</code>）により分割されます。上の例では、<code class="literal">com</code> は<em class="firstterm">トップレベルドメイン</em>、そのサブドメイン <code class="literal">example</code>、<code class="literal">example</code> のサブドメイン <code class="literal">sales</code> を定義します。この場合、<code class="literal">bob</code> は <code class="systemitem">sales.example.com</code> ドメインの一部であるリソースレコードを識別します。最も左にある部分（つまり、<code class="literal">bob</code>）を除き、これらのセクションの各部は<em class="firstterm">ゾーン</em>と呼ばれ、具体的な<em class="firstterm">名前空間</em>を定義します。
+ </div><a id="idm46854912" class="indexterm"></a><a id="idm46856000" class="indexterm"></a><div class="para">
+ ゾーンã¯<em class="firstterm">ゾーンファイル</em>ã®ä½¿ç”¨ã«ã‚ˆã‚Šæ¨©å¨ãƒãƒ¼ãƒ サーãƒãƒ¼ã«ãŠã„ã¦å®šç¾©ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€å„ゾーンã«ãŠã‘るリソースレコードã®å®šç¾©ã‚’å«ã¿ã¾ã™ã€‚ゾーンファイルã¯<em class="firstterm">プライマリãƒãƒ¼ãƒ サーãƒãƒ¼</em>（<em class="firstterm">マスターãƒãƒ¼ãƒ サーãƒãƒ¼</em>ã¨ã‚‚呼ã°ã‚Œã¾ã™ï¼‰ã«ãŠã„ã¦ï¼ˆå¤‰æ›´ã¯ãƒ•ã‚¡ã‚¤ãƒ«ã«å¯¾ã—ã¦è¡Œã‚ã‚Œã¾ã™ï¼‰ã€ãŠã‚ˆã³ã€<em class="firstterm">セカンダリãƒãƒ¼ãƒ サーãƒãƒ¼</em>（<em class="firstterm">スレーブãƒãƒ¼ãƒ サーãƒãƒ¼</em>ã¨ã‚‚呼ã°ã‚Œã¾ã™ï¼‰ã«ãŠã„ã¦ï¼ˆãƒ—ライマリãƒãƒ¼ãƒ サーãƒãƒ¼ã‹ã‚‰ã‚¾ãƒ¼ãƒ³å®šç¾©ã‚’å—ä¿¡ã—ã¾ã™ï¼‰ä¿å˜ã•ã‚Œã¾ã™ã€‚プライマリã¨ã‚»ã‚«ãƒ³ãƒ€ãƒªã©ã¡ã‚‰ã®ãƒãƒ¼ãƒ サーãƒãƒ¼ã‚‚ゾーンã«å¯¾ã™ã‚‹æ¨©å¨ã§ã‚ã‚Šã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«åŒã˜ã‚ˆã†ã«è¦‹ãˆã¾ã™ã€‚è¨å®šã«ã‚ˆã£ã¦ã¯ã€ã™ã¹ã¦ã®ãƒãƒ¼ãƒ サーãƒãƒ¼ãŒè¤‡æ•°ã®ã‚¾ãƒ¼ãƒ³ã«å
¯¾ã—ã¦åŒæ™‚ã«ãƒ—ライマリã¾ãŸã¯ã‚»ã‚«ãƒ³ãƒ€ãƒªã‚µãƒ¼ãƒãƒ¼ã¨ã—ã¦ã‚‚処ç†ã§ãã¾ã™ã€‚
+ </div></div><div class="section" id="s2-dns-introduction-nameservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.2. ネームサーバーのタイプ</h3></div></div></div><div class="para">
+ ネームサーバーの設定種別が2つあります:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm51490080" class="indexterm"></a>
+ <a id="idm51492464" class="indexterm"></a>
+ <a id="idm51494992" class="indexterm"></a>
+ <a id="idm51495792" class="indexterm"></a>
+ <a id="idm51498432" class="indexterm"></a>
+ <a id="idm51499872" class="indexterm"></a>
+ 権威</span></dt><dd><div class="para">
+ 権威ネームサーバーはそれらのゾーンのみの一部であるリソースレコードに回答します。この分類はプライマリ（マスター）およびセカンダリ（スレーブ）ネームサーバーを含みます。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm65742432" class="indexterm"></a>
+ <a id="idm65744320" class="indexterm"></a>
+ 再帰</span></dt><dd><div class="para">
+ 再帰ネームサーバーは解決サービスを提供しますが、あらゆるゾーンに対して権威的ではありません。すべての解決に対する回答は、取り出したリソースレコードにより指定された、一定期間メモリーにキャッシュされます。
+ </div></dd></dl></div><div class="para">
+ ネームサーバーは同時に権威および再帰になれますが、設定の種別を組み合わせることは推奨されません。これらの機能を実行できるようにするには、権威サーバーがいつでもすべてのクライアントに利用可能であるべきです。一方、再帰問い合わせは権威のある応答よりも時間がかかるので、再帰サーバーは制限された数のクライアントのみに利用可能であるべきです。そうしなければ、分散サービス妨害（DDoS）攻撃を受けやすくなります。
+ </div></div><div class="section" id="s2-dns-introduction-bind"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.3. ネームサーバーとしての BIND</h3></div></div></div><a id="idm65749328" class="indexterm"></a><a id="idm65753024" class="indexterm"></a><a id="idm17603296" class="indexterm"></a><a id="idm17601392" class="indexterm"></a><a id="idm17603616" class="indexterm"></a><a id="idm17604848" class="indexterm"></a><div class="para">
+ BIND は DNS 関連のプログラム群から構成されています。<code class="systemitem">named</code> という画一的なネームサーバー、<code class="command">rndc</code> という管理ユーティリティ、および <code class="command">dig</code> というデバッグツールを含みます。Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-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="s1-BIND.html"><strong>次へ</strong>12.2. BIND</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Directory_Servers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Directory_Servers.html
new file mode 100644
index 0000000..be229b5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Directory_Servers.html
@@ -0,0 +1,499 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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章 ディレクトリー サーバー</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Servers.html" title="パート V. サーバー" /><link rel="prev" href="s2-email-related-books.html" title="14.6.3. 関連書籍" /><link rel="next" href="ch-File_and_Print_Servers.html" title="第16章 ファイルサーバーおよびプリントサーバー" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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">第15ç« ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ サーãƒãƒ¼</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">15.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">15.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-installation">15.1.2. OpenLDAP 製å“群ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">15.1.3. OpenLDAP サーãƒãƒ¼ã®è¨å®šæ³•</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-running">15.1.4. Running an OpenLDAP Server</a></sp
an></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam">15.1.5. システムが OpenLDAP を使用して認証を実行するように設定する</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-resources">15.1.6. その他のリソース</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">15.1. OpenLDAP</h2></div></div></div><a id="idm24259584" class="indexterm"></a><a id="idm24261424" class="indexterm"></a><a id="idm24263280" class="indexterm"></a><a id="idm24265168" 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">15.1.1. Introduction to LDAP</h3></div></div></div><div class="para">
+ Using a client/server architecture, LDAP provides 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">Secure Sockets Layer</em> (<acronym class="acronym">SSL</acronym>) or <em class="firstterm">Transport Layer Security</em> (<acronym class="acronym">TLS</acronym>) cryptographic protocols 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 17 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, refer to <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">15.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="idm65678400" 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="idm24553888" 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, other 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="idm24562096" 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">15.1.1.2. OpenLDAP 機能</h4></div></div></div><a id="idm35507760" 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">15.1.1.3. OpenLDAP サーバーのセットアップ</h4></div></div></div><a id="idm44614624" 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">
+ OpenLDAP 製品群をインストールします。必要なパッケージの詳細は<a class="xref" href="ch-Directory_Servers.html#s2-ldap-installation">「OpenLDAP 製品群のインストール」</a>を参照してください。
+ </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">15.1.2. OpenLDAP 製品群のインストール</h3></div></div></div><a id="idm44627264" class="indexterm"></a><a id="idm44795968" class="indexterm"></a><div class="para">
+ OpenLDAP のライブラリとツールの製品群は以下のパッケージにより提供されます:
+ </div><div class="table" id="table-ldap-packages-openldap"><h6>表15.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>表15.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_authz_ldap</span>
+ </td><td class="">
+ <div class="para">
+ A package containing <code class="systemitem">mod_authz_ldap</code>, the LDAP authorization module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. Note that the <code class="systemitem">mod_ssl</code> module is required when using the <code class="systemitem">mod_authz_ldap</code> module.
+ </div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ これらのパッケージをインストールするには、以下の形式で <code class="command">yum</code> コマンドを使用します:
+ </div><pre class="screen"><code class="command">yum</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">yum 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, refer to <a class="xref" href="sec-Installing.html">「パッケージのインストール」</a>.
+ </div><div class="section" id="s3-ldap-packages-openldap-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.2.1. OpenLDAP サーバーユーティリティの概要</h4></div></div></div><a id="idm48050080" 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>表15.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, refer to the corresponding manual pages as referred to in <a class="xref" href="ch-Directory_Servers.html#s3-ldap-installed-docs">「インストールされているドキュメント」</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">
+ 起動、停止、再起動および <code class="systemitem">slapd</code> サービスの現在の状態を確認する方法の詳細は、<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">15.1.2.2. OpenLDAP クライアントユーティリティの概要</h4></div></div></div><a id="idm31923248" class="indexterm"></a><div class="para">
+ <span class="package">openldap-clients</span> パッケージは、LDAP ディレクトリのエントリを追加、変更および削除するために使用できる以下のユーティリティをインストールします:
+ </div><div class="table" id="table-ldap-packages-openldap-clients"><h6>表15.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">15.1.2.3. 一般的な LDAP クライアントアプリケーションの概要</h4></div></div></div><a id="idm44174544" 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">15.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>表15.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="idm44187440" 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="idm44881968" 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">15.1.3.1. 全体設定の変更方法</h4></div></div></div><a id="idm44896416" class="indexterm"></a><a id="idm22093648" 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="idm22095520" 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">表15.6「利用可能な olcAllows オプション」</a>. The default option is <code class="option">bind_v2</code>.
+ </div><div class="table" id="table-ldap-configuration-olcallows"><h6>表15.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>例15.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="idm46466192" 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>例15.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="idm18234592" 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>例15.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="idm18242464" 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">表15.7「利用可能な olcDisallows オプション」</a>. No features are disabled by default.
+ </div><div class="table" id="table-ldap-configuration-olcdisallows"><h6>表15.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>例15.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="idm37126224" 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>例15.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="idm37136080" 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>例15.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="idm64767344" 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>例15.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="idm17541664" 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>例15.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">15.1.3.2. データベース固有の設定の変更法</h4></div></div></div><a id="idm25451712" class="indexterm"></a><a id="idm17552560" 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="idm17556720" 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>例15.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="idm57663536" 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>例15.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="idm25449168" 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, use the <code class="command">slappaswd</code> utility, for example:
+ </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>例15.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="idm25461872" 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>例15.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">15.1.3.3. Extending Schema</h4></div></div></div><a id="idm20942544" class="indexterm"></a><a id="idm20943584" 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, refer to <a href="http://www.openldap.org/doc/admin/schema.html">http://www.openldap.org/doc/admin/schema.html</a>.
+ </div></div></div><div class="section" id="s2-ldap-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.1.4. Running an OpenLDAP Server</h3></div></div></div><a id="idm20949376" 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, refer to <a class="xref" href="ch-Services_and_Daemons.html">8章<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">15.1.4.1. サービスの開始</h4></div></div></div><a id="idm21988240" class="indexterm"></a><div class="para">
+ To run the <code class="systemitem">slapd</code> service, 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">
+ ブート時にサービスを自動的に開始したければ、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl enable slapd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s3-ldap-running-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.4.2. サービスの停止</h4></div></div></div><a id="idm21997920" class="indexterm"></a><div class="para">
+ To stop the running <code class="systemitem">slapd</code> service, 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">
+ 起動時にサービスが自動的に開始しないようにするには、次のように入力します:
+ </div><pre class="screen"><code class="command">systemctl disable slapd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s3-ldap-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.4.3. サービスの再起動方法</h4></div></div></div><a id="idm70882368" 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">
+ これにより、サービスが停止し、再び起動します。設定を再読み込みするためにこのコマンドを使用します。
+ </div></div><div class="section" id="s3-ldap-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.4.4. サービスの状態の確認方法</h4></div></div></div><a id="idm70889680" class="indexterm"></a><div class="para">
+ サービスが実行中であるかどうかを確認するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen"><code class="command">systemctl is-active slapd.service</code></pre></div></div><div class="section" id="s2-ldap-pam"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.1.5. システムが 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">yum install openldap openldap-clients nss-pam-ldapd</code></pre><div class="para">
+ <a class="xref" href="ch-Configuring_Authentication.html">9章<em>認証の設定</em></a> provides detailed instructions on how to configure applications to use LDAP for authentication.
+ </div><div class="section" id="s3-ldap-migrationtools"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.5.1. 古い認証情報を LDAP フォーマットへ移行</h4></div></div></div><a id="idm34467376" 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">yum 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, refer to <a class="xref" href="ch-Directory_Servers.html#table-ldap-migrationtools">表15.8「一般的に使用される LDAP 移行スクリプト」</a>.
+ </div><div class="table" id="table-ldap-migrationtools"><h6>表15.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, refer to 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-<em class="replaceable"><code>version</code></em>/</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">15.1.6. その他のリソース</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><div class="section" id="s3-ldap-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.6.1. インストールされているドキュメント</h4></div></div></div><div class="para">
+ The following documentation is installed with the <span class="package">openldap-servers</span> package:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/openldap-servers-<em class="replaceable"><code>version</code></em>/guide.html</code></span></dt><dd><div class="para">
+ A copy of the <em class="citetitle">OpenLDAP Software Administrator's Guide</em>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/openldap-servers-<em class="replaceable"><code>version</code></em>/README.schema</code></span></dt><dd><div class="para">
+ A README file containing the description of installed schema files.
+ </div></dd></dl></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">
+ <code class="command">man ldapadd</code> — Describes how to add entries to an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapdelete</code> — Describes how to delete entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapmodify</code> — Describes how to modify entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapsearch</code> — Describes how to search for entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldappasswd</code> — Describes how to set or change the password of an LDAP user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapcompare</code> — Describes how to use the <code class="command">ldapcompare</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapwhoami</code> — Describes how to use the <code class="command">ldapwhoami</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapmodrdn</code> — 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">
+ <code class="command">man slapd</code> — 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">
+ <code class="command">man slapadd</code> — Describes command line options used to add entries to a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapcat</code> — 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">
+ <code class="command">man slapindex</code> — 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">
+ <code class="command">man slappasswd</code> — 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">
+ <code class="command">man ldap.conf</code> — Describes the format and options available within the configuration file for LDAP clients.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapd-config</code> — Describes the format and options available within the configuration directory.
+ </div></li></ul></div></dd></dl></div></div><div class="section" id="s3-ldap-additional-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">15.1.6.2. 役に立つ Web サイト</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.openldap.org/doc/admin24/">http://www.openldap.org/doc/admin24/</a></span></dt><dd><div 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://www.kingsmountain.com/ldapRoadmap.shtml</a></span></dt><dd><div 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.org/articles/</a></span></dt><dd><div 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></span></dt><dd><div 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"><h4 class="title">15.1.6.3. 関連書籍</h4></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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-related-books.html"><strong>戻る</strong>14.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>第16章 ファイルサーバーおよびプリントサーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-File_and_Print_Servers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-File_and_Print_Servers.html
new file mode 100644
index 0000000..7121e2b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-File_and_Print_Servers.html
@@ -0,0 +1,662 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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章 ファイルサーバーおよびプリントサーバー</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Servers.html" title="パート V. サーバー" /><link rel="prev" href="ch-Directory_Servers.html" title="第15章 ディレクトリー サーバー" /><link rel="next" href="s1-FTP.html" title="16.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" href
="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">第16章 ファイルサーバーおよびプリントサーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">16.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#samba-rgs-overview">16.1.1. Samba の概要</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">16.1.2. Samba デーモンと関連サービス</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-connect-share">16.1.3. Samba シェアへの接続</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-configuring">16.1.4. Samba サーバーの設定</a></span></dt><dt><span class="section"><a hr
ef="ch-File_and_Print_Servers.html#s2-samba-startstop">16.1.5. Samba の開始と停止</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">16.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">16.1.7. Samba のセキュリティモード</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">16.1.8. Samba のアカウント情報データベース</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">16.1.9. Samba ネットワークブラウジング</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-cups">16.1.10. CUPS 印刷サポートを使った Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-pr
ograms">16.1.11. Samba ディストリビューションプログラム</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-resources">16.1.12. その他のリソース</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">16.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-FTP.html#s2-ftp-protocol">16.2.1. ファイル伝送プロトコル</a></span></dt><dt><span class="section"><a href="s2-ftp-servers.html">16.2.2. FTP サーバー</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">16.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">16.2.4. <code class="command">vsftpd</code> の開始と停止</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">16.2.5. <code class="command">vsftpd</code> 設定オプション</a></span></dt><dt><span class="section"><a href="s2-
ftp-resources.html">16.2.6. その他のリソース</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Printer_Configuration.html">16.3. プリンタの設定</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">16.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">16.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="sec-Adding_Other_Printer.html">16.3.3. ローカルプリンタの追加</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">16.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">16.3.5. IPP プリンタの追加</a></span></dt><dt><span class="section"><a href="sec-printing-LPDLPR-printer.html">16.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a h
ref="s1-printing-smb-printer.html">16.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">16.3.8. プリンタモデルの選択と終了</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">16.3.9. Printing a test page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">16.3.10. 既存プリンタの変更</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">16.3.11. その他のリソース</a></span></dt></dl></dd></dl></div><div class="para">
+ <em class="firstterm">Server Message Block</em> (<acronym class="acronym">SMB</acronym>) プロトコルのオープンソース実装である <span class="application"><strong>Samba</strong></span> および Fedora に同梱されている主要な FTP サーバーである <span class="application"><strong>vsftpd</strong></span> のインストールおよび設定についてガイドしています。さらに、プリンターを設定するための<span class="application"><strong>プリンター設定</strong></span>ツールを使用する方法を説明しています。
+ </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">16.1. Samba</h2></div></div></div><a id="idm61787232" class="indexterm"></a><a id="idm61789760" class="indexterm"></a><div class="para">
+ <em class="firstterm">Samba</em> is an open source implementation of the <em class="firstterm">Server Message Block</em> (<code class="systemitem">SMB</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">yum install samba</code></pre><div class="para">
+ Yum を用いてパッケージをインストールする方法の詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</a>を参照してください。
+ </div></div></div><div class="section" id="samba-rgs-overview"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.1. Samba の概要</h3></div></div></div><a id="idm48394992" class="indexterm"></a><div class="para">
+ Samba の 3 番目のメジャーリリースとなる バージョン 3.0.0 は 旧バージョンから数多くの改良が導入されました。
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The ability to join an Active Directory domain by means of the <em class="firstterm">Lightweight Directory Access Protocol</em> (<code class="systemitem">LDAP</code>) and <em class="firstterm">Kerberos</em>
+ </div></li><li class="listitem"><div class="para">
+ 国際化のための組み込み Unicode サポート
+ </div></li><li class="listitem"><div class="para">
+ 最近の Microsoft Windows サーバーとクライアントのすべてのバージョンが、ローカルレジストリの変更の必要性なく、Samba サーバーへの接続をサポートします
+ </div></li><li class="listitem"><div class="para">
+ Two new documents developed by the Samba.org team, which include a 400+ page reference manual, and a 300+ page implementation and integration manual. For more information about these published titles, refer to <a class="xref" href="ch-File_and_Print_Servers.html#s3-samba-resources-published">「関連書籍」</a>.
+ </div></li></ul></div><div class="section" id="s3-samba-abilities"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">16.1.1.1. Samba の機能</h4></div></div></div><a id="idm48405328" class="indexterm"></a><div class="para">
+ Samba はパワフルで用途の広いサーバアプリケーションです。経験豊富なシステム管理者であってもその機能や限界を学んでからインストール及び設定は行ってください。
+ </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
+ </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">16.1.2. Samba デーモンと関連サービス</h3></div></div></div><a id="idm62512976" 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">16.1.2.1. Samba デーモン</h4></div></div></div><a id="idm62515936" 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="idm37275072" 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="idm37283744" 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/<em class="firstterm">Common Internet File System</em> (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="idm57875392" class="indexterm"></a><div class="para">
+ The <code class="command">winbind</code> service resolves user and group information on a server running Windows NT, 2000, 2003 or Windows Server 2008. This makes Windows user / 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/or 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">
+ You may refer to <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">16.1.3. Samba シェアへの接続</h3></div></div></div><a id="idm67624832" 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>図16.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">16.1.3.1. コマンドライン</h4></div></div></div><a id="idm67417056" class="indexterm"></a><a id="idm67417984" class="indexterm"></a><a id="idm67428384" 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="idm67424128" class="indexterm"></a><a id="idm67426384" 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 wish 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">16.1.3.2. シェアの実装</h4></div></div></div><a id="idm20584928" 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">yum install cifs-utils</code></pre><div class="para">
+ Yum を用いてパッケージをインストールする方法の詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</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>, refer to <code class="command">man cifs.upcall</code>.
+ </div></div></div><div class="para">
+ Samba 共有のマウントに関する詳細は <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">16.1.4. Samba サーバーの設定</h3></div></div></div><a id="idm63192208" class="indexterm"></a><a id="idm63194016" 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. In other words, 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">16.1.4.1. グラフィックな設定</h4></div></div></div><a id="idm21642240" 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/samba/GUI/</a>.
+ </div></div><div class="section" id="s3-samba-configuring-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">16.1.4.2. コマンドライン管理</h4></div></div></div><a id="idm21647856" 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">16.1.4.3. 暗合化されたパスワード</h4></div></div></div><div class="para">
+ Encrypted passwords are enabled by default because it is more secure to do so. 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="idm52768672" class="indexterm"></a><a id="idm52774736" class="indexterm"></a><a id="idm52773552" class="indexterm"></a><a id="idm52774352" class="indexterm"></a><a id="idm52776000" class="indexterm"></a><a id="idm47736064" class="indexterm"></a><a id="idm47737856" 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">16.1.5. Samba の開始と停止</h3></div></div></div><a id="idm47741024" class="indexterm"></a><a id="idm47743904" class="indexterm"></a><a id="idm47745744" class="indexterm"></a><a id="idm47748336" class="indexterm"></a><a id="idm47750576" 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.
+ </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, use a service manager such as <code class="command">systemctl</code>. Refer to <a class="xref" href="ch-Services_and_Daemons.html">8章<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">16.1.6. Samba サーバー形式と <code class="filename">smb.conf</code> ファイル</h3></div></div></div><a id="idm20321536" class="indexterm"></a><a id="idm20323312" 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">16.1.6.1. スタンドアローンのサーバ</h4></div></div></div><a id="idm20328384" 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">16.1.6.1.1. Anonymous 読み取り専用</h5></div></div></div><a id="idm20333328" 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">16.1.6.1.2. Anonymous 読み取り/書き込み</h5></div></div></div><a id="idm60917808" 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">16.1.6.1.3. Anonymous プリントサーバ</h5></div></div></div><a id="idm60927696" 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">16.1.6.1.4. 安全な読み取り/書き込みファイルとプリントサーバ</h5></div></div></div><a id="idm25782256" 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">16.1.6.2. ドメインメンバーサーバ</h4></div></div></div><a id="idm69094128" 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">16.1.6.2.1. Active Directory ドメインメンバーサーバ</h5></div></div></div><a id="idm69098416" 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 at 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. For more information on Kerberos, the <code class="command">/etc/krb5.conf</code> file, and the <code class="command">kinit</code> command, refer to the <em class="citetitle">Using Kerberos</em> section of the Red Hat Enterprise Linux 6 <em class="citetitle">Managing Single Sign-On and Smart Cards</em> guide.
+ </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">16.1.6.2.2. Windows NT4 ベースのドメインメンバーサーバ</h5></div></div></div><a id="idm65887536" 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">16.1.6.3. Domain Controller</h4></div></div></div><a id="idm52785520" 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">16.1.6.3.1. Primary Domain Controller (PDC) using <code class="command">tdbsam</code> </h5></div></div></div><a id="idm66200976" 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">16.1.6.3.2. Active Directory を使ったプライマリドメインコントローラ (PDC)</h5></div></div></div><a id="idm27393904" 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">16.1.7. Samba のセキュリティモード</h3></div></div></div><a id="idm17671136" 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">16.1.7.1. ユーザーレベルセキュリティ</h4></div></div></div><a id="idm48794816" 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">16.1.7.1.1. ドメインセキュリティモード (ユーザーレベルセキュリティ)</h5></div></div></div><a id="idm17626272" 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">16.1.7.1.2. Active Directory セキュリティモード (ユーザーレベルセキュリティ)</h5></div></div></div><a id="idm51317792" 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">16.1.7.1.3. サーバセキュリティモード(ユーザーレベルセキュリティ)</h5></div></div></div><a id="idm45455248" 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">16.1.7.2. Share-Level Security</h4></div></div></div><a id="idm70042720" 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">16.1.8. Samba のアカウント情報データベース</h3></div></div></div><a id="idm36765344" 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="idm69681152" class="indexterm"></a><a id="idm57778624" class="indexterm"></a><a id="idm21653456" class="indexterm"></a><a id="idm59515824" class="indexterm"></a><a id="idm20102464" class="indexterm"></a><a id="idm48508736" class="indexterm"></a><a id="idm25159008" class="indexterm"></a><a id="idm21515888" class="indexterm"></a><a id="idm42184544" 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 the <span class="application"><strong>Red Hat Directory Server</strong></span> or an <span class="application"><strong>OpenLDAP Server</strong></span>. LDAP databases are light-weight and scalable, and as such are preferred by large enterprises. Installation and configuration of directory servers is beyond the scope of this chapter. For more information on the <span class="application"><strong>Red Hat Directory Server</strong></span>, refer to the <em class="citetitle">Red Hat Directory Server 8.2 Deployment Guide</em>. 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-<em class="replaceable"><code>version</code></em>/LDAP/samba.schema</code>) and the Red Hat Directory Server schema file (<code class="filename">/usr/share/doc/samba-<em class="replaceable"><code>version</code></em>/LDAP/samba-schema-FDS.ldif</code>) have 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. Refer to <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">16.1.9. Samba ネットワークブラウジング</h3></div></div></div><a id="idm67016240" class="indexterm"></a><a id="idm39345216" 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">16.1.9.1. Domain Browsing</h4></div></div></div><a id="idm40176496" class="indexterm"></a><div class="para">
+ デフォルトでは、ドメインの Windows PDC もそのドメインのドメインマスターブラウザです。このような場合、 Samba サーバはドメインマスターサーバとして設定する必要があります。
+ </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.
+ </div></div><div class="section" id="s3-samba-wins"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">16.1.9.2. WINS (Windows Internet Name Server)</h4></div></div></div><a id="idm45796624" class="indexterm"></a><a id="idm62075600" 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">16.1.10. CUPS 印刷サポートを使った Samba</h3></div></div></div><a id="idm59107424" 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">16.1.10.1. Simple <code class="filename">smb.conf</code> Settings</h4></div></div></div><a id="idm24458752" 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">16.1.11. Samba ディストリビューションプログラム</h3></div></div></div><a id="idm41580592" class="indexterm"></a><h4 id="s3-samba-programs-findsmb"><code class="filename">findsmb</code></h4><a id="idm25973888" class="indexterm"></a><a id="idm29933120" 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="idm47328464" class="indexterm"></a><a id="idm66383840" 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 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="idm55914688" class="indexterm"></a><a id="idm39504048" 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">
+ 次がその例です。
+ </div><pre class="screen">~]$ <code class="command">nmblookup trek</code>
+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="idm64692368" class="indexterm"></a><a id="idm27738320" 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="idm43618016" class="indexterm"></a><a id="idm42617088" 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="idm24723792" class="indexterm"></a><a id="idm24395184" 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="idm27687760" class="indexterm"></a><a id="idm41983968" 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="idm26574560" class="indexterm"></a><a id="idm69106064" 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="idm60895072" class="indexterm"></a><a id="idm48621952" 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 as well as 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="idm61033680" class="indexterm"></a><a id="idm36841168" 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="idm47180752" class="indexterm"></a><a id="idm51649648" 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="idm27626416" class="indexterm"></a><a id="idm40974736" 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="idm21851376" class="indexterm"></a><a id="idm24307392" 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">/etc/samba/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 hostname and IP 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">/etc/samba/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="idm53254064" class="indexterm"></a><a id="idm27310224" 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">16.1.12. その他のリソース</h3></div></div></div><a id="idm47540320" 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">16.1.12.1. インストールされているドキュメント</h4></div></div></div><a id="idm41593904" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/samba-<em class="replaceable"><code>version-number</code></em>/</code> — All additional files included with the Samba distribution. This includes all helper scripts, sample configuration files, and documentation. This directory also contains online versions of <em class="citetitle">The Official Samba-3 HOWTO-Collection</em> and <em class="citetitle">Samba-3 by Example</em>, both of which are cited below.
+ </div><div class="note"><div class="admonition_header"><h2>Make sure you have the samba-doc package installed</h2></div><div class="admonition"><div class="para">
+ In order to use the <span class="application"><strong>Samba</strong></span> documentation, first ensure the <span class="package">samba-doc</span> package is installed on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install samba-doc</code></pre><div class="para">
+ Yum を用いてパッケージをインストールする方法の詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</a>を参照してください。
+ </div></div></div></li></ul></div><div class="para">
+ Refer to the following manual pages for detailed information specific <span class="application"><strong>Samba</strong></span> features:
+ </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">16.1.12.2. 関連書籍</h4></div></div></div><a id="idm62692800" 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">16.1.12.3. 役に立つ Web サイト</h4></div></div></div><a id="idm59298976" 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.org/samba/archives.html </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 gmane.org, that use the NNTP 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>第15章 ディレクトリー サーバー</a></li><li class="up"><a accesskey="u" href="#"><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>16.2. FTP</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html
new file mode 100644
index 0000000..447e98a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Graphical_Package_Management-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>5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-PackageKit.html" title="第5章 PackageKit" /><link rel="prev" href="sec-PackageKit_Architecture.html" title="5.3. PackageKit アーキテクチャー" /><link rel="next" href="part-Networking.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-PackageKit_Architecture.html"><strong>戻る</strong></a></li>
<li class="next"><a accesskey="n" href="part-Networking.html"><strong>次へ</strong></a></li></ul><div class="section" id="ch-Graphical_Package_Management-sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. その他のリソース</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="application"><strong>PackageKit</strong></span> ホームページ — <a href="http://www.packagekit.org/index.html">http://www.packagekit.org/index.html</a></span></dt><dd><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> のメーリングリストに関する情報です。
+ </div></dd><dt class="varlistentry"><span class="term"><span class="application"><strong>PackageKit</strong></span> FAQ — <a href="http://www.packagekit.org/pk-faq.html">http://www.packagekit.org/pk-faq.html</a></span></dt><dd><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> ソフトウェアスイートのよくある質問の参考一覧です。
+ </div></dd><dt class="varlistentry"><span class="term"><span class="application"><strong>PackageKit</strong></span> 機能マトリクス — <a href="http://www.packagekit.org/pk-matrix.html">http://www.packagekit.org/pk-matrix.html</a></span></dt><dd><div class="para">
+ パッケージ管理のバックエンドの長い一覧を持つ、<span class="application"><strong>PackageKit</strong></span> が提供する機能の相互参照です。
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-PackageKit_Architecture.html"><strong>戻る</strong>5.3. PackageKit アーキテクチャー</a></li><li class="up"><a accesskey="u" href="#"><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-Networking.html"><strong>次へ</strong>パート III. ネットワーク</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Mail_Servers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Mail_Servers.html
new file mode 100644
index 0000000..686e6c4
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Mail_Servers.html
@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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章 メールサーバー</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Servers.html" title="パート V. サーバー" /><link rel="prev" href="ch-Web_Servers.html" title="第13章 ウェブ サーバー" /><link rel="next" href="s1-email-types.html" title="14.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 a
ccesskey="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">第14章 メールサーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s1-email-protocols">14.1. 電子メールプロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-send">14.1.1. メール トランスポートのプロトコル</a></span></dt><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-client">14.1.2. メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">14.2. 電子メールプログラム分類</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">14.2.1. メール転送エージェント (Mail Transport Agent)</a></s
pan></dt><dt><span class="section"><a href="s2-email-types-mda.html">14.2.2. メール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">14.2.3. メール ユーザー エージェント</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">14.3. Mail Transport Agent</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-postfix">14.3.1. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-sendmail.html">14.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">14.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="s2-email-switchmail.html">14.3.4. Mail Transport Agent (MTA) の設定</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mda.html">14.4. メール配送エージェント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-
email-procmail-configuration">14.4.1. Procmail の設定</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">14.4.2. Procmail レシピ</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">14.5. メールユーザーエージェント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">14.5.1. 通信のセキュリティ</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">14.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">14.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">14.6.2. 役に立つ Web サイト</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">14.6.3. 関連書籍</a></span></dt></dl></dd></dl></div><a id="idm
50544736" class="indexterm"></a><div class="para">
+ <em class="firstterm">電子メール</em>は1960年代に生まれました。メールボックスは、そのユーザーのみが読み込めるユーザーのホームディレクトリにあるファイルでした。初期の電子メールアプリケーションは新しいテキストメッセージをファイルの末尾に追加しました。ユーザーはある特定のメッセージを検索するために常に大きくなるファイルを読み通します。このシステムは同じシステムにいるユーザーにメッセージを送信できるだけでした。
+ </div><div class="para">
+ 電子メールのメッセージファイルのネットワーク転送は1971年に初めて行われました。Ray Tomlinson というコンピューター技術者が、インターネットの前進である ARPANET 経由で2台のマシン間でテストメッセージを送信しました。電子メールによるコミュニケーションは、すぐに大人気になり、2年しないうちに ARPANET のトラフィックの75%を占めるようになりました。
+ </div><div class="para">
+ 今日、標準化されたネットワークプロトコルに基づいた電子メールシステムは、インターネットにおいて最も広く利用されるサービスのいくつかに進歩してきました。Fedora は電子メールを処理およびアクセスする多くの高度なアプリケーションを提供します。
+ </div><div class="para">
+ 本章は今日使用されている最近の電子メールプロトコル、および電子メールを送信および受信するよう設定されたプログラムのいくつかを概説します。
+ </div><div class="section" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">14.1. 電子メールプロトコル</h2></div></div></div><a id="idm19991712" 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">14.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">14.1.1.1. SMTP</h4></div></div></div><a id="idm31350384" 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">14.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">14.1.2.1. POP</h4></div></div></div><a id="idm47070048" 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">
+ <span class="application"><strong>Dovecot</strong></span> を使用するには、まず <code class="systemitem">root</code> として次のコマンドを実行することにより、マシンに <code class="command">dovecot</code> パッケージを確実にインストールします:
+ </div><pre class="screen"><code class="command">yum install dovecot</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</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">MDS</code> (Monash Directory Service) authentication. An encoded hash of the user's password is sent from the email client to the server rather then 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">/usr/sbin/stunnel</code> application. For more information on securing email communication, refer to <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">14.1.2.2. IMAP</h4></div></div></div><a id="idm25073024" class="indexterm"></a><div class="para">
+ Fedora における標準の <code class="systemitem">IMAP</code> サーバーは <span class="application"><strong>Dovecot</strong></span> です。<span class="package">dovecot</span> パッケージにより提供されます。<span class="application"><strong>Dovecot</strong></span> をインストールする方法の詳細は<a class="xref" href="ch-Mail_Servers.html#s3-email-protocols-pop">「POP」</a>を参照してください。
+ </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">/usr/sbin/stunnel</code> program. For more information on securing email communication, refer to <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">14.1.2.3. Dovecot</h4></div></div></div><a id="idm56677488" 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="command">#</code>) at the beginning of the line) and contains the <code class="literal">pop3</code> argument. For example:
+ </div><pre class="programlisting">protocols = imap imaps pop3 pop3s</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 specified for this variable.
+ </div></li><li class="listitem"><div class="para">
+ Make that 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.service</code></pre></li><li class="listitem"><div class="para">
+ コマンドを起動させることによって、次回のリブート後に変更を操作可能にします。
+ </div><pre class="screen"><code class="command">systemctl enable dovecot.service</code></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 username 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.conf</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 typing the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl restart dovecot.service</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>第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="s1-email-types.html"><strong>次へ</strong>14.2. 電子メールプログラム分類</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html
new file mode 100644
index 0000000..eb0607b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.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>第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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-Configuring_the_Date_and_Time-Additional_Resources.html" title="2.3. その他のリソース" /><link rel="next" href="sect-Managing_Users_and_Groups-User_Accounts.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-Configuring_the_Date_and_Time-Additional_Resources.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Managing_Users_and_Groups-User_Accounts.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">第3章 ユーザーとグループの管理</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">3.1. ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">3.1.1. ユーザープライベートグループ</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">3.1.2. シャドウパスワード</a></span>
</dt></dl></dd><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts.html">3.2. ユーザー アカウントのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts.html#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.2.1. アカウントの設定</a></span></dt><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html">3.2.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html">3.2.3. ユーザーの削除</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">3.3. ユーザー管理のツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-configui.html#s2-redhat-config-users-list">3.3.1. ユーザーとグループを閲覧する</a></span></dt><dt><span clas
s="section"><a href="s2-redhat-config-users-user-new.html">3.3.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-group-new.html">3.3.3. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-user-properties.html">3.3.4. ユーザーのプロパティを変更する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-group-properties.html">3.3.5. グループのプロパティを変更する</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">3.4. コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">3.4.1. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">3.4.2. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="s2-users-tools-
password-aging.html">3.4.3. パスワードエージングの有効化</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">3.4.4. 自動ログアウトの有効化</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">3.4.5. グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-additional-resources.html">3.5. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">3.5.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a id="idm58657728" class="indexterm"></a><a id="idm54738032" class="indexterm"></a><a id="idm56534368" class="indexterm"></a><a id="idm44082288" class="indexterm"></a><div class="para">
+ ユーザーとグループの管理は Fedora のシステム管理の中心的な要素です。本章は、グラフィカルユーザーインターフェースとコマンドラインにおいてユーザーとグループを追加、管理および削除する方法について説明しています。また、パスワードエージングやグループディレクトリの作成などの高度な話題を取り扱います。
+ </div><div class="section" id="s1-users-groups-introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. ユーザーとグループのイントロダクション</h2></div></div></div><div class="para">
+ ユーザーが人（アカウントが物理的なユーザーにひもづいていることを意味します）または特定のアプリケーションが使用するために存在するアカウントである一方、グループは共通の目的のために一緒なユーザーとひもづく組織の論理的な表現です。
+ </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">
+ さらに Fedora は、所有者以外の特定のユーザーに対してパーミッションを設定できる<em class="firstterm">アクセス制御リスト</em> (<acronym class="acronym">ACLs</acronym>: access control lists) をファイルとディレクトリに対してサポートしています。この機能の詳細については、<a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/index.html"><em class="citetitle">Storage Administration Guide</em></a> の <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-acls.html"><em class="citetitle">Access Control Lists</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">3.1.1. ユーザープライベートグループ</h3></div></div></div><a id="idm72172672" class="indexterm"></a><a id="idm43928208" class="indexterm"></a><a id="idm43926800" class="indexterm"></a><a id="idm20784304" 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">
+ 新しく作成されたファイルやディレクトリに適用されるパーミッションを決める設定は、<em class="firstterm">umask</em> と呼ばれ、<code class="filename">/etc/bashrc</code> ファイルにおいて設定されます。UNIX システムにおいては伝統的に、ファイルやディレクトリを作成したユーザーのみが変更をできる、<code class="command">umask</code> が <code class="command">022</code> に設定されます。このスキーマの下では、 <span class="emphasis"><em>作成者のグループのメンバーを含めて</em></span>すべての他のユーザーはすべての変更が許可されません。しかしながら、UPG スキーマにおいては、すべてのユーザーが自分のプライベートグループを持つので、この<span class="quote">「<span class="quote">グループ保護</span>」</span>は必要ありません。
+ </div></div><div class="section" id="s2-users-groups-shadow-utilities"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.1.2. シャドウパスワード</h3></div></div></div><a id="idm29696064" class="indexterm"></a><a id="idm29694624" class="indexterm"></a><div class="para">
+ 複数のユーザーを持つ環境においてはとくに、システムの認証ファイルのセキュリティを向上させるために、<span class="package">shadow-utils</span> パッケージにより提供される<em class="firstterm">シャドウパスワード</em>を使用することは非常に重要です。このため、インストールプログラムはデフォルトでシャドウパスワードを有効にします。
+ </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">
+ <span class="package">shadow-utils</span> パッケージにより提供されるユーティリティの多くは、シャドウパスワードが有効かどうかによらず適切に機能します。しかしながら、パスワードエージング情報は <code class="filename">/etc/shadow</code> ファイルにだけ保存されるので、パスワードエージング情報を作成または変更するコマンドはすべて動作しません。以下は最初にシャドウパスワードを有効にしないと動作しないユーティリティとコマンドの一覧です:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">chage</code> ユーティリティ。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">gpasswd</code> ユーティリティ。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">-e</code> または <code class="option">-f</code> オプションをつけた <code class="command">usermod</code> コマンド。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">-e</code> または <code class="option">-f</code> オプションをつけた <code class="command">useradd</code> コマンド。
+ </div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Date_and_Time-Additional_Resources.html"><strong>戻る</strong>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="sect-Managing_Users_and_Groups-User_Accounts.html"><strong>次へ</strong>3.2. ユーザー アカウントのツールを使う</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html
new file mode 100644
index 0000000..36f7445
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>第21章 カーネルをアップグレードする</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Kernel_Module_and_Driver_Configuration.html" title="パート VII. カーネル、モジュールおよびドライバーの設定" /><link rel="prev" href="part-Kernel_Module_and_Driver_Configuration.html" title="パート VII. カーネル、モジュールおよびドライバーの設定" /><link rel="next" href="s1-kernel-preparing.html" title="21.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="Docume
ntation 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="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">第21章 カーネルをアップグレードする</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">21.1. カーネルパッケージの概要</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">21.2. アップグレードの準備</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">21.3. アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">
21.4. アップグレードの実行</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">21.5. 初期RAMディスクイメージの確認</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">21.6. ブートローダの確認</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-pseries.html">21.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></div><a id="idm54792528" class="indexterm"></a><a id="idm50202048" class="indexterm"></a><a id="idm45334960" class="indexterm"></a><a id="idm58810224" 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>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span> package managers. <span class="application"><strong>PackageKit</strong></span> automatically queries the Yum repositories and informs you of packages with available updates, including kernel packages.
+ </div><div class="para">
+ そのため、本章は <code class="command">yum</code> の代わりに <code class="command">rpm</code> コマンドを使用してカーネルパッケージを手動で更新する必要があるユーザーの対して<span class="emphasis"><em>のみ</em></span>有用です。
+ </div><a id="idm37112352" class="indexterm"></a><a id="idm49015984" class="indexterm"></a><div class="warning"><div class="admonition_header"><h2>Use Yum to install kernels whenever possible</h2></div><div class="admonition"><div class="para">
+ Whenever possible, use either the <span class="application"><strong>Yum</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="idm36626832" class="indexterm"></a><div class="para">
+ For more information on installing kernel packages with <span class="application"><strong>Yum</strong></span>, refer to <a class="xref" href="ch-yum.html#sec-Updating_Packages">「パッケージの更新」</a>.
+ </div><div class="section" id="s1-kernel-packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.1. カーネルパッケージの概要</h2></div></div></div><a id="idm66286128" class="indexterm"></a><a id="idm52790000" class="indexterm"></a><a id="idm52788112" class="indexterm"></a><a id="idm41066576" class="indexterm"></a><a id="idm41064720" class="indexterm"></a><a id="idm41062832" class="indexterm"></a><a id="idm41130176" class="indexterm"></a><a id="idm41128256" class="indexterm"></a><a id="idm69488496" class="indexterm"></a><a id="idm69486576" class="indexterm"></a><a id="idm69484656" class="indexterm"></a><a id="idm56419568" class="indexterm"></a><a id="idm56417648" 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-doc</span> — Documentation files from the kernel source. Various portions of the Linux kernel and the device drivers shipped with it are documented in these files. Installation of this package provides a reference to the options that can be passed to Linux kernel modules at load time.
+ </div><div class="para">
+ By default, these files are placed in the <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/</code> directory.
+ </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></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Kernel_Module_and_Driver_Configuration.html"><strong>戻る</strong>パート VII. カーネル、モジュールおよびドライバーの設定</a></li><li class="up"><a accesskey="u" href="#"><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>21.2. アップグレードの準備</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-NetworkManager.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-NetworkManager.html
new file mode 100644
index 0000000..e8147e6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-NetworkManager.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章 NetworkManager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Networking.html" title="パート III. ネットワーク" /><link rel="prev" href="part-Networking.html" title="パート III. ネットワーク" /><link rel="next" href="sec-Interacting_with_NetworkManager.html" title="6.2. Interacting with NetworkManager" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Networking.html"><strong>戻る</stron
g></a></li><li class="next"><a accesskey="n" href="sec-Interacting_with_NetworkManager.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="chapter" id="ch-NetworkManager" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第6章 NetworkManager</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-NetworkManager.html#sec-The_NetworkManager_Daemon">6.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html">6.2. Interacting with NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">6.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">6.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.htm
l">6.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-User_and_System_Connections.html">6.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Establishing_Connections.html">6.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Establishing_Connections.html#sec-Establishing_a_Wired_Ethernet_Connection">6.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Wireless_Connection.html">6.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">6.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">6.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html
">6.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_Routes.html">6.3.6. Establishing Routes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">6.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html#sec-Configuring_802.1x_Security">6.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_Wireless_Security.html">6.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_PPP_Point-to-Point_Settings.html">6.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv4_Settings.html">6.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Settings.html">6.4.5. Configuring IPv6 Settings</a></span></dt></dl></d
d><dt><span class="section"><a href="sec-NetworkManager_Architecture.html">6.5. NetworkManager Architecture</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> is a dynamic network control and configuration system that attempts to keep network devices and connections up and active when they are available. <span class="application"><strong>NetworkManager</strong></span> consists of a core daemon, a GNOME Notification Area applet that provides network status information, and graphical configuration tools that can create, edit and remove connections and interfaces. <span class="application"><strong>NetworkManager</strong></span> can be used to configure the following types of connections: Ethernet, wireless, mobile broadband (such as cellular 3G), and <code class="systemitem">DSL</code> and <code class="systemitem">PPPoE</code> (Point-to-Point over Ethernet). In addition, <span class="application"><strong>NetworkManager</strong></span> allows for the configuration of network aliases, static routes, DNS information and VPN connections, as well as many connection-specifi
c parameters. Finally, <span class="application"><strong>NetworkManager</strong></span> provides a rich API via D-Bus which allows applications to query and control network configuration and state.
+ </div><div class="para">
+ Previous versions of Fedora included the <span class="application"><strong>Network Administration Tool</strong></span>, which was commonly known as <code class="command">system-config-network</code> after its command line invocation. In Fedora 17, <span class="application"><strong>NetworkManager</strong></span> replaces the former <span class="application"><strong>Network Administration Tool</strong></span> while providing enhanced functionality, such as user-specific and mobile broadband configuration. It is also possible to configure the network in Fedora 17 by editing interface configuration files; refer to <a class="xref" href="ch-Network_Interfaces.html">7章<em>ネットワーク・インターフェース</em></a> for more information.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> may be installed by default on Fedora. To ensure that it is, first run the following command as the root user:
+ </div><pre class="screen">~]# <code class="command">yum install NetworkManager</code>
+</pre><div class="section" id="sec-The_NetworkManager_Daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. The NetworkManager Daemon</h2></div></div></div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> daemon runs with root privileges and is usually configured to start up at boot time. You can determine whether the <span class="application"><strong>NetworkManager</strong></span> daemon is running by entering this command as root:
+ </div><pre class="screen">~]# <code class="command">service NetworkManager status</code>
+NetworkManager (pid 1527) is running...
+</pre><div class="para">
+ The <code class="command">service</code> command will report <code class="computeroutput">NetworkManager is stopped</code> if the <span class="application"><strong>NetworkManager</strong></span> service is not running. To start it for the current session:
+ </div><pre class="screen">~]# <code class="command">service NetworkManager start</code>
+</pre><div class="para">
+ Run the <code class="command">chkconfig</code> command to ensure that <span class="application"><strong>NetworkManager</strong></span> starts up every time the system boots:
+ </div><pre class="screen">~]# <code class="command">chkconfig NetworkManager on</code>
+</pre><div class="para">
+ For more information on starting, stopping and managing services and runlevels, refer to <a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Networking.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="sec-Interacting_with_NetworkManager.html"><strong>次へ</strong>6.2. Interacting with NetworkManager</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Network_Interfaces.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Network_Interfaces.html
new file mode 100644
index 0000000..d3423b9
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Network_Interfaces.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>第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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Networking.html" title="パート III. ネットワーク" /><link rel="prev" href="sec-NetworkManager_Architecture.html" title="6.5. NetworkManager Architecture" /><link rel="next" href="s1-networkscripts-interfaces.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="sec-NetworkManager_Archite
cture.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-interfaces.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="chapter" id="ch-Network_Interfaces" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第7章 ネットワーク・インターフェース</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Network_Interfaces.html#s1-networkscripts-files">7.1. ネットワーク設定ファイル</a></span></dt><dt><span class="section"><a href="s1-networkscripts-interfaces.html">7.2. インターフェース設定ファイル</a></span></dt><dd><dl><dt><span class="section"><a href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">7.2.1. イーサネット インターフェース</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-chan.html">7.2.2. チャンネル・ボンディング・インターフェース</a></s
pan></dt><dt><span class="section"><a href="s2-networkscripts-interfaces_network-bridge.html">7.2.3. ネットワークブリッジ</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html">7.2.4. Setting up 802.1q VLAN tagging</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-alias.html">7.2.5. エイリアス ファイルとクローン ファイル</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-ppp0.html">7.2.6. ダイヤルアップ インターフェース</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-other.html">7.2.7. 他のインターフェース</a></span></dt></dl></dd><dt><span class="section"><a href="s1-networkscripts-control.html">7.3. インターフェース制御スクリプト</a></span></dt><dt><span class="section"><a href="s1-networkscripts-static-routes.html">7.4. スタティック ルートの設定</a></span></
dt><dt><span class="section"><a href="s1-networkscripts-functions.html">7.5. ネットワーク機能ファイル</a></span></dt><dt><span class="section"><a href="s1-networkscripts-resources.html">7.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-networkscripts-resources.html#s2-networkscripts-docs-inst">7.6.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></div><a id="idm20224336" class="indexterm"></a><a id="idm26396800" class="indexterm"></a><div class="para">
+ Fedora においては、すべてのネットワーク通信はシステムに接続された設定済みソフトウェア<em class="firstterm">インターフェース</em>と<em class="firstterm">物理ネットワークデバイス</em>の間で発生します。
+ </div><div class="para">
+ The configuration files for network interfaces are located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. The scripts used to activate and deactivate these network interfaces are also located here. Although the number and type of interface files can differ from system to system, there are three categories of files that exist in this directory:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <em class="firstterm">インターフェースの設定ファイル</em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">インターフェースの制御スクリプト</em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">ネットワークの関数ファイル</em>
+ </div></li></ol></div><div class="para">
+ これらの各カテゴリーのファイルは、合同で機能し各種ネットワークデバイスを動作させます。
+ </div><div class="para">
+ この章では、これらファイル間の関係とファイルの使用方法について説明していきます。
+ </div><div class="section" id="s1-networkscripts-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. ネットワーク設定ファイル</h2></div></div></div><a id="idm60932432" class="indexterm"></a><div class="para">
+ インターフェース設定ファイルを調べる前に、まずネットワーク設定において使用される主要な設定ファイルを項目別にあげましょう。Fedora システムをカスタマイズするときに役に立つネットワークスタックをセットアップすることに役立ちます。
+ </div><div class="para">
+ 主要なネットワーク設定ファイルは、次のようになります：
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/etc/hosts</code></span></dt><dd><div class="para">
+ The main purpose of this file is to resolve hostnames that cannot be resolved any other way. It can also be used to resolve hostnames on small networks with no DNS server. Regardless of the type of network the computer is on, this file should contain a line specifying the IP address of the loopback device (<code class="systemitem">127.0.0.1</code>) as <code class="systemitem">localhost.localdomain</code>. For more information, refer to the <span class="bold bold"><strong>hosts</strong></span>(5) manual page.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/etc/resolv.conf</code></span></dt><dd><div class="para">
+ This file specifies the IP addresses of DNS servers and the search domain. Unless configured to do otherwise, the network initialization scripts populate this file. For more information about this file, refer to the <span class="bold bold"><strong>resolv.conf</strong></span>(5) manual page.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/etc/sysconfig/network</code></span></dt><dd><div class="para">
+ このファイルはすべてのネットワークインターフェースに対するルーティングとホスト情報を指定します。このファイルと利用可能なディレクティブの詳細は、<a class="xref" href="ch-The_sysconfig_Directory.html#s2-sysconfig-network">「/etc/sysconfig/network」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>interface-name</code></em> </code></span></dt><dd><div class="para">
+ 各ネットワークインターフェースに対して、対応するインターフェース設定ファイルがあります。これらのファイルはそれぞれ、特定のネットワークインターフェースに固有の情報を提供します。この種のファイルと利用可能なディレクティブに関する詳細は<a class="xref" href="s1-networkscripts-interfaces.html">「インターフェース設定ファイル」</a>を参照してください。
+ </div></dd></dl></div><div class="important"><div class="admonition_header"><h2>ネットワークインターフェース名</h2></div><div class="admonition"><div class="para">
+ ネットワークインターフェース名は異なるハードウェア種別において異なるかもしれません。詳細は<a class="xref" href="appe-Consistent_Network_Device_Naming.html">付録A <em>Consistent Network Device Naming</em></a>を参照してください。
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>/etc/sysconfig/networking/ ディレクトリ</h2></div><div class="admonition"><div class="para">
+ The <code class="filename">/etc/sysconfig/networking/</code> directory is used by the now deprecated <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>). Its contents should <span class="strong strong"><strong>not</strong></span> be edited manually. Using only one method for network configuration is strongly encouraged, due to the risk of configuration deletion. For more information about configuring network interfaces using graphical configuration tools, refer to <a class="xref" href="ch-NetworkManager.html">6章<em>NetworkManager</em></a>.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-NetworkManager_Architecture.html"><strong>戻る</strong>6.5. NetworkManager Architecture</a></li><li class="up"><a accesskey="u" href="#"><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-networkscripts-interfaces.html"><strong>次へ</strong>7.2. インターフェース設定ファイル</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-OProfile.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-OProfile.html
new file mode 100644
index 0000000..bab526b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-OProfile.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>第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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Monitoring_and_Automation.html" title="パート VI. 監視および自動化" /><link rel="prev" href="s1-autotasks-additional-resources.html" title="19.3. その他のリソース" /><link rel="next" href="s1-oprofile-configuring.html" title="20.2. Configuring 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="s1-autotasks-additional-resource
s.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-configuring.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><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">20.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="s1-oprofile-configuring.html">20.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">20.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">20.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">20.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofi
le-starting.html">20.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">20.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">20.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">20.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">20.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">20.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">20.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">20.6. Understanding <code class="filename">/dev/op
rofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">20.7. 使用法の例</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">20.8. 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.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-gui.html">20.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">20.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="s1-oprofile-additional-resources.html">20.11. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-docs">20.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="s2-oprofile-useful-websites.html">20.11.2. 役に立つ Web サイト</a></s
pan></dt></dl></dd></dl></div><a id="idm63290064" class="indexterm"></a><a id="idm45687664" 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, essentially rolls over, 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">
+ OProfile is a useful tool, but be aware of some limitations when using it:
+ </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. Run 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="idm20064976" 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 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. Refer to <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. Refer to <a class="xref" href="s1-oprofile-configuring.html">「Configuring OProfile」</a> for details.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="command">opreport</code>
+ </td><td class="">
+ <div class="para">
+ Retrieves profile data. Refer to <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></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-oprofile-configuring.html"><strong>次へ</strong>20.2. Configuring OProfile</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-OpenSSH.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-OpenSSH.html
new file mode 100644
index 0000000..c727c06
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>第10章 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Infrastructure_Services.html" title="パート IV. インフラストラクチャーサービス" /><link rel="prev" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html" title="9.2.9. SSSD Configuration File Format" /><link rel="next" href="s1-ssh-configuration.html" title="10.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 c
lass="previous"><a accesskey="p" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.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">第10ç« OpenSSH</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">10.1. SSH プãƒãƒˆã‚³ãƒ«</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">10.1.1. ãªãœ SSH を使ã†ã®ã‹ï¼Ÿ</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-features">10.1.2. 主ãªæ©Ÿèƒ½</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">10.1.3. プãƒãƒˆã‚³ãƒ«ãƒ»ãƒãƒ¼ã‚¸ãƒ§ãƒ³</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">10.1.4. SSH コãƒã
‚¯ã‚·ãƒ§ãƒ³ã®ã‚¤ãƒ™ãƒ³ãƒˆãƒ»ã‚·ãƒ¼ã‚±ãƒ³ã‚¹</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">10.2. OpenSSH ã®è¨å®š</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">10.2.1. è¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">10.2.2. OpenSSH サーãƒãƒ¼ã®èµ·å‹•</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">10.2.3. リモート接続ã«å¯¾ã™ã‚‹ SSH ã®è¦æ±‚</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">10.2.4. ã‚ーèªè¨¼ã®ä½¿ç”¨</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clients.html">10.3. OpenSSH クライアント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">10.3.1. ssh ユーティリティã®ä½¿ç”¨æ–¹æ³•</a></span></dt><dt><span class="section"><a href="s2-ss
h-clients-scp.html">10.3.2. <code class="command">scp</code> ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">10.3.3. <code class="command">sftp</code> ユーティリティの使用方法</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-beyondshell.html">10.4. 安全なシェル以上のもの</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">10.4.1. X11 転送</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">10.4.2. ポート転送</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">10.5. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-openssh-additional-resources.html#s2-openssh-installed-docs">10.5.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-openssh-useful-websi
tes.html">10.5.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></div><a id="idm48733344" class="indexterm"></a><div class="para">
+ <code class="systemitem">SSH</code> (Secure Shell) は、クライアント/サーバー型アーキテクチャーを用いて2つのシステム間でセキュアなコミュニケーションを促進して、ユーザーがサーバー・ホスト・システムにリモートでログインできるようにするプロトコルです。<code class="systemitem">FTP</code> や <code class="systemitem">Telnet</code> のような他のリモート・コミュニケーション・プロトコルと違い、SSH はログインセッションを暗号化します。侵入者が暗号化されていないパスワードを収集するのを難しくするコミュニケーションを行います。
+ </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 は一般的な OpenSSH パッケージ (<span class="package">openssh</span>) だけでなく、OpenSSH サーバー (<span class="package">openssh-server</span>) およびクライアント (<span class="package">openssh-clients</span>) パッケージを含みます。OpenSSH パッケージは OpenSSL パッケージ (<span class="package">openssl</span>) を必要なことに注意してください。これは OpenSSH に暗号化されたコミュニケーションを提供できるようにする、いくつかの重要な暗号ライブラリをインストールします。
+ </div><div class="section" id="s1-ssh-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.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">10.1.1. なぜ SSH を使うのか？</h3></div></div></div><a id="idm73680592" 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">10.1.2. 主な機能</h3></div></div></div><a id="idm69067440" class="indexterm"></a><a id="idm69066000" 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">
+ <em class="firstterm">X11 転送</em>という技術を使用することで、クライアントはサーバーから <em class="firstterm">X11</em> (<em class="firstterm">X Window System</em>) アプリケーションを転送できます。
+ </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">10.1.3. プロトコル・バージョン</h3></div></div></div><a id="idm18187088" class="indexterm"></a><a id="idm18185648" class="indexterm"></a><div class="para">
+ 現在 SSH には2種類あります。バージョン1と新しいバージョン2です。Fedora の OpenSSH は SSH バージョン2を使用します。これは、バージョン1において知られていたエクスプロイトに脆弱性がない、改善された鍵交換アルゴリズムを持ちます。しかしながら、互換性のため、OpenSSH はバージョン1の接続も同様にサポートします。
+ </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">10.1.4. SSH コネクションのイベント・シーケンス</h3></div></div></div><a id="idm68125520" 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">
+ リモートクライアントは、暗号化した接続を通じてリモートホストと交信します。
+ </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">10.1.4.1. トランスポート層</h4></div></div></div><a id="idm54248272" 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">
+ éµäº¤æ›ã®é–“ã€ã‚µãƒ¼ãƒãƒ¼ã¯ãれ自身を独自㮠<em class="firstterm">ホストéµ</em> ã§ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«å¯¾ã—ã¦è¨¼æ˜Žã—ã¾ã™ã€‚クライアントãŒã“ã®ç‰¹å®šã®ã‚µãƒ¼ãƒãƒ¼ã¨éŽåŽ»ã«é€šä¿¡ã—ãŸã“ã¨ãŒãªã‘ã‚Œã°ã€ã‚µãƒ¼ãƒãƒ¼ã®ãƒ›ã‚¹ãƒˆéµã¯ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«ã¯æœªçŸ¥ã§ã‚ã‚Šã€æŽ¥ç¶šã¯æˆç«‹ã—ã¾ã›ã‚“。 OpenSSH ã¯ã€ã‚µãƒ¼ãƒãƒ¼ã®ãƒ›ã‚¹ãƒˆéµã‚’承èªã™ã‚‹ã“ã¨ã§ã“ã®å•é¡Œã‚’回é¿ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒé€šçŸ¥ã‚’å—ã‘ã¦æ–°è¦ã®ãƒ›ã‚¹ãƒˆéµã‚’承èªã—確証ã—ãŸå¾Œã«èµ·ã“ã‚Šã¾ã™ã€‚ãれ以é™ã®æŽ¥ç¶šã§ã¯ã€ã‚µãƒ¼ãƒãƒ¼ã®ãƒ›ã‚¹ãƒˆéµã¯ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆä¸Šã«ä¿å˜ã—ã¦ã‚ã‚‹æƒ…å ±ã¨ç…§ã‚‰ã—åˆã‚ã›ã¦ãƒã‚§ãƒƒã‚¯ã•ã‚Œã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆãŒæœ¬å½“ã«ç›®çš„ã®ã‚µãƒ¼ãƒãƒ¼ã¨é€šä¿¡ã—ã¦ã„ã‚‹ã“ã¨ã®ç¢ºè¨¼ã‚’与ãˆã¾ã™ã€‚時間ãŒçµŒéŽã—ã¦ã€ã“ã®ãƒ›ã‚¹ãƒˆéµãŒä¸€è‡´ã—ãªã„状態ãŒèµ·ã“ã‚‹ã¨ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«ä¿å˜ã—ã¦ã‚ã‚‹å¤ã„æƒ…å ±ã‚’å‰Šé™¤ã
™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€æ–°ã—ã„接続ãŒå¯èƒ½ã«ãªã‚Šã¾ã™ã€‚
+ </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 の実装によりことなります)、別の鍵交換が発生してもう１つのハッシュ値セットと新しい共有秘密値が生成されます。攻撃者がハッシュ値と共有秘密値を判別できたとしても、その情報はほんの短い時間しか役に立ちません。
+ </div></div><div class="section" id="s2-ssh-protocol-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.4.2. 認証</h4></div></div></div><a id="idm62707168" 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">10.1.4.3. チャネル</h4></div></div></div><a id="idm98799632" class="indexterm"></a><div class="para">
+ SSH 転送層において認証が成功した後、複数のチャネルが<em class="firstterm">多重化</em><a href="#ftn.idm98797104" class="footnote"><sup class="footnote" id="idm98797104">[2]</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.idm98797104" class="footnote"><div class="para"><a href="#idm98797104" class="para"><sup class="para">[2] </sup></a>
+ 多重化された接続は共有された一般的なメディア上で送られる複数の信号から構成されます。SSH では、異なるチャネルが共通のセキュアなコネクション上で送られます。
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>戻る</strong>9.2.9. SSSD Configuration File 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="s1-ssh-configuration.html"><strong>次へ</strong>10.2. OpenSSH の設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-PackageKit.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-PackageKit.html
new file mode 100644
index 0000000..1c6a754
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-PackageKit.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>第5章 PackageKit</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="sec-Additional_Resources.html" title="4.5. その他のリソース" /><link rel="next" href="sec-Using_Add_Remove_Software.html" title="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="sec-Additional_Resources
.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Add_Remove_Software.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="chapter" id="ch-PackageKit" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第5章 PackageKit</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">5.1. ソフトウェアの更新を用いたパッケージの更新</a></span></dt><dd><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Setting_preferences_for_checking_for_updates">5.1.1. 更新の確認間隔の設定</a></span></dt><dt><span class="section"><a href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">5.1.2. ソフトウェアソースの設定</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html">5.2. ソフトウェアの追加/削除の使用</a></span></dt><dd
><dl><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. ソフトウェアソースの更新 (Yum リポジトリー)</a></span></dt><dt><span class="section"><a href="sec-Finding_Packages_with_Filters.html">5.2.2. フィルターを用いたパッケージの検索</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Packages_and_Dependencies.html">5.2.3. パッケージ（および依存するもの）のインストールおよび削除</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Package_Groups.html">5.2.4. パッケージグループのインストールおよび削除</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Transaction_Log.html">5.2.5. トランザクションログの表示</a></span></dt></dl></dd><dt><span class="section"><a href="sec-PackageKit_Architecture.html">5.3. PackageKit アーキテクチャー</a><
/span></dt><dt><span class="section"><a href="ch-Graphical_Package_Management-sec-Additional_Resources.html">5.4. その他のリソース</a></span></dt></dl></div><a id="idm59037680" class="indexterm"></a><a id="idm46440992" class="indexterm"></a><a id="idm28263392" class="indexterm"></a><a id="idm26323456" class="indexterm"></a><a id="idm68997888" class="indexterm"></a><a id="idm45431568" class="indexterm"></a><a id="idm35135008" class="indexterm"></a><a id="idm58490928" class="indexterm"></a><a id="idm27939024" class="indexterm"></a><a id="idm24759072" class="indexterm"></a><a id="idm65692656" class="indexterm"></a><div class="para">
+ Fedora は、あなたのシステムと互換性のあるパッケージを表示、管理、更新、インストールおよびアンインストールするために <span class="application"><strong>PackageKit</strong></span> を提供します。<span class="application"><strong>PackageKit</strong></span> は、GNOME パネルメニューから、または <span class="application"><strong>PackageKit</strong></span> が更新を利用可能であることを通知するときに通知領域から開くことができるグラフィカルインターフェースがいくつかから構成されます。<span class="application"><strong>PackageKit</strong></span> のアーキテクチャーおよび利用可能なフロントエンドの詳細は、<a class="xref" href="sec-PackageKit_Architecture.html">「PackageKit アーキテクチャー」</a>を参照してください。
+ </div><div class="section" id="sec-Updating_Packages_with_Software_Update"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. ソフトウェアの更新を用いたパッケージの更新</h2></div></div></div><a id="idm42111536" class="indexterm"></a><a id="idm42109680" class="indexterm"></a><div class="para">
+ <span class="guimenu"><strong>Activities</strong></span> メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの更新</strong></span>をクリックすることにより、<span class="application"><strong>ソフトウェアの更新</strong></span>を開くことができます。またはシェルプロンプトにおいて、<code class="command">gpk-update-viewer</code> コマンドを実行します。<span class="guilabel"><strong>ソフトウェアの更新</strong></span>ウィンドウにおいて、すべての利用可能な更新を、更新されるパッケージ（<code class="filename">.rpm</code> を除き、CPU アーキテクチャーを含みます）、パッケージの概要、および一般的に更新が提供する変更の概要とともに一覧表示します。インストー
ルしたくないすべての更新は、更新に対応するチェックボックスをチェック解除することにより、ここで選択解除できます。
+ </div><div class="figure" id="fig-Graphical_Package_Management-software_update"><div class="figure-contents"><div class="mediaobject"><img src="images/software-update.png" alt="ソフトウェアの更新を用いたアップデートのインストール" /><div class="longdesc"><div class="para">
+ installing 56 updates with PackageKit's software update window
+ </div></div></div></div><h6>図5.1 ソフトウェアの更新を用いたアップデートのインストール</h6></div><br class="figure-break" /><div class="para">
+ <span class="guilabel"><strong>ソフトウェアの更新</strong></span>ウィンドウのみに表示された更新は、利用可能な更新に対して現在インストールされているパッケージを表しています。
+ <a id="idm43690784" class="indexterm"></a>
+ <a id="idm43688896" class="indexterm"></a>
+ それらのパッケージに依存するもの（システムにある既存のパッケージか新しいものかどちらか）は、<span class="guibutton"><strong>更新のインストール</strong></span>をクリックするまで表示されません。
+ </div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> <a id="idm68929600" class="indexterm"></a>
+ <a id="idm68927712" class="indexterm"></a>
+ <a id="idm68926304" class="indexterm"></a>
+ は、システムに変更を加える要求をするときは必ず <span class="application"><strong>PolicyKit</strong></span> ツールキットにより提供される精密なユーザー認証
+ <a id="idm68924928" class="indexterm"></a>
+ 機能を使用します。<span class="application"><strong>PackageKit</strong></span> にパッケージの更新、インストールまたは削除を指示すると必ず、システムに変更を加える前にスーパーユーザーのパスワードを入力するよう要求されます。
+ </div><div class="para">
+ <code class="filename">kernel</code> パッケージを更新するよう <span class="application"><strong>PackageKit</strong></span> に指示すると、インストール後にプロンプトが表示され、システムを再起動して、新しくインストールしたカーネルから起動したいかどうかを尋ねられます。
+ </div><div class="section" id="sec-Setting_preferences_for_checking_for_updates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.1.1. 更新の確認間隔の設定</h3></div></div></div><a id="idm52096304" class="indexterm"></a><div class="para">
+ <span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>その他</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの更新</strong></span>を選択することにより、<span class="guilabel"><strong>ソフトウェアの更新の設定</strong></span>ウィンドウが開きます。<span class="guilabel"><strong>更新の設定</strong></span>タブにより、<span class="application"><strong>PackageKit</strong></span> がパッケージの更新を確認する間隔、およびすべての更新またはセキュリティ更新のみを自動的にインストールするかどうかを定義できます。<span class="guilabel"><strong>モバイル接続を使用するとき更新を確認する</strong></span>ボックスをチェック解除しておくことにより、ダウンロードするデータ
量に対して課金される無線接続を使用しているときに、膨大な帯域使用を避けるために適しています。
+ </div><div class="figure" id="fig-Graphical_Package_Management-Software_Update_Preferences"><div class="figure-contents"><div class="mediaobject"><img src="images/software-update-preferences.png" alt="PackageKit の更新の確認間隔の設定" /><div class="longdesc"><div class="para">
+ Setting the update-checking interval for PackageKit
+ </div></div></div></div><h6>図5.2 PackageKit の更新の確認間隔の設定</h6></div><br class="figure-break" /></div><div class="section" id="sec-Setting_preferences_for_software_sources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.1.2. ソフトウェアソースの設定</h3></div></div></div><div class="para">
+ ソフトウェアの更新をインストールするために使用するパッケージリポジトリを選択するには、<span class="guimenu"><strong>Activities</strong></span> メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>その他</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの更新</strong></span>を選択し、<span class="guilabel"><strong>ソフトウェアの更新の設定</strong></span>の<span class="guilabel"><strong>ソフトウェアのソース</strong></span>をクリックします。
+ </div><div class="figure" id="fig-Graphical_Package_Management-Software_Update_Software_Sources"><div class="figure-contents"><div class="mediaobject"><img src="images/software-update-software-sources.png" alt="PackageKit のソフトウェアソースの設定" /><div class="longdesc"><div class="para">
+ Setting the software sources for PackageKit
+ </div></div></div></div><h6>図5.3 PackageKit のソフトウェアソースの設定</h6></div><br class="figure-break" /><a id="idm72666736" class="indexterm"></a><a id="idm43785440" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> はソフトウェアのソースとして\n <span class="application"><strong>Yum</strong></span> リポジトリを参照します。すべてのソフトウェアを有効なソフトウェアのソースから取得します。<span class="guilabel"><strong>ソフトウェアのソース</strong></span>タブは、<code class="filename">/etc/yum.conf</code> 設定ファイルおよび <code class="filename">/etc/yum.repos.d/</code> ディレクトリにあるすべての <code class="filename"><em class="replaceable"><code>repository</code></em>.repo</code> にあるすべての [<em class="replaceable"><code>repository</code></em>] セクションの <code class="computeroutput">name=<em class="replaceable"><code>My Repository Name</code></em></code> 項目に書かれているようにリポジトリ名を表示します。
+ </div><div class="para">
+ <span class="guilabel"><strong>有効化</strong></span>ã®åˆ—ã«ãƒã‚§ãƒƒã‚¯ãŒã¤ã„ã¦ã„ã‚‹é …ç›®ã¯ã€å¯¾å¿œã™ã‚‹ãƒªãƒã‚¸ãƒˆãƒªãŒã™ã¹ã¦ã®æ›´æ–°ã¨ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã®è¦æ±‚（ä¾å˜é–¢ä¿‚ã®è§£æ±ºã‚’å«ã‚）を満ãŸã™ãƒ‘ッケージã®ä½ç½®ã‚’決ã‚ã‚‹ãŸã‚ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚<span class="guilabel"><strong>有効化</strong></span>ã®åˆ—㯠[<em class="replaceable"><code>repository</code></em>] セクションã«ãŠã‘ã‚‹ <code class="computeroutput">enabled=<em class="replaceable"><code><1 ã¾ãŸã¯ 0></code></em></code> é …ç›®ã«å¯¾å¿œã—ã¾ã™ã€‚ãƒã‚§ãƒƒã‚¯ãƒœãƒƒã‚¯ã‚¹ã‚’ãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€Yum リãƒã‚¸ãƒˆãƒªã‚’有効ã«ã—ã¾ã™ã€‚ã¾ãŸã€ãƒã‚§ãƒƒã‚¯è§£é™¤ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šç„¡åŠ¹ã«ã—ã¾ã™ã€‚リãƒã‚¸ãƒˆãƒªã‚’有効ã¾ãŸã¯ç„¡åŠ¹ã«ã™ã‚‹ã©ã¡ã‚‰ã‹ã®æ©Ÿèƒ½ã‚’実行ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€<span class="application"><strong>PolicyKit</strong></span> ãŒã‚¹ãƒ¼ãƒ‘ーユーザーã®èªè¨¼ã‚’ダイアãƒã‚°ã«è¦æ±‚ã
—ã¾ã™ã€‚<span class="application"><strong>PackageKit</strong></span> ã¯å®Ÿéš›ã« <code class="literal">enabled=<em class="replaceable"><code><1 ã¾ãŸã¯ 0></code></em></code> ãŒå˜åœ¨ã—ãªã‘ã‚Œã°ãã®è¡Œã‚’é©åˆ‡ãª [<em class="replaceable"><code>repository</code></em>] セクションã«æŒ¿å…¥ã—ã¾ã™ã€‚ã¾ãŸã¯ã€å˜åœ¨ã™ã‚Œã°å€¤ã‚’変更ã—ã¾ã™ã€‚ã¤ã¾ã‚Šã€<span class="guilabel"><strong>ソフトウェアã®ã‚½ãƒ¼ã‚¹</strong></span>ウィンドウを通ã—ã¦ãƒªãƒã‚¸ãƒˆãƒªã‚’有効化ã¾ãŸã¯ç„¡åŠ¹åŒ–ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚¦ã‚£ãƒ³ãƒ‰ã‚¦ã‚’é–‰ã˜ãŸå¾Œã¾ãŸã¯ã‚·ã‚¹ãƒ†ãƒ ã‚’å†èµ·å‹•ã—ãŸå¾Œã«å¤‰æ›´ã‚’永続化ã•ã›ã¾ã™ã€‚å¿…è¦ã«å¿œã˜ã¦ãƒªãƒã‚¸ãƒˆãƒªã‚’ç°¡å˜ã«æœ‰åŠ¹åŒ–ã¾ãŸã¯ç„¡åŠ¹åŒ–ã™ã‚‹æ©Ÿèƒ½ã¯ <span class="application"><strong>PackageKit</strong></span> ã®éžå¸¸ã«ä¾¿åˆ©ãªæ©Ÿèƒ½ã§ã™ã€‚
+ </div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> を通して <span class="application"><strong>Yum</strong></span> リポジトリの追加または削除ができないことに注意してください。
+ </div><div class="note" id="note-Showing_Source_RPM_and_Test_Repositories"><div class="admonition_header"><h2>source RPM, test, および debuginfo リポジトリの表示</h2></div><div class="admonition"><div class="para">
+ <span class="guilabel"><strong>ソフトウェアのソース</strong></span> タブの下部にあるボックスをチェックすることにより、<span class="application"><strong>PackageKit</strong></span> が source RPM, testing および debuginfo リポジトリを同じように表示するようになります。このボックスはデフォルトでチェックされていません。
+ </div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Additional_Resources.html"><strong>戻る</strong>4.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="sec-Using_Add_Remove_Software.html"><strong>次へ</strong>5.2. ソフトウェアの追加/削除の使用</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-RPM.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-RPM.html
new file mode 100644
index 0000000..73e5dd7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-RPM.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>付録B 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="sect-Consistent_Network_Device_Naming-Notes.html" title="A.4. Notes for Administrators" /><link rel="next" href="s1-rpm-using.html" title="B.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="sect-Consistent_Network_Device_Naming-Notes.html"><strong>戻る</strong></
a></li><li 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="idm69276576" class="indexterm"></a><a id="idm69277344" class="indexterm"></a><div class="para">
+ The <em class="firstterm">RPM Package Manager</em> (RPM) is an open packaging system
+ <a id="idm69278912" class="indexterm"></a>
+ , which runs on Fedora as well as other Linux and UNIX systems. Red Hat, Inc. and the Fedora Project encourage other vendors to use RPM for their own products. RPM 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 RPM Package Manager only works with packages built to work with the <span class="emphasis"><em>RPM format</em></span>. RPM is itself provided as a pre-installed <span class="package">rpm</span> package. For the end user, RPM makes system updates easy. Installing, uninstalling and upgrading RPM packages can be accomplished with short commands. RPM maintains a database of installed packages and their files, so you can invoke powerful queries and verifications on your system.
+ </div><div class="para">
+ The RPM package format has been improved for Fedora 17. RPM packages are now compressed using the XZ lossless data compression format, which has the benefit of greater compression and less CPU usage during decompression, and support multiple strong hash algorithms, such as SHA-256, for package signing and verification.
+ </div><div class="warning" id="warning-Use_Yum_Instead_of_RPM_Whenever_Possible"><div class="admonition_header"><h2>Use Yum Instead of RPM Whenever Possible</h2></div><div class="admonition"><div class="para">
+ For most package management tasks, the <span class="application"><strong>Yum</strong></span> package manager offers equal and often greater capabilities and utility than RPM
+ <a id="idm40967776" class="indexterm"></a>
+ . <span class="application"><strong>Yum</strong></span> also performs and tracks complicated system dependency resolution, and will complain and force system integrity checks if you use RPM as well to install and remove packages. For these reasons, it is highly recommended that you use <span class="application"><strong>Yum</strong></span> instead of RPM whenever possible to perform package management tasks. Refer to <a class="xref" href="ch-yum.html">4章<em>Yum</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>Yum</strong></span> as its back end, to manage your system's packages. Refer to <a class="xref" href="ch-PackageKit.html">5章<em>PackageKit</em></a> for details.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Install RPM packages with the correct architecture!</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. Many of the following examples show RPM packages compiled for the AMD64/Intel 64 computer architectures; thus, the RPM file name ends in <code class="filename">x86_64.rpm</code>.
+ </div></div></div><div class="para">
+ During upgrades, RPM 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><div class="para">
+ For the developer, RPM allows you to take software source code and package it into source and binary packages for end users.
+ <a id="idm24605616" class="indexterm"></a>
+ This process is quite simple and is driven from a single file and optional patches that you create. This clear delineation between <em class="firstterm">pristine</em> 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"><div class="admonition_header"><h2>Running rpm commands must be performed as root</h2></div><div class="admonition"><div class="para">
+ Because RPM makes changes to your system, you must be logged in as root to install, remove, or upgrade an RPM package.
+ </div></div></div><div class="section" id="s1-rpm-design"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.1. RPM の設計目標</h2></div></div></div><a id="idm150306944" class="indexterm"></a><div class="para">
+ To understand how to use RPM, it can be helpful to understand the design goals of RPM:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Upgradability
+ <a id="idm150309680" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ With RPM, you can upgrade individual components of your system without completely reinstalling. When you get a new release of an operating system based on RPM, such as Fedora, you do not need to reinstall a fresh copy of the operating system your machine (as you might need to with operating systems based on other packaging systems). RPM allows 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 RPM file is used to both install and upgrade the package on your system.
+ </div></dd><dt class="varlistentry"><span class="term">Powerful Querying
+ <a id="idm58045408" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ RPM is designed to provide powerful querying options. You can perform searches on your entire database for packages or even just certain files. You can also easily find out what package a file belongs to and from where the package came. The files an RPM 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"> System Verification
+ <a id="idm43808576" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Another powerful RPM feature is the ability to verify packages. If you are worried that you deleted an important file for some package, you can verify the package. You are then notified of anomalies, if any—at which point 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">Pristine Sources
+ <a id="idm56916128" class="indexterm"></a>
+ </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 RPM, 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, too.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Consistent_Network_Device_Naming-Notes.html"><strong>戻る</strong>A.4. Notes for Administrators</a></li><li class="up"><a accesskey="u" href="#"><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>B.2. RPMの使用法</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Services_and_Daemons.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Services_and_Daemons.html
new file mode 100644
index 0000000..fbb87cd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>第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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Infrastructure_Services.html" title="パート IV. インフラストラクチャーサービス" /><link rel="prev" href="part-Infrastructure_Services.html" title="パート IV. インフラストラクチャーサービス" /><link rel="next" href="s1-services-running.html" title="8.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">第8章 サービスおよびデーモン</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">8.1. サービスの設定</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">8.1.1. サービスの有効化</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">8.1.2. サービスの無効化</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">8.2. サービスの実行</a></span></dt><dd><dl><dt><span class="section"><a href="s1-s
ervices-running.html#s3-services-running-checking">8.2.1. サービスの状態の確認</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">8.2.2. サービスの実行</a></span></dt><dt><span class="section"><a href="s3-services-running-stopping.html">8.2.3. サービスの停止</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">8.2.4. サービスの再起動</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">8.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">8.3.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">8.3.2. 関連書籍</a></span></dt></dl></dd></dl></div><a id="idm48745888" 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 17 <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">8.1. サービスの設定</h2></div></div></div><a id="idm42728976" class="indexterm"></a><a id="idm10163984" 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 17 のインストール中にインストールされ設定されています。<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">8.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>例8.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">8.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>例8.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>パート 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="s1-services-running.html"><strong>次へ</strong>8.2. サービスの実行</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html
new file mode 100644
index 0000000..2efe17e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Monitoring_and_Automation.html" title="パート VI. 監視および自動化" /><link rel="prev" href="part-Monitoring_and_Automation.html" title="パート VI. 監視および自動化" /><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_Autom
ation.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><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 cl
ass="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. U
sing 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 Comma
nd</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 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></div><a id="idm42416064" class="indexterm"></a><a id="idm26480096" 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="idm21046256" class="indexterm"></a><a id="idm69581728" 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="idm83090128" 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="idm28372832" class="indexterm"></a><a id="idm28370912" 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="idm50308512" class="indexterm"></a><a id="idm50307392" 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>パート 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="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/17/html/System_Administrators_Guide/ch-The_X_Window_System.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-The_X_Window_System.html
new file mode 100644
index 0000000..991e856
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-The_X_Window_System.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>付録C X Window 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s2-rpm-related-books.html" title="B.5.3. 関連書籍" /><link rel="next" href="s1-x-clients.html" title="C.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-rpm-related-books.html"><strong>戻る</strong></a></li><li cla
ss="next"><a accesskey="n" href="s1-x-clients.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="appendix" id="ch-The_X_Window_System" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">X Window System</h1></div></div></div><a id="idm17617920" class="indexterm"></a><a id="idm66857680" class="indexterm"></a><a id="idm75197136" class="indexterm"></a><a id="idm24990352" class="indexterm"></a><a id="idm47601728" class="indexterm"></a><div class="para">
+ While the heart of Fedora is the kernel, for many users, the face of the operating system is the graphical environment provided by the <em class="firstterm">X Window System</em>, also called <em class="firstterm">X</em>.
+ </div><div class="para">
+ Other windowing environments have existed in the UNIX world, including some that predate the release of the X Window System in June 1984. Nonetheless, X has been the default graphical environment for most UNIX-like operating systems, including Fedora, for many years.
+ </div><div class="para">
+ The graphical environment for Fedora is supplied by the <em class="firstterm">X.Org Foundation</em>, an open source organization created to manage development and strategy for the X Window System and related technologies. X.Org is a large-scale, rapid-developing project with hundreds of developers around the world. It features a wide degree of support for a variety of hardware devices and architectures, and runs on myriad operating systems and platforms.
+ </div><div class="para">
+ The X Window System uses a client-server architecture. Its main purpose is to provide network transparent window system, which runs on a wide range of computing and graphics machines. The <em class="firstterm">X server</em> (the <code class="command">Xorg</code> binary) listens for connections from <em class="firstterm">X client</em> applications via a network or local loopback interface. The server communicates with the hardware, such as the video card, monitor, keyboard, and mouse. X client applications exist in the user space, creating a <em class="firstterm">graphical user interface</em> (<em class="firstterm">GUI</em>) for the user and passing user requests to the X server.
+ </div><div class="section" id="s1-x-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.1. The X Server</h2></div></div></div><a id="idm43858416" class="indexterm"></a><div class="para">
+ Fedora 17 uses X server version, which includes several video drivers, EXA, and platform support enhancements over the previous release, among others. In addition, this release includes several automatic configuration features for the X server, as well as the generic input driver, <code class="systemitem">evdev</code>, that supports all input devices that the kernel knows about, including most mice and keyboards.
+ </div><div class="para">
+ X11R7.1 was the first release to take specific advantage of the modularization of the X Window System. With it, X is split into logically distinct modules, which make it easier for open source developers to contribute code to the system.
+ </div><div class="para">
+ In the current release, all libraries, headers, and binaries live under the <code class="filename">/usr/</code> directory. The <code class="filename">/etc/X11/</code> directory contains configuration files for X client and server applications. This includes configuration files for the X server itself, the X display managers, and many other base components.
+ </div><div class="para">
+ The configuration file for the newer Fontconfig-based font architecture is still <code class="filename">/etc/fonts/fonts.conf</code>. For more information on configuring and adding fonts, refer to <a class="xref" href="s1-x-fonts.html">「フォント」</a>.
+ </div><div class="para">
+ Because the X server performs advanced tasks on a wide array of hardware, it requires detailed information about the hardware it works on. The X server is able to automatically detect most of the hardware that it runs on and configure itself accordingly. Alternatively, hardware can be manually specified in configuration files.
+ </div><div class="para">
+ The Fedora system installer, Anaconda, installs and configures X automatically, unless the X packages are not selected for installation. If there are any changes to the monitor, video card or other devices managed by the X server, most of the time, X detects and reconfigures these changes automatically. In rare cases, X must be reconfigured manually.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-related-books.html"><strong>戻る</strong>B.5.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-x-clients.html"><strong>次へ</strong>C.2. デスクトップ環境とウィンドウマネージャ</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-The_sysconfig_Directory.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-The_sysconfig_Directory.html
new file mode 100644
index 0000000..e172205
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-The_sysconfig_Directory.html
@@ -0,0 +1,335 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>付録D sysconfig ディレクトリー</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s2-x-useful-websites.html" title="C.5.2. 役に立つ Web サイト" /><link rel="next" href="s1-sysconfig-etcsysconf-dir.html" title="D.2. Directories in the /etc/sysconfig/ 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-x-useful-websites.html"><strong>戻る</strong>
</a></li><li class="next"><a accesskey="n" href="s1-sysconfig-etcsysconf-dir.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="appendix" id="ch-The_sysconfig_Directory" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">sysconfig ディレクトリー</h1></div></div></div><a id="idm42035248" class="indexterm"></a><a id="idm24761504" class="indexterm"></a><div class="para">
+ This appendix outlines some of the files and directories found in the <code class="filename">/etc/sysconfig/</code> directory, their function, and their contents. The information in this appendix is not intended to be complete, as many of these files have a variety of options that are only used in very specific or rare circumstances.
+ </div><div class="note"><div class="admonition_header"><h2>The content of the /etc/sysconfig/ directory</h2></div><div class="admonition"><div class="para">
+ <code class="filename">/etc/sysconfig/</code> ディレクトリーの実際の内容は、マシンにインストールされているプログラムに依存します。設定ファイルが含まれるパッケージの名前を見つけるには、シェルプロンプトにおいて次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">yum provides /etc/sysconfig/<em class="replaceable"><code>filename</code></em> </code>
+</pre><div class="para">
+ Fedora にある新しいパッケージをインストールする方法に関する詳細は <a class="xref" href="sec-Installing.html">「パッケージのインストール」</a> を参照してください。
+ </div></div></div><div class="section" id="s1-sysconfig-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">D.1. Files in the /etc/sysconfig/ Directory</h2></div></div></div><a id="idm75023824" class="indexterm"></a><div class="para">
+ The following sections offer descriptions of files normally found in the <code class="filename">/etc/sysconfig/</code> directory.
+ </div><div class="section" id="s2-sysconfig-arpwatch"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.1. /etc/sysconfig/arpwatch </h3></div></div></div><a id="idm52702144" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/arpwatch</code> file is used to pass arguments to the <code class="command">arpwatch</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">arpwatch</code> daemon. For example:
+ </div><pre class="screen">OPTIONS="-u arpwatch -e root -s 'root (Arpwatch)'"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-authconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.2. /etc/sysconfig/authconfig </h3></div></div></div><a id="idm36879024" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/authconfig</code> file sets the authorization to be used on the host. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">USEMKHOMEDIR=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) creating a home directory for a user on the first login. For example:
+ </div><pre class="screen">USEMKHOMEDIR=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEPAMACCESS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the PAM authentication. For example:
+ </div><pre class="screen">USEPAMACCESS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESSSDAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the SSSD authentication. For example:
+ </div><pre class="screen">USESSSDAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESHADOW=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) shadow passwords. For example:
+ </div><pre class="screen">USESHADOW=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEWINBIND=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using Winbind for user account configuration. For example:
+ </div><pre class="screen">USEWINBIND=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEDB=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the FAS authentication. For example:
+ </div><pre class="screen">USEDB=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEFPRINTD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the fingerprint authentication. For example:
+ </div><pre class="screen">USEFPRINTD=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">FORCESMARTCARD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) enforcing the smart card authentication. For example:
+ </div><pre class="screen">FORCESMARTCARD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PASSWDALGORITHM=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The password algorithm. The <em class="replaceable"><code>value</code></em> can be <code class="option">bigcrypt</code>, <code class="option">descrypt</code>, <code class="option">md5</code>, <code class="option">sha256</code>, or <code class="option">sha512</code>. For example:
+ </div><pre class="screen">PASSWDALGORITHM=sha512</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELDAPAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the LDAP authentication. For example:
+ </div><pre class="screen">USELDAPAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELOCAUTHORIZE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the local authorization for local users. For example:
+ </div><pre class="screen">USELOCAUTHORIZE=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USECRACKLIB=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the CrackLib. For example:
+ </div><pre class="screen">USECRACKLIB=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEWINBINDAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the Winbind authentication. For example:
+ </div><pre class="screen">USEWINBINDAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESMARTCARD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the smart card authentication. For example:
+ </div><pre class="screen">USESMARTCARD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELDAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using LDAP for user account configuration. For example:
+ </div><pre class="screen">USELDAP=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USENIS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using NIS for user account configuration. For example:
+ </div><pre class="screen">USENIS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEKERBEROS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the Kerberos authentication. For example:
+ </div><pre class="screen">USEKERBEROS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESYSNETAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) authenticating system accounts with network services. For example:
+ </div><pre class="screen">USESYSNETAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESMBAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the SMB authentication. For example:
+ </div><pre class="screen">USESMBAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESSSD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using SSSD for obtaining user information. For example:
+ </div><pre class="screen">USESSSD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEHESIOD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the Hesoid name service. For example:
+ </div><pre class="screen">USEHESIOD=no</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-Configuring_Authentication.html">9章<em>認証の設定</em></a> for more information on this topic.
+ </div></div><div class="section" id="s2-sysconfig-autofs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.3. /etc/sysconfig/autofs </h3></div></div></div><a id="idm36593168" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/autofs</code> file defines custom options for the automatic mounting of devices. This file controls the operation of the automount daemons, which automatically mount file systems when you use them and unmount them after a period of inactivity. File systems can include network file systems, CD-ROM drives, diskettes, and other media.
+ </div><div class="para">
+ By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">MASTER_MAP_NAME=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default name for the master map. For example:
+ </div><pre class="screen">MASTER_MAP_NAME="auto.master"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default mount timeout. For example:
+ </div><pre class="screen">TIMEOUT=300</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">NEGATIVE_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default negative timeout for unsuccessful mount attempts. For example:
+ </div><pre class="screen">NEGATIVE_TIMEOUT=60</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOUNT_WAIT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for a response from <code class="command">mount</code>. For example:
+ </div><pre class="screen">MOUNT_WAIT=-1</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">UMOUNT_WAIT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for a response from <code class="command">umount</code>. For example:
+ </div><pre class="screen">UMOUNT_WAIT=12</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">BROWSE_MODE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) browsing the maps. For example:
+ </div><pre class="screen">BROWSE_MODE="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOUNT_NFS_DEFAULT_PROTOCOL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default protocol to be used by <code class="command">mount.nfs</code>. For example:
+ </div><pre class="screen">MOUNT_NFS_DEFAULT_PROTOCOL=4</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">APPEND_OPTIONS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) appending the global options instead of replacing them. For example:
+ </div><pre class="screen">APPEND_OPTIONS="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LOGGING=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default logging level. The <em class="replaceable"><code>value</code></em> has to be either <code class="option">none</code>, <code class="option">verbose</code>, or <code class="option">debug</code>. For example:
+ </div><pre class="screen">LOGGING="none"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_URI=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of server URIs in the form of <code class="systemitem"><em class="replaceable"><code>protocol</code></em>://<em class="replaceable"><code>server</code></em> </code>. For example:
+ </div><pre class="screen">LDAP_URI="ldaps://ldap.example.com/"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The synchronous API calls timeout. For example:
+ </div><pre class="screen">LDAP_TIMEOUT=-1</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_NETWORK_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The network response timeout. For example:
+ </div><pre class="screen">LDAP_NETWORK_TIMEOUT=8</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SEARCH_BASE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The base Distinguished Name (DN) for the map search. For example:
+ </div><pre class="screen">SEARCH_BASE=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">AUTH_CONF_FILE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default location of the SASL authentication configuration file. For example:
+ </div><pre class="screen">AUTH_CONF_FILE="/etc/autofs_ldap_auth.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MAP_HASH_TABLE_SIZE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The hash table size for the map cache. For example:
+ </div><pre class="screen">MAP_HASH_TABLE_SIZE=1024</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USE_MISC_DEVICE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the autofs miscellaneous device. For example:
+ </div><pre class="screen">USE_MISC_DEVICE="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the LDAP daemon. For example:
+ </div><pre class="screen">OPTIONS=""</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-clock"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.4. /etc/sysconfig/clock </h3></div></div></div><a id="idm47334480" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/clock</code> file controls the interpretation of values read from the system hardware clock. It is used by the <span class="application"><strong>Date and Time</strong></span> configuration tool, and should not be edited by hand. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">ZONE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time zone file under <code class="filename">/usr/share/zoneinfo</code> that <code class="filename">/etc/localtime</code> is a copy of. For example:
+ </div><pre class="screen">ZONE="Europe/Prague"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">「日付と時刻の設定ツールの使い方」</a> for more information on the <span class="application"><strong>Date and Time</strong></span> configuration tool and its usage.
+ </div></div><div class="section" id="s2-sysconfig-dhcpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.5. /etc/sysconfig/dhcpd </h3></div></div></div><a id="idm31669088" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/dhcpd</code> file is used to pass arguments to the <code class="command">dhcpd</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">DHCPDARGS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">dhcpd</code> daemon. For example:
+ </div><pre class="screen">DHCPDARGS=</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-DHCP_Servers.html">11章<em>DHCP サーバー</em></a> for more information on DHCP and its usage.
+ </div></div><div class="section" id="s2-sysconfig-firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.6. /etc/sysconfig/firstboot </h3></div></div></div><a id="idm28733200" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/firstboot</code> file defines whether to run the <code class="command">firstboot</code> utility. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">RUN_FIRSTBOOT=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">YES</code>) or disable (<code class="option">NO</code>) running the <code class="command">firstboot</code> program. For example:
+ </div><pre class="screen">RUN_FIRSTBOOT=NO</pre></dd></dl></div><div class="para">
+ The first time the system boots, the <code class="command">init</code> program calls the <code class="filename">/etc/rc.d/init.d/firstboot</code> script, which looks for the <code class="filename">/etc/sysconfig/firstboot</code> file. If this file does not contain the <code class="option">RUN_FIRSTBOOT=NO</code> option, the <code class="command">firstboot</code> program is run, guiding a user through the initial configuration of the system.
+ </div><div class="note"><div class="admonition_header"><h2>You can run the firstboot program again</h2></div><div class="admonition"><div class="para">
+ To start the <code class="command">firstboot</code> program the next time the system boots, change the value of <code class="command">RUN_FIRSTBOOT</code> option to <code class="option">YES</code>, and type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl enable firstboot.service</code>
+</pre></div></div></div><div class="section" id="s2-sysconfig-i18n"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.7. /etc/sysconfig/i18n </h3></div></div></div><div class="para">
+ The <code class="filename">/etc/sysconfig/i18n</code> configuration file defines the default language, any supported languages, and the default system font. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">LANG=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default language. For example:
+ </div><pre class="screen">LANG="en_US.UTF-8"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SUPPORTED=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A colon-separated list of supported languages. For example:
+ </div><pre class="screen">SUPPORTED="en_US.UTF-8:en_US:en"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SYSFONT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default system font. For example:
+ </div><pre class="screen">SYSFONT="latarcyrheb-sun16"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-init"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.8. /etc/sysconfig/init </h3></div></div></div><a id="idm42388384" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/init</code> file controls how the system appears and functions during the boot process. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">BOOTUP=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The bootup style. The value has to be either <code class="option">color</code> (the standard color boot display), <code class="option">verbose</code> (an old style display which provides more information), or anything else for the new style display, but without ANSI formatting. For example:
+ </div><pre class="screen">BOOTUP=color</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RES_COL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The number of the column in which the status labels start. For example:
+ </div><pre class="screen">RES_COL=60</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOVE_TO_COL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to move the cursor to the column specified in <code class="option">RES_COL</code> (see above). For example:
+ </div><pre class="screen">MOVE_TO_COL="echo -en \\033[${RES_COL}G"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_SUCCESS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the success color. For example:
+ </div><pre class="screen">SETCOLOR_SUCCESS="echo -en \\033[0;32m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_FAILURE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the failure color. For example:
+ </div><pre class="screen">SETCOLOR_FAILURE="echo -en \\033[0;31m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_WARNING=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the warning color. For example:
+ </div><pre class="screen">SETCOLOR_WARNING="echo -en \\033[0;33m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_NORMAL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the default color. For example:
+ </div><pre class="screen">SETCOLOR_NORMAL="echo -en \\033[0;39m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LOGLEVEL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The initial console logging level. The <em class="replaceable"><code>value</code></em> has to be in the range from <code class="option">1</code> (kernel panics only) to <code class="option">8</code> (everything, including the debugging information). For example:
+ </div><pre class="screen">LOGLEVEL=3</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PROMPT=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the hotkey interactive startup. For example:
+ </div><pre class="screen">PROMPT=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">AUTOSWAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) probing for devices with swap signatures. For example:
+ </div><pre class="screen">AUTOSWAP=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ACTIVE_CONSOLES=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The list of active consoles. For example:
+ </div><pre class="screen">ACTIVE_CONSOLES=/dev/tty[1-6]</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SINGLE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The single-user mode type. The <em class="replaceable"><code>value</code></em> has to be either <code class="option">/sbin/sulogin</code> (a user will be prompted for a password to log in), or <code class="option">/sbin/sushell</code> (the user will be logged in directly). For example:
+ </div><pre class="screen">SINGLE=/sbin/sushell</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-ip6tables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.9. /etc/sysconfig/ip6tables-config </h3></div></div></div><a id="idm50138832" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ip6tables-config</code> file stores information used by the kernel to set up IPv6 packet filtering at boot time or whenever the <code class="command">ip6tables</code> service is started. Note that you should not modify it unless you are familiar with <code class="command">ip6tables</code> rules. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_MODULES=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of helpers to be loaded after the firewall rules are applied. For example:
+ </div><pre class="screen">IP6TABLES_MODULES="ip_nat_ftp ip_nat_irc"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_MODULES_UNLOAD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) module unloading when the firewall is stopped or restarted. For example:
+ </div><pre class="screen">IP6TABLES_MODULES_UNLOAD="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_ON_STOP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the current firewall rules when the firewall is stopped. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_ON_STOP="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_ON_RESTART=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the current firewall rules when the firewall is restarted. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_ON_RESTART="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_COUNTER=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the rule and chain counters. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_COUNTER="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_NUMERIC=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing IP addresses and port numbers in a numeric format in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_NUMERIC="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_VERBOSE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing information about the number of packets and bytes in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_VERBOSE="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_LINENUMBERS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing line numbers in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_LINENUMBERS="yes"</pre></dd></dl></div><div class="para">
+ </div><div class="note"><div class="admonition_header"><h2>Use the ip6tables command to create the rules</h2></div><div class="admonition"><div class="para">
+ You can create the rules manually using the <code class="command">ip6tables</code> command. Once created, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service ip6tables save</code>
+</pre><div class="para">
+ This will add the rules to <code class="filename">/etc/sysconfig/ip6tables</code>. Once this file exists, any firewall rules saved in it persist through a system reboot or a service restart.
+ </div></div></div></div><div class="section" id="s2-sysconfig-kybd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.10. /etc/sysconfig/keyboard </h3></div></div></div><a id="idm49671040" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/keyboard</code> file controls the behavior of the keyboard. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">KEYTABLE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The name of a keytable file. The files that can be used as keytables start in the <code class="filename">/lib/kbd/keymaps/i386/</code> directory, and branch into different keyboard layouts from there, all labeled <code class="filename"><em class="replaceable"><code>value</code></em>.kmap.gz</code>. The first file name that matches the <code class="option">KEYTABLE</code> setting is used. For example:
+ </div><pre class="screen">KEYTABLE="us"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MODEL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard model. For example:
+ </div><pre class="screen">MODEL="pc105+inet"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LAYOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard layout. For example:
+ </div><pre class="screen">LAYOUT="us"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">KEYBOARDTYPE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard type. Allowed values are <code class="option">pc</code> (a PS/2 keyboard), or <code class="option">sun</code> (a Sun keyboard). For example:
+ </div><pre class="screen">KEYBOARDTYPE="pc"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.11. /etc/sysconfig/ldap </h3></div></div></div><a id="idm33896880" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ldap</code> file holds the basic configuration for the LDAP server. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">slapd</code> daemon. For example:
+ </div><pre class="screen">SLAPD_OPTIONS="-4"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLURPD_OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">slurpd</code> daemon. For example:
+ </div><pre class="screen">SLURPD_OPTIONS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over TCP (that is, <code class="systemitem">ldap:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAP="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAPI=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over IPC (that is, <code class="systemitem">ldapi:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAPI="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAPS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over TLS (that is, <code class="systemitem">ldaps:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAPS="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_URLS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of URLs. For example:
+ </div><pre class="screen">SLAPD_URLS="ldapi:///var/lib/ldap_root/ldapi ldapi:/// ldaps:///"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_SHUTDOWN_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for <code class="command">slapd</code> to shut down. For example:
+ </div><pre class="screen">SLAPD_SHUTDOWN_TIMEOUT=3</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_ULIMIT_SETTINGS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The parameters to be passed to <code class="command">ulimit</code> before the <code class="command">slapd</code> daemon is started. For example:
+ </div><pre class="screen">SLAPD_ULIMIT_SETTINGS=""</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-Directory_Servers.html#s1-OpenLDAP">「OpenLDAP」</a> for more information on LDAP and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-named"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.12. /etc/sysconfig/named </h3></div></div></div><a id="idm51408192" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/named</code> file is used to pass arguments to the <code class="command">named</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">ROOTDIR=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The chroot environment under which the <code class="command">named</code> daemon runs. The <em class="replaceable"><code>value</code></em> has to be a full directory path. For example:
+ </div><pre class="screen">ROOTDIR="/var/named/chroot"</pre><div class="para">
+ Note that the chroot environment has to be configured first (type <code class="command">info chroot</code> at a shell prompt for more information).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">named</code>. For example:
+ </div><pre class="screen">OPTIONS="-6"</pre><div class="para">
+ Note that you should not use the <code class="option">-t</code> option. Instead, use <code class="option">ROOTDIR</code> as described above.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">KEYTAB_FILE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keytab file name. For example:
+ </div><pre class="screen">KEYTAB_FILE="/etc/named.keytab"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="s1-BIND.html">「BIND」</a> for more information on the BIND DNS server and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-network"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.13. /etc/sysconfig/network</h3></div></div></div><a id="idm43033920" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/network</code> file is used to specify information about the desired network configuration. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">NETWORKING=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the networking. For example:
+ </div><pre class="screen">NETWORKING=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">HOSTNAME=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The hostname of the machine. For example:
+ </div><pre class="screen">HOSTNAME=penguin.example.com</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">GATEWAY=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The IP address of the network's gateway. For example:
+ </div><pre class="screen">GATEWAY=192.168.1.0</pre></dd></dl></div><div class="warning"><div class="admonition_header"><h2>Avoid using custom init scripts</h2></div><div class="admonition"><div class="para">
+ Do not use custom init scripts to configure network settings. When performing a post-boot network service restart, custom init scripts configuring network settings that are run outside of the network init script lead to unpredictable results.
+ </div></div></div></div><div class="section" id="s2-sysconfig-ntpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.14. /etc/sysconfig/ntpd </h3></div></div></div><a id="idm36696720" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ntpd</code> file is used to pass arguments to the <code class="command">ntpd</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">ntpd</code>. For example:
+ </div><pre class="screen">OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid -g"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html">「Network Time Protocol の設定」</a> for more information on how to configure the <code class="command">ntpd</code> daemon.
+ </div></div><div class="section" id="s2-sysconfig-quagga"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.15. /etc/sysconfig/quagga </h3></div></div></div><a id="idm28044112" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/quagga</code> file holds the basic configuration for Quagga daemons. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">QCONFDIR=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The directory with the configuration files for Quagga daemons. For example:
+ </div><pre class="screen">QCONFDIR="/etc/quagga"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">BGPD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">bgpd</code> daemon. For example:
+ </div><pre class="screen">BGPD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/bgpd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OSPF6D_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ospf6d</code> daemon. For example:
+ </div><pre class="screen">OSPF6D_OPTS="-A ::1 -f ${QCONFDIR}/ospf6d.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OSPFD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ospfd</code> daemon. For example:
+ </div><pre class="screen">OSPFD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/ospfd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RIPD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ripd</code> daemon. For example:
+ </div><pre class="screen">RIPD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/ripd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RIPNGD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ripngd</code> daemon. For example:
+ </div><pre class="screen">RIPNGD_OPTS="-A ::1 -f ${QCONFDIR}/ripngd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ZEBRA_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">zebra</code> daemon. For example:
+ </div><pre class="screen">ZEBRA_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/zebra.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ISISD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">isisd</code> daemon. For example:
+ </div><pre class="screen">ISISD_OPTS="-A ::1 -f ${QCONFDIR}/isisd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WATCH_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">watchquagga</code> daemon. For example:
+ </div><pre class="screen">WATCH_OPTS="-Az -b_ -r/sbin/service_%s_restart -s/sbin/service_%s_start -k/sbin/service_%s_stop"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WATCH_DAEMONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space separated list of monitored daemons. For example:
+ </div><pre class="screen">WATCH_DAEMONS="zebra bgpd ospfd ospf6d ripd ripngd"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-radvd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.16. /etc/sysconfig/radvd </h3></div></div></div><a id="idm66264928" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/radvd</code> file is used to pass arguments to the <code class="command">radvd</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">radvd</code> daemon. For example:
+ </div><pre class="screen">OPTIONS="-u radvd"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-samba"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.17. /etc/sysconfig/samba </h3></div></div></div><a id="idm18218032" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/samba</code> file is used to pass arguments to the Samba daemons at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SMBDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">smbd</code>. For example:
+ </div><pre class="screen">SMBDOPTIONS="-D"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">NMBDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">nmbd</code>. For example:
+ </div><pre class="screen">NMBDOPTIONS="-D"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WINBINDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">winbindd</code>. For example:
+ </div><pre class="screen">WINBINDOPTIONS=""</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-File_and_Print_Servers.html#s1-Samba">「Samba」</a> for more information on Samba and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-selinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.18. /etc/sysconfig/selinux </h3></div></div></div><a id="idm56797232" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/selinux</code> file contains the basic configuration options for SELinux. It is a symbolic link to <code class="filename">/etc/selinux/config</code>, and by default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SELINUX=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The security policy. The <em class="replaceable"><code>value </code></em> can be either <code class="option">enforcing</code> (the security policy is always enforced), <code class="option">permissive</code> (instead of enforcing the policy, appropriate warnings are displayed), or <code class="option">disabled</code> (no policy is used). For example:
+ </div><pre class="screen">SELINUX=enforcing</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SELINUXTYPE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The protection type. The <em class="replaceable"><code>value</code></em> can be either <code class="option">targeted</code> (the targeted processes are protected), or <code class="option">mls</code> (the Multi Level Security protection). For example:
+ </div><pre class="screen">SELINUXTYPE=targeted</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.19. /etc/sysconfig/sendmail </h3></div></div></div><a id="idm41112288" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/sendmail</code> is used to set the default values for the <span class="application"><strong>Sendmail</strong></span> application. By default, it contains the following values:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">DAEMON=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) running <code class="command">sendmail</code> as a daemon. For example:
+ </div><pre class="screen">DAEMON=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">QUEUE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The interval at which the messages are to be processed. For example:
+ </div><pre class="screen">QUEUE=1h</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="s2-email-mta-sendmail.html">「Sendmail」</a> for more information on Sendmail and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-spamd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.20. /etc/sysconfig/spamassassin </h3></div></div></div><a id="idm61054288" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/spamassassin</code> file is used to pass arguments to the <code class="command">spamd</code> daemon (a daemonized version of <span class="application"><strong>Spamassassin</strong></span>) at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SPAMDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">spamd</code> daemon. For example:
+ </div><pre class="screen">SPAMDOPTIONS="-d -c -m5 -H"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="s2-email-procmail-recipes.html#s3-email-mda-spam">「スパムフィルタ」</a> for more information on Spamassassin and its configuration.
+ </div></div><div class="section" id="s2-sysconfig-squid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.21. /etc/sysconfig/squid </h3></div></div></div><a id="idm24893216" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/squid</code> file is used to pass arguments to the <code class="command">squid</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">SQUID_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">squid</code> daemon. For example:
+ </div><pre class="screen">SQUID_OPTS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SQUID_SHUTDOWN_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for <code class="command">squid</code> daemon to shut down. For example:
+ </div><pre class="screen">SQUID_SHUTDOWN_TIMEOUT=100</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SQUID_CONF=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default configuration file. For example:
+ </div><pre class="screen">SQUID_CONF="/etc/squid/squid.conf"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-rcu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.22. /etc/sysconfig/system-config-users </h3></div></div></div><a id="idm26133472" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/system-config-users</code> file is the configuration file for the <span class="application"><strong>User Manager</strong></span> utility, and should not be edited by hand. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">FILTER=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) filtering of system users. For example:
+ </div><pre class="screen">FILTER=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ASSIGN_HIGHEST_UID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) assigning the highest available UID to newly added users. For example:
+ </div><pre class="screen">ASSIGN_HIGHEST_UID=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ASSIGN_HIGHEST_GID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) assigning the highest available GID to newly added groups. For example:
+ </div><pre class="screen">ASSIGN_HIGHEST_GID=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PREFER_SAME_UID_GID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) using the same UID and GID for newly added users when possible. For example:
+ </div><pre class="screen">PREFER_SAME_UID_GID=true</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="s1-users-configui.html">「ユーザー管理のツールを使う」</a> for more information on <span class="application"><strong>User Manager</strong></span> and its usage.
+ </div></div><div class="section" id="s2-sysconfig-vncservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.23. /etc/sysconfig/vncservers </h3></div></div></div><a id="idm56105616" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/vncservers</code> file configures the way the <em class="firstterm">Virtual Network Computing</em> (<em class="firstterm">VNC</em>) server starts up. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">VNCSERVERS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A list of space separated <code class="option"><em class="replaceable"><code>display</code></em>:<em class="replaceable"><code>username</code></em> </code> pairs. For example:
+ </div><pre class="screen">VNCSERVERS="2:myusername"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">VNCSERVERARGS[<em class="replaceable"><code>display</code></em>]=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional arguments to be passed to the VNC server running on the specified <em class="replaceable"><code>display</code></em>. For example:
+ </div><pre class="screen">VNCSERVERARGS[2]="-geometry 800x600 -nolisten tcp -localhost"</pre></dd></dl></div></div><div class="section" id="s2-sysconfig-xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.1.24. /etc/sysconfig/xinetd </h3></div></div></div><a id="idm48474176" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/xinetd</code> file is used to pass arguments to the <code class="command">xinetd</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">EXTRAOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">xinetd</code>. For example:
+ </div><pre class="screen">EXTRAOPTIONS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">XINETD_LANG=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The locale information to be passed to every service started by <code class="command">xinetd</code>. Note that to remove locale information from the <code class="command">xinetd</code> environment, you can use an empty string (<code class="option">""</code>) or <code class="option">none</code>. For example:
+ </div><pre class="screen">XINETD_LANG="en_US"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a> for more information on how to configure the <code class="command">xinetd</code> services.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x-useful-websites.html"><strong>戻る</strong>C.5.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="s1-sysconfig-etcsysconf-dir.html"><strong>次へ</strong>D.2. Directories in the /etc/sysconfig/ Directory</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html
new file mode 100644
index 0000000..5101cb4
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html
@@ -0,0 +1,325 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Monitoring_and_Automation.html" title="パート VI. 監視および自動化" /><link rel="prev" href="s1-sysinfo-additional-resources.html" title="17.7. その他のリソース" /><link rel="next" href="s1-logfiles-locating.html" title="18.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-sysinfo-additional-resource
s.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-locating.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><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s1-configuring-rsyslog">18.1. rsyslog の設定法</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-global-directives">18.1.1. 全体ディレクティブ</a></span></dt><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-modules">18.1.2. モジュール</a></span></dt><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-rules">18.1.3. ルール</a></span></dt><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.htm
l#s2-rsyslog-cmd-options">18.1.4. <span class="application"><strong>rsyslog</strong></span> コマンドラインè¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="s1-logfiles-locating.html">18.2. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’探ã™</a></span></dt><dd><dl><dt><span class="section"><a href="s1-logfiles-locating.html#configuring-logrotate">18.2.1. logrotate ã®è¨å®šæ³•</a></span></dt></dl></dd><dt><span class="section"><a href="s1-logfiles-viewing.html">18.3. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º</a></span></dt><dt><span class="section"><a href="s1-logfiles-adding.html">18.4. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¿½åŠ </a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">18.5. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’監視ã™ã‚‹</a></span></dt><dt><span class="section"><a href="s1-log-files-additional-resources.html">18.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="s1-log-files-additional-resources.html#s2-log-files-installed-docs">18.6.1. インã‚
¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt><dt><span class="section"><a href="s2-log-files-useful-websites.html">18.6.2. å½¹ã«ç«‹ã¤ Web サイト</a></span></dt></dl></dd></dl></div><a id="idm70184976" class="indexterm"></a><a id="idm42008832" class="indexterm"></a><div class="para">
+ <em class="firstterm">ログファイル</em> は、システム上で動作しているカーネル、サービス、アプリケーションなどのシステムに関するメッセージが入っているファイルです。情報ごとに異なるログファイルがあります。例えば、デフォルトシステムログファイル、セキュリティメッセージだけのログファイル、 cron タスク用のログファイルなどがあります。
+ </div><div class="para">
+ Log files can be very useful when trying to troubleshoot a problem with the system such as trying to load a kernel driver or when looking for unauthorized login attempts to the system. This chapter discusses where to find log files, how to view log files, and what to look for in log files.
+ </div><a id="idm44064944" class="indexterm"></a><a id="idm58681456" class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code class="systemitem">rsyslogd</code>. 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.
+ </div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> is an enhanced, multi-threaded syslog daemon which replaced the <code class="command">sysklogd</code> daemon. <span class="application"><strong>rsyslog</strong></span> supports the same functionality as <span class="application"><strong>sysklogd</strong></span> and extends it with enhanced filtering, encryption protected relaying of messages, various configuration options, or support for transportation via the <code class="systemitem">TCP</code> or <code class="systemitem">UDP</code> protocols. Note that <span class="application"><strong>rsyslog</strong></span> is compatible with <span class="application"><strong>sysklogd</strong></span>.
+ </div><div class="section" id="s1-configuring-rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.1. 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>. It consists of <em class="firstterm">global directives</em>, <em class="firstterm">rules</em> or comments (any empty lines or any text following a hash sign (<code class="literal">#</code>)). Both, global directives and rules are extensively described in the sections below.
+ </div><div class="section" id="s2-global-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.1. 全体ディレクティブ</h3></div></div></div><div class="para">
+ Global directives specify configuration options that apply to the <code class="systemitem">rsyslogd</code> daemon. They usually specify a value for a specific pre-defined 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.
+ </div><div class="para">
+ A comprehensive list of all available configuration directives and their detailed description can be found in <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/rsyslog_conf_global.html</code>.
+ </div></div><div class="section" id="s2-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.2. モジュール</h3></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 dynamic 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 <code class="literal">Text File Input Module</code> (<code class="command">imfile</code> — enables <span class="application"><strong>rsyslog</strong></span> to convert any standard text files into syslog messages), specify the following line in your <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 these 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">imrelp</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Output Modules — Output modules provide a facility to store messages into various targets such as sending them across network, storing them in a database or encrypting them. 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">
+ Filter Modules — Filter modules provide the ability to filter messages according to specified rules. The name of a filter module always starts with the <code class="literal">fm</code> prefix.
+ </div></li><li class="listitem"><div class="para">
+ Parser Modules — Parser modules use the message parsers to parse message content of any received messages. 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>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Message Modification Modules — Message modification modules change the content of a syslog message. The message modification modules only differ in their implementation from the output and filter modules but share the same interface.
+ </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, refer to <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s3-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>, <code class="command">smtradfile</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Library Modules — Library modules generally 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/">http://www.rsyslog.com/doc/rsyslog_conf_modules.html</a>
+ </div><div class="warning"><div class="admonition_header"><h2>Make sure you use trustworthy modules only</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><div class="section" id="s2-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.3. ルール</h3></div></div></div><div class="para">
+ A rule is specified by a <em class="firstterm">filter</em> part, which selects a subset of syslog messages, and an <em class="firstterm">action</em> 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. For more information on filters, refer to <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s3-filter-conditions">「フィルター条件」</a> and for information on actions, refer to <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s3-actions">「アクション」</a>.
+ </div><div class="section" id="s3-filter-conditions"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">18.1.3.1. フィルター条件</h4></div></div></div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> offers various ways how to filter syslog messages according to various properties. This sections sums up the most used filter conditions.
+ </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>. 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 these keywords: <code class="command">auth</code>, <code class="command">authpriv</code>, <code class="command">cron</code>, <code class="command">daemon</code>, <code class="command">kern</code>, <code class="command">lpr</code>, <code class="command">mail</code>, <code class="command">news</code>, <code class="command">syslog</code>, <code class="command">user</code>, <code class="command">uucp</code>, and <code class="command">local0</code> through <code class="command">local7</code>.
+ </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 these keywords (listed in an ascending order): <code class="command">debug</code>, <code class="command">info</code>, <code class="command">notice</code>, <code class="command">warning</code>, <code class="command">err</code>, <code class="command">crit</code>, <code class="command">alert</code>, and <code class="command">emerg</code>.
+ </div><div class="para">
+ By preceding any priority with an equal sign (<code class="literal">=</code>), you specify that only syslog messages with that priority will be selected. All other priorities will be ignored. Conversely, preceding a priority with an exclamation mark (<code class="literal">!</code>) selects all syslog messages but those with the defined priority. By not using either of these two extensions, you specify a selection of syslog messages with the defined or higher 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 dot). Specifying the keyword <code class="literal">none</code> serves for facilities with no given priorities.
+ </div><div class="para">
+ To define multiple facilities and priorities, simply separate them with a comma (<code class="literal">,</code>). To define multiple filters on one line, separate them with a semi-colon (<code class="literal">;</code>).
+ </div><div class="para">
+ 以下は、ファシリティとプライオリティによる簡単なフィルターのいくつかの例です:
+ </div><pre class="screen">
+kern.* # すべてのプライオリティを持つすべての kernel syslog メッセージを選択します
+</pre><pre class="screen">
+mail.crit # プライオリティ <code class="command">crit</code> 以上を持つすべての mail syslog メッセージを選択します。
+</pre><pre class="screen">
+cron.!info,!debug # Selects all cron syslog messages except those with the <code class="command">info</code> or <code class="command">debug</code> priority.
+</pre></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, refer to <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s4-properties">「プロパティ」</a>. Each of the properties specified in the filters lets you compare it to a specific value using one of the compare-operations listed in <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#table-compare-operations">表18.1「プロパティによる比較演算」</a>.
+ </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.
+ </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.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>startswith</code></em>
+ </td><td class="">
+ Checks whether the provided string matches a prefix of the text provided by the property.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>regex</code></em>
+ </td><td class="">
+ Compares the provided POSIX BRE (Basic Regular Expression) 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></tbody></table></div></div><br class="table-break" /><div class="para">
+ プロパティによるフィルターを定義するには、以下の構文を使用します:
+ </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 (for example, <em class="parameter"><code>timegenerated</code></em>, <em class="parameter"><code>hostname</code></em>, etc.).
+ </div></li><li class="listitem"><div class="para">
+ The optional exclamation point (<code class="literal">!</code>) negates the output of the compare-operation (if prefixing the compare-operation).
+ </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="ch-Viewing_and_Managing_Log_Files.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. To escape certain character (for example a quotation mark (<code class="literal">"</code>)), use the backslash character (<code class="literal">\</code>).
+ </div></li></ul></div><div class="para">
+ 以下は、プロパティによるフィルターのいくつかの例です:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 以下のフィルターは、メッセージテキストに文字列 <code class="literal">error</code> を含む syslog メッセージを選択します:
+ </div><pre class="screen">:msg, contains, "error"</pre></li><li class="listitem"><div class="para">
+ 以下のフィルターは、ホスト名 <code class="literal">host1</code> から受信した syslog メッセージを選択します:
+ </div><pre class="screen">:hostname, isequal, "host1"</pre></li><li class="listitem"><div class="para">
+ The following filter selects 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>):
+ </div><pre class="screen">:msg, !regex, "fatal .* error"</pre></li></ul></div></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. The syntax of this language is defined in <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/rscript_abnf.html</code> along with examples of various expression-based filters.
+ </div><div class="para">
+ 表現によるフィルターを定義するには、以下の構文を使用します:
+ </div><pre class="screen">if <em class="replaceable"><code><EXPRESSION></code></em> then <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>.
+ </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>.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Define an expression-based filter on a single line</h2></div><div class="admonition"><div class="para">
+ When defining an expression-based filter, it must be defined on a single line.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>正規表現を使用しないでください</h2></div><div class="admonition"><div class="para">
+ 正規表現は今のところ表現によるフィルターにおいてサポートされていません。
+ </div></div></div></dd><dt class="varlistentry"><span class="term">BSD 形式のブロック</span></dt><dd><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> supports BSD-style blocks inside the <code class="filename">/etc/rsyslog.conf</code> configuration file. Each block consists of rules which are preceded with a program or hostname label. Use the '!<em class="replaceable"><code><PROGRAM></code></em>' or '-<em class="replaceable"><code><PROGRAM></code></em>' labels to include or exclude programs, respectively. Use the '+<em class="replaceable"><code><HOSTNAME></code></em> ' or '-<em class="replaceable"><code><HOSTNAME></code></em> ' labels include or exclude hostnames, respectively.
+ </div><div class="para">
+ <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#example-bsd-block1">例18.1「BSD 形式のブロック」</a> shows a BSD-style block that saves all messages generated by <span class="application"><strong>yum</strong></span> to a file.
+ </div><div class="example" id="example-bsd-block1"><h6>例18.1 BSD 形式のブロック</h6><div class="example-contents"><pre class="screen">
+!yum
+*.* /var/log/named.log
+</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s3-actions"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">18.1.3.2. アクション</h4></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. The following is a rule 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="screen">cron.* /var/log/cron.log
+</pre><div class="para">
+ Use a dash mark (<code class="literal">-</code>) as a prefix of the file path you specified if you want to omit syncing the desired log file after every syslog message is generated.
+ </div><div class="para">
+ Your specified file path can be either static or dynamic. Static files are represented by a simple file path as was shown in the example above. Dynamic files are represented by a template and a question mark (<code class="literal">?</code>) prefix. For more information on templates, refer to <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s4-generating-dynamic-fnames">「動的なファイル名の収集」</a>.
+ </div><div class="para">
+ If the file you specified is an existing <span class="application"><strong>tty</strong></span> or <code class="filename">/dev/console</code> device, syslog messages are sent to standard output (using special <span class="application"><strong>tty</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 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">(<em class="replaceable"><code><OPTION></code></em>)</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 <em class="replaceable"><code><OPTION></code></em> attribute can be replaced with an option such as <code class="command">z<em class="replaceable"><code><NUMBER></code></em> </code>. This option 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. To define multiple options, simply separate each one of them with a comma (<code class="literal">,</code>).
+ </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="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):
+ </div><pre class="screen">*.* @192.168.0.1 # <code class="systemitem">UDP</code> プロトコル経由で 192.168.0.1 にメッセージを転送します</pre><pre class="screen">*.* @@example.com:18 # ポート 18 の <code class="systemitem">TCP</code> プロトコルを使用して "example.com" にメッセージを転送します</pre><pre class="screen">
+*.* @(z9)[2001::1] # Compresses messages with <span class="application"><strong>zlib</strong></span> (level 9 compression)
+ # and forwards them to 2001::1 using the <code class="systemitem">UDP</code> protocol</pre></dd><dt class="varlistentry"><span class="term">出力チャネル</span></dt><dd><div class="para">
+ Output channels are primarily used for log file rotation (for more info on log file rotation, refer to <a class="xref" href="s1-logfiles-locating.html#configuring-logrotate">「logrotate の設定法」</a>), that is, to specify the maximum size a log file can grow to. To define an output channel, 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.
+ </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">
+ <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#example-log-rotation">例18.2「Output channel log rotation」</a> 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 and then used in a rule which selects every syslog message with any priority and executes the previously-defined output channel on the acquired syslog messages. 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 class="example" id="example-log-rotation"><h6>例18.2 Output channel log rotation</h6><div class="example-contents"><pre class="screen">
+$outchannel log_rotation,/var/log/test_log.log, 104857600, /home/joe/log_rotation_script
+
+*.* $log_rotation
+</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Support for output channels is to be removed in the future</h2></div><div class="admonition"><div class="para">
+ Output channels are currently supported by <span class="application"><strong>rsyslog</strong></span>, however, they are planned to be removed in the nearby future.
+ </div></div></div></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 simply specifying a username of the user you wish to send the messages to. To specify more than one user, separate each username 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, refer to <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s3-templates">「テンプレート」</a>). 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 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 specified by the attacker in the program you specified (in your action) to be executed. 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">Inputting 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">
+ <em class="replaceable"><code><DB_HOST></code></em> 属性はデータベースのホスト名を指定します。
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code><DB_NAME></code></em> 属性はデータベースの名前を指定します。
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code><DB_USER></code></em> 属性はデータベースのユーザーを指定します。
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code><DB_PASSWORD></code></em> 属性は前述のデータベースのユーザーに使用するパスワードを指定します。
+ </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, refer to <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s3-templates">「テンプレート」</a>.
+ </div></li></ul></div><div class="important"><div class="admonition_header"><h2>MySQL および PostgreSQL の使用法</h2></div><div class="admonition"><div class="para">
+
+ </div><pre class="screen">
+$ModLoad ommysql # MySQL サポートの出力モジュール
+$ModLoad ompgsql # PostgreSQL サポートの出力モジュール
+</pre><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> モジュールの詳細は <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s2-modules">「モジュール」</a> を参照してください。
+ </div><div class="para">
+ Alternatively, you may use a generic database interface provided by the <code class="systemitem">omlibdb</code> module. However, this module is currently not compiled.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">syslog メッセージの破棄</span></dt><dd><div class="para">
+ 選択されたメッセージを破棄するには、チルダ記号 (<code class="literal">~</code>) を使用します。以下のルールはすべての cron syslog メッセージを破棄します:
+ </div><pre class="screen">cron.* ~</pre></dd></dl></div><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 (&). Only the first action is allowed to have a selector specified on its line. The following is an example of a rule with multiple actions:
+ </div><pre class="screen">
+kern.=crit joe
+& ^test-program;temp
+& @192.168.0.1
+</pre><div class="para">
+ In the example above, all kernel syslog messages with the critical priority (<em class="parameter"><code>crit</code></em>) are send to user <code class="systemitem">joe</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><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="para">
+ Note that 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.
+ </div><div class="warning"><div class="admonition_header"><h2>テンプレートの使用法</h2></div><div class="admonition"><div class="para">
+ テンプレートはアクションにおいて使用する前に定義されている必要があります。そうでなければ、無視されます。
+ </div></div></div><div class="para">
+ テンプレートの詳細は <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s3-templates">「テンプレート」</a> を参照してください。
+ </div></div><div class="section" id="s3-templates"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">18.1.3.3. テンプレート</h4></div></div></div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> により生成されたすべての出力は、テンプレートの使用を通して、必要に応じて変更および整形できます。テンプレートを作成するには、以下の構文を使用します:
+ </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> はテンプレートの名前です。テンプレートを参照するには、この名前を使用します。
+ </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, you are allowed to escape characters in order to use their functionality, such as <code class="literal">\n</code> for new line or <code class="literal">\r</code> for carriage return. Other characters, such as <code class="literal">%</code> or <code class="literal">"</code>, have to be escaped in case you want to those characters literally.
+ </div><div class="para">
+ The text specified within two percent signs (<code class="literal">%</code>) specifies a <em class="firstterm">property</em> that is consequently replaced with the property's actual value. For more information on properties, refer to <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s4-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. Do not mistake these for property options, which are defined inside the template text (between <code class="literal">"</code>…<code class="literal">"</code>). The currently supported template options are <em class="parameter"><code>sql</code></em> and <em class="parameter"><code>stdsql</code></em> 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 (for more information, refer to section <em class="citetitle">Inputting syslog messages in a database</em> in <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#s3-actions">「アクション」</a>) checks whether the <em class="parameter"><code>sql</code></em> and <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></div></li></ul></div><div class="section" id="s4-generating-dynamic-fnames"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">18.1.3.3.1. 動的なファイル名の収集</h5></div></div></div><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. For example, use the <em class="parameter"><code>timegenerated</code></em> property 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:
+ </div><pre class="screen">*.* ?DynamicFile</pre></div><div class="section" id="s4-properties"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">18.1.3.3.2. プロパティ</h5></div></div></div><div class="para">
+ Properties defined inside a template (within two percent signs (<code class="literal">%</code>)) allow you to 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 comprehensible list of all available properties and their detailed description can be found in <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/property_replacer.html</code> 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, specify 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. A comprehensible list of all available properties and their detailed description can be found in <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/property_replacer.html</code> 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">
+ 以下のプロパティは単に syslog メッセージのテキスト全体を取得します:
+ </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 timestamp that is generated when the syslog message is received and formats it according to the RFC 3999 date standard.
+ </div><pre class="screen">%timegenerated:1:10:date-rfc3339%</pre></li></ul></div></div><div class="section" id="s4-template-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">18.1.3.3.3. テンプレート例</h5></div></div></div><div class="para">
+ このセクションは <span class="application"><strong>rsyslog</strong></span> のテンプレートの例をいくつか説明します。
+ </div><div class="para">
+ <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#example-temp1">例18.3「冗長な syslog メッセージのテンプレート」</a> shows a template that formats a syslog message so that it outputs the message's severity, facility, the timestamp of when the message was received, the hostname, the message tag, the message text, and ends with a new line.
+ </div><div class="example" id="example-temp1"><h6>例18.3 冗長な syslog メッセージのテンプレート</h6><div class="example-contents"><pre class="screen">$template verbose,"%syslogseverity%,%syslogfacility%,%timegenerated%,%HOSTNAME%,%syslogtag%,%msg%
+"</pre></div></div><br class="example-break" /><div class="para">
+ <a class="xref" href="ch-Viewing_and_Managing_Log_Files.html#example-temp2">例18.4「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 hostname, message tag and a timestamp, 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.4 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="ch-Viewing_and_Managing_Log_Files.html#example-temp3">例18.5「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.5 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. It is advisable to not create a template using this prefix to avoid any 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><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><pre class="screen">"<%PRI%>1 %TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA% %msg%
+\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_FileFormat</code></em></span></dt><dd><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><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><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><pre class="screen">"<%PRI%>%TIMESTAMP% %HOSTNAME% %syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd></dl></div></div></div></div><div class="section" id="s2-rsyslog-cmd-options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.4. <span class="application"><strong>rsyslog</strong></span> コマンドライン設定</h3></div></div></div><div class="para">
+ Some of <span class="application"><strong>rsyslog</strong></span>'s functionality can be configured through the command line options, as <span class="application"><strong>sysklogd</strong></span>'s can. Note that as of version 3 of <span class="application"><strong>rsyslog</strong></span>, this method was deprecated. To enable some of these option, you must specify the compatibility mode <span class="application"><strong>rsyslog</strong></span> should run in. However, configuring <span class="application"><strong>rsyslog</strong></span> through the command line options should be avoided.
+ </div><div class="para">
+ To specify the compatibility mode <span class="application"><strong>rsyslog</strong></span> should run in, use the <code class="option">-c</code> option. When no parameter is specified, <span class="application"><strong>rsyslog</strong></span> tries to be compatible with <span class="application"><strong>sysklogd</strong></span>. This is partially achieved by activating configuration directives that modify your configuration accordingly. Therefore, it is advisable to supply this option with a number that matches the major version of <span class="application"><strong>rsyslog</strong></span> that is in use and update your <code class="filename">/etc/rsyslog.conf</code> configuration file accordingly. If you want to, for example, use <span class="application"><strong>sysklogd</strong></span> options (which were deprecated in version 3 of <span class="application"><strong>rsyslog</strong></span>), you can specify so by executing the following command:
+ </div><pre class="screen">~]# rsyslogd -c 2</pre><div class="para">
+ Options that are passed to the <code class="systemitem">rsyslogd</code> daemon, including the backward compatibility mode, can be specified in the <code class="filename">/etc/sysconfig/rsyslog</code> configuration file.
+ </div><div class="para">
+ さまざまな <code class="command">rsyslogd</code> オプションの詳細は <code class="command">man rsyslogd</code> を参照してください。
+ </div></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-logfiles-locating.html"><strong>次へ</strong>18.2. ログファイルを探す</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Web_Servers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Web_Servers.html
new file mode 100644
index 0000000..8d43977
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Web_Servers.html
@@ -0,0 +1,1357 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Servers.html" title="パート V. サーバー" /><link rel="prev" href="s2-bind-additional-resources.html" title="12.2.7. その他のリソース" /><link rel="next" href="ch-Mail_Servers.html" title="第14章 メールサーバー" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-bind-additional-resources.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">第13章 ウェブ サーバー</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">13.1. Apache HTTP サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-features">13.1.1. 新機能</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-changes">13.1.2. 注目すべき変更</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">13.1.3. 設定の更新</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-running">13.1.4. httpd サービスの実行方法</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-ap
ache-editing">13.1.5. 設定ファイルの編集</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">13.1.6. Working with Modules</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-virtualhosts">13.1.7. 仮想ホストのセットアップ</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">13.1.8. SSL サーバーのセットアップ</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">13.1.9. その他のリソース</a></span></dt></dl></dd></dl></div><a id="idm67715136" class="indexterm"></a><a id="idm41119552" class="indexterm"></a><div class="para">
+ <code class="systemitem">HTTP</code> (ハイパーテキスト転送プロトコル)サーバー、あるいは<em class="firstterm">ウェブサーバー</em>は、ウェブ経由でクライアントにコンテンツを提供するネットワークサービスです。これは通常ウェブページを意味しますが、他の文書も同様に提供することができます。
+ </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">13.1. Apache HTTP サーバー</h2></div></div></div><a id="idm67709664" class="indexterm"></a><div class="para">
+ This section 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 <a href="http://www.apache.org/">Apache Software Foundation</a>, that is included in Fedora 17. It describes the basic configuration of the <code class="systemitem">httpd</code> service, and covers advanced topics such as adding server modules, setting up virtual hosts, or configuring the secure HTTP server.
+ </div><div class="para">
+ Apache HTTP Server 2.2 とバージョン 2.0 の間には大きな変更点があります。以前のリリースの Fedora からアップグレードしているならば、必要に応じて <code class="systemitem">httpd</code> サービス設定を更新する必要があります。このセクションは、いくつかの新しく追加された機能、重要な変更点の概要、および古い設定ファイルの更新について詳しく説明しているガイドを概観します。
+ </div><div class="section" id="s2-apache-version2-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.1. 新機能</h3></div></div></div><a id="idm67716608" class="indexterm"></a><div class="para">
+ Apache HTTP Server バージョン 2.2 は以下の機能拡張をしています:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="idm67720976" class="indexterm"></a>
+ <a id="idm18327968" class="indexterm"></a>
+ つまり、改良されたキャッシュモジュール <code class="systemitem">mod_cache</code> および <code class="systemitem">mod_disk_cache</code>。
+ </div></li><li class="listitem"><div class="para">
+ <a id="idm18333808" class="indexterm"></a>
+ つまり、プロキシ負荷分散のサポート <code class="systemitem">mod_proxy_balancer</code> モジュール。
+ </div></li><li class="listitem"><div class="para">
+ 32ビットアーキテクチャーにおける大容量ファイルのサポート、ウェブサーバーが2GBより大きなファイルを取り扱えます。
+ </div></li><li class="listitem"><div class="para">
+ 認証モジュールを置き換える、認証と認可のサポートの新しい構成は、前のバージョンで提供されました。
+ </div></li></ul></div></div><div class="section" id="s2-apache-version2-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.2. 注目すべき変更</h3></div></div></div><a id="idm18340688" class="indexterm"></a><div class="para">
+ 2.0 以降、デフォルトの <code class="systemitem">httpd</code> サービス設定にいくつかの変更がありました:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="idm58227936" class="indexterm"></a>
+ <a id="idm58229872" class="indexterm"></a>
+ 以下のモジュールはもはやデフォルトで読み込まれません: <code class="systemitem">mod_cern_meta</code> および <code class="systemitem">mod_asis</code>。
+ </div></li><li class="listitem"><div class="para">
+ <a id="idm58235472" class="indexterm"></a>
+ 以下のモジュールは新しくデフォルトで読み込まれます: <code class="systemitem">mod_ext_filter</code>。
+ </div></li></ul></div></div><div class="section" id="s2-apache-version2-migrating"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.3. 設定の更新</h3></div></div></div><a id="idm51277216" class="indexterm"></a><div class="para">
+ Apache HTTP Server バージョン 2.0 から設定ファイルを更新するには、以下の手順に従ってください:
+ </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="idm51284688" 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">service httpd configtest</code></pre><div class="para">
+ Apache HTTP Server のバージョン 2.0 から 2.2 に設定を更新することに関する詳細は <a href="http://httpd.apache.org/docs/2.2/upgrading.html">http://httpd.apache.org/docs/2.2/upgrading.html</a> を参照してください。
+ </div></div><div class="section" id="s2-apache-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.4. 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 as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install httpd</code></pre><div class="para">
+ For more information on the concept of runlevels and how to manage system services in Fedora in general, refer to <a class="xref" href="ch-Services_and_Daemons.html">8章<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">13.1.4.1. サービスの開始</h4></div></div></div><a id="idm42150624" 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">
+ ブート時にサービスを自動的に開始したければ、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl enable httpd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div><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">13.1.4.2. さービスの停止</h4></div></div></div><a id="idm57676608" 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">
+ 起動時にサービスが自動的に開始しないようにするには、次のように入力します:
+ </div><pre class="screen"><code class="command">systemctl disable httpd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s3-apache-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.4.3. サービスの再開</h4></div></div></div><a id="idm57687840" class="indexterm"></a><div class="para">
+ 実行中の <code class="systemitem">httpd</code> サービスを再起動するには、二つの異なる方法があります:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ サービスを完全に再起動するには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のとおり入力します:
+ </div><pre class="screen"><code class="command">systemctl restart httpd.service</code></pre><div class="para">
+ これは実行中の <code class="systemitem">httpd</code> サービスを停止して、その後再び開始します。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 will cause the running <code class="systemitem">httpd</code> service to reload the configuration file. Note that any requests being currently 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">
+ 処理中の内容に影響を与えることなく設定を再読み込みするには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="screen"><code class="command">service httpd graceful</code></pre><div class="para">
+ This will cause the running <code class="systemitem">httpd</code> service to reload the configuration file. Note that any requests being currently processed will use the old configuration.
+ </div></li></ol></div><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><div class="section" id="s3-apache-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.4.4. サービスの状態確認</h4></div></div></div><a id="idm49554960" class="indexterm"></a><div class="para">
+ サービスが実行中であるかどうかを確認するには、シェルプロンプトにおいて次のとおり入力します:
+ </div><pre class="screen"><code class="command">systemctl is-active httpd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div></div><div class="section" id="s2-apache-editing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.1.5. 設定ファイルの編集</h3></div></div></div><div class="para">
+ <code class="systemitem">httpd</code> サービスが開始するとき、<a class="xref" href="ch-Web_Servers.html#table-apache-editing-files">表13.1「httpd サービス設定ファイル」</a>に一覧化されている位置から設定が読み込まれます。
+ </div><div class="table" id="table-apache-editing-files"><h6>表13.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="idm22073008" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf/httpd.conf</code>
+ </td><td class="">
+ 中心となる設定ファイルです。
+ </td></tr><tr><td class="">
+ <a id="idm22077520" 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. Refer to <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="idm45775696" class="indexterm"></a><div class="para">
+ 起こりえるエラーに対して設定を確認するには、シェルプロンプトにおいて次のとおり入力します:
+ </div><pre class="screen"><code class="command">service httpd configtest</code></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">13.1.5.1. 一般的な httpd.conf ディレクティブ</h4></div></div></div><a id="idm45779248" 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="idm51389728" 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>例13.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="idm51399632" 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>例13.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="idm48545392" 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>例13.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="idm60511296" 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>例13.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="idm22160192" 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>例13.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="idm22169584" 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">表13.2「利用可能な <VirtualHost> オプション」</a>に記載されている特別な形式を使用できます。
+ </div><div class="table" id="table-apache-httpdconf-virtualhost"><h6>表13.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>例13.6 <VirtualHost> ディレクティブの使用法</h6><div class="example-contents"><pre class="programlisting"><VirtualHost *:80>
+ ServerAdmin webmaster at 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="idm46943680" 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="idm46950656" class="indexterm"></a><a id="idm46951104" class="indexterm"></a><div class="para">
+ <em class="replaceable"><code>filename</code></em> は要求されたディレクトリにおいて探すファイルの名前です。デフォルトで、サーバーは <code class="filename">.htaccess</code> を探します。
+ </div><a id="idm44768976" class="indexterm"></a><a id="idm44771360" 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>例13.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="idm44779264" 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>例13.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="idm27185792" 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>例13.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="idm73789616" 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>例13.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="idm73802480" 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>例13.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="idm59361168" 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>表13.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>例13.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="idm34459360" 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>例13.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="idm55199552" 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>例13.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="idm52144048" 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>例13.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="idm70079872" 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>例13.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="idm22037648" 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="idm22046320" 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>例13.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="idm25389088" 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>例13.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="idm25398432" class="indexterm"></a>
+ <code class="option">AllowOverride</code></span></dt><dd><a id="idm27959104" class="indexterm"></a><a id="idm27963600" 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">表13.4「利用可能な AllowOverride オプション」</a>.
+ </div><div class="table" id="table-apache-httpdconf-allowoverride"><h6>表13.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>例13.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="idm25431664" 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>例13.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="idm46701664" 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>例13.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="idm25507952" 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>例13.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="idm25518144" 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">表13.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>表13.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>例13.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="idm49311056" 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>例13.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="idm47234240" 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>例13.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="idm47244784" 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">表13.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>表13.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>例13.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="idm50410416" 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="idm50417184" 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>例13.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="idm50424016" 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="idm45662432" 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>例13.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="idm45670720" 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>例13.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="idm43439600" 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>例13.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="idm25687984" 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>例13.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="idm25698832" 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>例13.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="idm56232800" 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="idm56236656" 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>例13.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="idm39453488" 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>例13.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="idm69312512" 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="idm69317872" 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>例13.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="idm51913120" 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">表13.7「利用可能な ExtendedStatus オプション」</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" id="table-apache-httpdconf-extendedstatus"><h6>表13.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>例13.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="idm66303616" 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>例13.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="idm45752832" 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>例13.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="idm45761312" 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">表13.8「利用可能な HostnameLookups オプション」</a>において説明されている有効なキーワードである必要があります。サーバーにおいてリソースを保護するために、オプションの初期値は <code class="option">Off</code> です。
+ </div><div class="table" id="table-apache-httpdconf-hostnamelookup"><h6>表13.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>例13.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="idm25602208" 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="idm25607136" 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>例13.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="idm71655456" 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>例13.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="idm52998272" 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">表13.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>表13.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>例13.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="idm58379312" 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">表13.10「利用可能な KeepAlive オプション」</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" id="table-apache-httpdconf-keepalive"><h6>表13.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>例13.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="idm69304064" 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>例13.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="idm59663504" 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>例13.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="idm46825536" 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>例13.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="idm46839232" 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="idm47210448" class="indexterm"></a><a id="idm34195904" 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">
+ Apache HTTP Server の DSO サポートの詳細は<a class="xref" href="ch-Web_Servers.html#s2-apache-dso">「Working with Modules」</a>を参照してください。
+ </div><div class="example" id="example-apache-httpdconf-loadmodule"><h6>例13.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="idm34196064" 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">表13.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>表13.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>例13.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="idm40884480" 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">表13.12「利用可能な LogLevel オプション」</a>. The default option is <code class="option">warn</code>.
+ </div><div class="table" id="table-apache-httpdconf-loglevel"><h6>表13.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>例13.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="idm26667600" 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>例13.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="idm38148576" 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>例13.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="idm49217904" 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">表13.13「利用できるサーバーの機能」</a>に説明されている有効なキーワードでなければいけません。
+ </div><div class="table" id="table-apache-httpdconf-options"><h6>表13.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>例13.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="idm55695312" 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">表13.14「利用可能な Order オプション」</a>. The default option is <code class="option">allow,deny</code>.
+ </div><div class="table" id="table-apache-httpdconf-order"><h6>表13.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>例13.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="idm57891744" 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="idm57898080" 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>例13.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="idm62024352" 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">表13.15「利用可能な ProxyRequests オプション」</a> に説明されている有効なキーワードである必要があります。初期オプションは <code class="option">Off</code> です。
+ </div><div class="table" id="table-apache-httpdconf-proxyrequests"><h6>表13.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>例13.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="idm66839056" 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>例13.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="idm64580720" 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">表13.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>表13.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="idm28653744" 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>例13.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="idm28660592" 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="idm32462880" 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>例13.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="idm32472112" 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 at 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>例13.59 ServerAdmin ディレクティブの使用法</h6><div class="example-contents"><pre class="programlisting">ServerAdmin webmaster at penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm53846624" 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>例13.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="idm65524848" 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="idm65529760" 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>例13.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="idm21588832" 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">表13.17「利用可能な ServerSignature オプション」</a>において説明されている有効なキーワードである必要があります。オプションの初期値は <code class="option">On</code> です。
+ </div><div class="table" id="table-apache-httpdconf-serversignature"><h6>表13.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>例13.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="idm38104112" 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">表13.18「利用可能な ServerTokens オプション」</a>. The default option is <code class="option">OS</code>.
+ </div><div class="table" id="table-apache-httpdconf-servertokens"><h6>表13.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>例13.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="idm41628896" 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>例13.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="idm44957440" 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>例13.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="idm44966992" 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="idm60116800" 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>例13.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="idm60125728" 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">表13.19「利用可能な UseCanonicalName オプション」</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" id="table-apache-httpdconf-usecanonicalname"><h6>表13.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>例13.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="idm64953456" 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>例13.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="idm52825936" 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="idm52831888" 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">表13.20「利用可能な UserDir オプション」</a>. The default option is <code class="option">disabled</code>.
+ </div><div class="table" id="table-apache-httpdconf-userdir"><h6>表13.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>例13.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">13.1.5.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="idm21396304" 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="idm21400256" 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">表13.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>表13.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>例13.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">
+ <code class="filename">/etc/httpd/conf.d/ssl.conf</code> ファイルが存在するには、<span class="package">mod_ssl</span> がインストールされている必要があることに注意してください。SSL サーバーのインストールと設定に関する詳細は<a class="xref" href="ch-Web_Servers.html#s2-apache-mod_ssl">「SSL サーバーのセットアップ」</a>を参照してください。
+ </div></div><div class="section" id="s3-apache-mpm-common"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.5.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="idm39564640" 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="idm39568448" 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>例13.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="idm35187984" 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>例13.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="idm61700336" 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>例13.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="idm61711696" 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>例13.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="idm51442800" 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>例13.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="idm18172576" 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>例13.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="idm49372640" 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>例13.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="idm49380272" 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>例13.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">13.1.6. Working with Modules</h3></div></div></div><a id="idm33903488" class="indexterm"></a><a id="idm33906080" 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">13.1.6.1. モジュールの読み込み方法</h4></div></div></div><a id="idm33913952" 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>例13.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. Refer to <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">13.1.6.2. モジュールの書き込み方法</h4></div></div></div><a id="idm46650384" 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, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum 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">13.1.7. 仮想ホストのセットアップ</h3></div></div></div><a id="idm47347232" class="indexterm"></a><a id="idm47351376" 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, hostname, or port is being requested.
+ </div><div class="para">
+ To create a name-based virtual host, find the virtual host container provided in <code class="filename">/etc/httpd/conf/httpd.conf</code> as an example, remove the hash sign (that is, <code class="literal">#</code>) from the beginning of each line, and customize the options according to your requirements as shown in <a class="xref" href="ch-Web_Servers.html#example-apache-virtualhosts-config">例13.80「仮想ホストのサンプル設定」</a>.
+ </div><div class="example" id="example-apache-virtualhosts-config"><h6>例13.80 仮想ホストのサンプル設定</h6><div class="example-contents"><pre class="programlisting">NameVirtualHost penguin.example.com:80
+
+<VirtualHost penguin.example.com:80>
+ ServerAdmin webmaster at penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName penguin.example.com:80
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.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. Refer to <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">13.1.8. SSL サーバーのセットアップ</h3></div></div></div><a id="idm68371280" class="indexterm"></a><a id="idm68373776" class="indexterm"></a><a id="idm68375824" class="indexterm"></a><a id="idm68377424" class="indexterm"></a><a id="idm49732464" class="indexterm"></a><a id="idm49727232" 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">13.1.8.1. 証明書とセキュリティの概要</h4></div></div></div><a id="idm49735984" class="indexterm"></a><a id="idm49737280" 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="idm51952224" class="indexterm"></a><a id="idm51954464" 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 hostname, 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 issued 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 hostname listed in the certificate does not match the hostname 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">表13.22「CA lists for most common web browsers」</a>.
+ </div><div class="table" id="table-apache-mod_ssl-certificates-authorities"><h6>表13.22 CA lists for most common web browsers</h6><div class="table-contents"><table summary="CA lists for most 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/">Mozilla root CA list</a>。
+ </td></tr><tr><td class="">
+ <span class="application"><strong>Opera</strong></span>
+ </td><td class="">
+ <a href="http://my.opera.com/rootstore/blog/">The Opera Rootstore</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">Windows root certificate program members</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">13.1.8.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, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install mod_ssl openssl</code></pre><a id="idm28676496" 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">13.1.8.3. Using an Existing Key and Certificate</h4></div></div></div><a id="idm28683328" class="indexterm"></a><a id="idm28686336" 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">
+ 上のケースのどちらかにおいて、新しい証明書を取得する必要があります。このトピックの詳細は、<a class="xref" href="ch-Web_Servers.html#s3-apache-mod_ssl-genkey">「新規キーおよび証明書の生成」</a>を参照してください。
+ </div><div class="para">
+ If you wish 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 running 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>例13.81 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">13.1.8.4. 新規キーおよび証明書の生成</h4></div></div></div><a id="idm48557584" class="indexterm"></a><a id="idm48559632" class="indexterm"></a><div class="para">
+ In order to generate a new key and certificate pair, you must to have the <span class="package">crypto-utils</span> package installed in your system. As <code class="systemitem">root</code>, you can install it by typing the following at a shell prompt:
+ </div><pre class="screen"><code class="command">yum 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, as <code class="systemitem">root</code>, 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 hostname 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">
+ ユーティリティを実行するには、<code class="systemitem">root</code> として、適切なホスト名をつけて (たとえば、<code class="systemitem">penguin.example.com</code>) <code class="command">genkey</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>図13.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">
+ <span class="keycap"><strong>上</strong></span> と <span class="keycap"><strong>下</strong></span> の矢印キーを使用して、適切なキーの大きさを選択します。大きなキーはセキュリティを向上させる一方、サーバーの応答時間も増加させることに注意してください。このため、推奨されるオプションは <code class="literal">1024 ビット</code> です。
+ </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>図13.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">
+ 証明書要求を証明書認証局に送信したいかどうかを決定します。
+ </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>図13.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>図13.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>図13.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>図13.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>図13.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">13.1.9. その他のリソース</h3></div></div></div><div class="para">
+ Apache HTTP Server に関してさらに詳細をお知りになりたい場合は、以下のリソースを参照してください。
+ </div><div class="section" id="s3-apache-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.9.1. インストールされているドキュメント</h4></div></div></div><a id="idm63166848" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://localhost/manual/">http://localhost/manual/</a></span></dt><dd><div class="para">
+ 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></dd><dt class="varlistentry"><span class="term"><code class="command">man httpd</code></span></dt><dd><div class="para">
+ <code class="systemitem">httpd</code> サービスのコマンドラインオプションの完全な一覧を含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man genkey</code></span></dt><dd><div class="para">
+ <code class="command">genkey</code> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd></dl></div></div><div class="section" id="s3-apache-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">13.1.9.2. 役に立つ Web サイト</h4></div></div></div><a id="idm41070256" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://httpd.apache.org/">http://httpd.apache.org/</a></span></dt><dd><div class="para">
+ The official website for the Apache HTTP Server with documentation on all the directives and default modules.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.modssl.org/">http://www.modssl.org/</a></span></dt><dd><div class="para">
+ <span class="application"><strong>mod_ssl</strong></span> モジュールの公式ウェブサイトです。
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.openssl.org/">http://www.openssl.org/</a></span></dt><dd><div class="para">
+ さらなるドキュメント、よくある質問、メーリングリストへのリンク、および他の有用なリソースがある OpenSSL のホームページです。
+ </div></dd></dl></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-additional-resources.html"><strong>戻る</strong>12.2.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="ch-Mail_Servers.html"><strong>次へ</strong>第14章 メールサーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html
new file mode 100644
index 0000000..571792a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.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>第22章 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Kernel_Module_and_Driver_Configuration.html" title="パート VII. カーネル、モジュールおよびドライバーの設定" /><link rel="prev" href="s2-kernel-boot-loader-pseries.html" title="21.6.3. Configuring the YABOOT Boot Loader" /><link rel="next" href="sec-Displaying_Information_About_a_Module.html" title="22.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">第22章 Working with Kernel Modules</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. モジュールの読み込み方法</a></span></dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module<
/a></span></dt><dt><span class="section"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sec-Specific_Kernel_Module_Capabilities.html">22.7. Specific Kernel Module Capabilities</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Specific_Kernel_Module_Capabilities.html#sec-Using_Multiple_Ethernet_Cards">22.7.1. 複数のイーサネットカードの使用</a></span></dt><dt><span class="section"><a href="sec-Using_Channel_Bonding.html">22.7.2. Using Channel Bonding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">22.8. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html#s2-kernel-modules-additional-resources-installed">22.8.1. インストー
ルされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-kernel-modules-additional-resources-websites.html">22.8.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></div><a id="idm70181296" class="indexterm"></a><a id="idp3030000" class="indexterm"></a><a id="idm66597152" 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">module-init-tools</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 and/or unload modules manually, such as when a module provides optional functionality, one module should be preferred over another although either could provide basic functionality, or when a module is misbehaving, among other situations.
+ </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="package">module-init-tools</span> package 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 module-init-tools package</h2></div><div class="admonition"><div class="para">
+ In order to use the kernel module utilities described in this chapter, first ensure the module-init-tools package is installed on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install module-init-tools</code>
+</pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は <a class="xref" href="sec-Installing.html">「パッケージのインストール」</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">22.1. Listing Currently-Loaded Modules</h2></div></div></div><a id="idm54277824" class="indexterm"></a><a id="idm62748992" class="indexterm"></a><a id="idm62746592" 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
+xfs 803635 1
+exportfs 3424 1 xfs
+vfat 8216 1
+fat 43410 1 vfat
+tun 13014 2
+fuse 54749 2
+ip6table_filter 2743 0
+ip6_tables 16558 1 ip6table_filter
+ebtable_nat 1895 0
+ebtables 15186 1 ebtable_nat
+ipt_MASQUERADE 2208 6
+iptable_nat 5420 1
+nf_nat 19059 2 ipt_MASQUERADE,iptable_nat
+rfcomm 65122 4
+ipv6 267017 33
+sco 16204 2
+bridge 45753 0
+stp 1887 1 bridge
+llc 4557 2 bridge,stp
+bnep 15121 2
+l2cap 45185 16 rfcomm,bnep
+cpufreq_ondemand 8420 2
+acpi_cpufreq 7493 1
+freq_table 3851 2 cpufreq_ondemand,acpi_cpufreq
+usb_storage 44536 1
+sha256_generic 10023 2
+aes_x86_64 7654 5
+aes_generic 27012 1 aes_x86_64
+cbc 2793 1
+dm_crypt 10930 1
+kvm_intel 40311 0
+kvm 253162 1 kvm_intel
+<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, refer to <a class="xref" href="sec-Unloading_a_Module.html">「Unloading a Module」</a>.
+ </div></li></ul></div><a id="idm30984000" 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>21.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>22.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/17/html/System_Administrators_Guide/ch-kdump.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-kdump.html
new file mode 100644
index 0000000..a48c529
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-kdump.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>第23章 The kdump Crash Recovery 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="part-Kernel_Module_and_Driver_Configuration.html" title="パート VII. カーネル、モジュールおよびドライバーの設定" /><link rel="prev" href="s2-kernel-modules-additional-resources-websites.html" title="22.8.2. 役に立つ Web サイト" /><link rel="next" href="s1-kdump-configuration.html" title="23.2. Configuring the kdump 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="docna
v"><li class="previous"><a accesskey="p" href="s2-kernel-modules-additional-resources-websites.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-kdump-configuration.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="chapter" id="ch-kdump" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第23章 The kdump Crash Recovery Service</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-kdump.html#s1-kdump-installation">23.1. Installing the kdump Service</a></span></dt><dt><span class="section"><a href="s1-kdump-configuration.html">23.2. Configuring the kdump Service</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kdump-configuration.html#s2-kdump-configuration-firstboot">23.2.1. Configuring the kdump at First Boot</a></span></dt><dt><span class="section"><a href="s2-kdump-configuration-gui.html">23.2.2. Using the Kernel Dump Configuration Utility</a></span></dt><dt><span cla
ss="section"><a href="s2-kdump-configuration-cli.html">23.2.3. Configuring kdump on the Command Line</a></span></dt><dt><span class="section"><a href="s2-kdump-configuration-testing.html">23.2.4. Testing the Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kdump-crash.html">23.3. Analyzing the Core Dump</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kdump-crash.html#s2-kdump-crash-running">23.3.1. Running the crash Utility</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-log.html">23.3.2. Displaying the Message Buffer</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-backtrace.html">23.3.3. Displaying a Backtrace</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-processes.html">23.3.4. Displaying a Process Status</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-memory.html">23.3.5. Displaying Virtual Memory Information</a></span></dt><dt><span class="section"><a href="s2-k
dump-crash-files.html">23.3.6. Displaying Open Files</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-exit.html">23.3.7. Exiting the Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kdump-resources.html">23.4. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kdump-resources.html#s2-kdump-resources-installed">23.4.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-kdump-resources-online.html">23.4.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></div><div class="para">
+ When the <code class="systemitem">kdump</code> crash dumping mechanism is enabled, the system is booted from the context of another kernel. This second kernel reserves a small amount of memory and its only purpose is to capture the core dump image in case the system crashes.
+ </div><div class="para">
+ Being able to analyze the core dump significantly helps to determine the exact cause of the system failure, and it is therefore strongly recommended to have this feature enabled. This chapter explains how to configure, test, and use the <code class="systemitem">kdump</code> service in Fedora, and provides a brief overview of how to analyze the resulting core dump using the <span class="application"><strong>crash</strong></span> debugging utility.
+ </div><div class="section" id="s1-kdump-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">23.1. Installing the kdump Service</h2></div></div></div><a id="idm47676800" class="indexterm"></a><div class="para">
+ In order use the <code class="systemitem">kdump</code> service on your system, make sure you have the <span class="package">kexec-tools</span> package installed. To do so, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install kexec-tools</code></pre><div class="para">
+ For more information on how to install new packages in Fedora, refer to <a class="xref" href="sec-Installing.html">「パッケージのインストール」</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-modules-additional-resources-websites.html"><strong>戻る</strong>22.8.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="s1-kdump-configuration.html"><strong>次へ</strong>23.2. Configuring the kdump Service</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-proc.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-proc.html
new file mode 100644
index 0000000..6f1980c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-proc.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>付録E The proc File 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s1-sysconfig-additional-resources.html" title="D.3. その他のリソース" /><link rel="next" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File 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="previous"><a accesskey="p" href="s1-sysconfig-additional-resources.html"><strong>戻ã‚
‹</strong></a></li><li class="next"><a accesskey="n" href="s1-proc-topfiles.html"><strong>次ã¸</strong></a></li></ul><div xml:lang="ja-JP" class="appendix" id="ch-proc" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">The proc File System</h1></div></div></div><a id="idm52574784" class="indexterm"></a><a id="idm61327232" class="indexterm"></a><div class="para">
+ The Linux kernel has two primary functions: to control access to physical devices on the computer and to schedule when and how processes interact with these devices. The <code class="filename">/proc/</code> directory (also called the <code class="filename">proc</code> file system) contains a hierarchy of special files which represent the current state of the kernel, allowing applications and users to peer into the kernel's view of the system.
+ </div><div class="para">
+ The <code class="filename">/proc/</code> directory contains a wealth of information detailing system hardware and any running processes. In addition, some of the files within <code class="filename">/proc/</code> can be manipulated by users and applications to communicate configuration changes to the kernel.
+ </div><div class="note"><div class="admonition_header"><h2>The /proc/ide/ and /proc/pci/ directories</h2></div><div class="admonition"><div class="para">
+ Later versions of the 2.6 kernel have made the <code class="filename">/proc/ide/</code> and <code class="filename">/proc/pci/</code> directories obsolete. The <code class="command">/proc/ide/</code> file system is now superseded by files in <code class="command">sysfs</code>; to retrieve information on PCI devices, use <code class="command">lspci</code> instead. For more information on <code class="command">sysfs</code> or <code class="command">lspci</code>, refer to their respective <code class="command">man</code> pages.
+ </div></div></div><div class="section" id="s1-proc-virtual"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.1. A Virtual File System</h2></div></div></div><a id="idm52282912" class="indexterm"></a><a id="idm50350000" class="indexterm"></a><a id="idm50347888" class="indexterm"></a><div class="para">
+ Linux systems store all data as <span class="emphasis"><em>files</em></span>. Most users are familiar with the two primary types of files: text and binary. But the <code class="filename">/proc/</code> directory contains another type of file called a <em class="firstterm">virtual file</em>. As such, <code class="filename">/proc/</code> is often referred to as a <em class="firstterm">virtual file system</em>.
+ </div><div class="para">
+ Virtual files have unique qualities. Most of them are listed as zero bytes in size, but can still contain a large amount of information when viewed. In addition, most of the time and date stamps on virtual files reflect the current time and date, indicative of the fact they are constantly updated.
+ </div><div class="para">
+ Virtual files such as <code class="filename">/proc/interrupts</code>, <code class="filename">/proc/meminfo</code>, <code class="filename">/proc/mounts</code>, and <code class="filename">/proc/partitions</code> provide an up-to-the-moment glimpse of the system's hardware. Others, like the <code class="filename">/proc/filesystems</code> file and the <code class="filename">/proc/sys/</code> directory provide system configuration information and interfaces.
+ </div><div class="para">
+ For organizational purposes, files containing information on a similar topic are grouped into virtual directories and sub-directories. Process directories contain information about each running process on the system.
+ </div><div class="section" id="s2-proc-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.1.1. Viewing Virtual Files</h3></div></div></div><a id="idm31024464" class="indexterm"></a><a id="idm27457568" class="indexterm"></a><div class="para">
+ Most files within <code class="filename">/proc/</code> files operate similarly to text files, storing useful system and hardware data in human-readable text format. As such, you can use <code class="command">cat</code>, <code class="command">more</code>, or <code class="command">less</code> to view them. For example, to display information about the system's CPU, run <code class="command">cat /proc/cpuinfo</code>. This will return output similar to the following:
+ </div><pre class="screen">
+processor : 0
+vendor_id : AuthenticAMD
+cpu family : 5
+model : 9
+model name : AMD-K6(tm) 3D+
+Processor stepping : 1 cpu
+MHz : 400.919
+cache size : 256 KB
+fdiv_bug : no
+hlt_bug : no
+f00f_bug : no
+coma_bug : no
+fpu : yes
+fpu_exception : yes
+cpuid level : 1
+wp : yes
+flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
+bogomips : 799.53
+</pre><div class="para">
+ Some files in <code class="command">/proc/</code> contain information that is not human-readable. To retrieve information from such files, use tools such as <code class="command">lspci</code>, <code class="command">apm</code>, <code class="command">free</code>, and <code class="command">top</code>.
+ </div><div class="note"><div class="admonition_header"><h2>Certain files can only be accessed with root privileges</h2></div><div class="admonition"><div class="para">
+ Some of the virtual files in the <code class="filename">/proc/</code> directory are readable only by the root user.
+ </div></div></div></div><div class="section" id="s2-proc-change"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.1.2. Changing Virtual Files</h3></div></div></div><a id="idm26496480" class="indexterm"></a><a id="idm26494848" class="indexterm"></a><div class="para">
+ As a general rule, most virtual files within the <code class="filename">/proc/</code> directory are read-only. However, some can be used to adjust settings in the kernel. This is especially true for files in the <code class="filename">/proc/sys/</code> subdirectory.
+ </div><div class="para">
+ To change the value of a virtual file, use the following command:
+ </div><div class="para">
+ <code class="command">echo <em class="replaceable"><code>value</code></em> > /proc/<em class="replaceable"><code>file</code></em> </code>
+ </div><div class="para">
+ For example, to change the hostname on the fly, run:
+ </div><div class="para">
+ <code class="command">echo <em class="replaceable"><code>www.example.com</code></em> > /proc/sys/kernel/hostname </code>
+ </div><div class="para">
+ Other files act as binary or Boolean switches. Typing <code class="command">cat /proc/sys/net/ipv4/ip_forward</code> returns either a <code class="computeroutput">0</code> (off or false) or a <code class="computeroutput">1</code> (on or true). A <code class="computeroutput">0</code> indicates that the kernel is not forwarding network packets. To turn packet forwarding on, run <code class="command">echo 1 > /proc/sys/net/ipv4/ip_forward</code>.
+ </div><div class="note"><div class="admonition_header"><h2>The sysctl command</h2></div><div class="admonition"><div class="para">
+ Another command used to alter settings in the <code class="filename">/proc/sys/</code> subdirectory is <code class="command">/sbin/sysctl</code>. For more information on this command, refer to <a class="xref" href="s1-proc-sysctl.html">「Using the sysctl Command」</a>
+ </div></div></div><div class="para">
+ For a listing of some of the kernel configuration files available in the <code class="filename">/proc/sys/</code> subdirectory, refer to <a class="xref" href="s2-proc-dir-sys.html">「 /proc/sys/ 」</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysconfig-additional-resources.html"><strong>戻る</strong>D.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-proc-topfiles.html"><strong>次へ</strong>E.2. Top-level Files within the proc File System</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-yum.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-yum.html
new file mode 100644
index 0000000..3bff259
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch-yum.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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章 Yum</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="4.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-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-yum" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第4ç« Yum</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">4.1. パッケージã®ç¢ºèªã¨æ›´æ–°</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">4.1.1. æ›´æ–°ã®ç¢ºèª</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">4.1.2. パッケージã®æ›´æ–°</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">4.1.3. è¨å®šãƒ•ã‚¡ã‚¤ãƒ«å¤‰æ›´ã®ä¿å˜</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">4.2. パッケージã¨ãƒ‘ッケージ グルーã
ƒ—</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">4.2.1. パッケージã®æ¤œç´¢</a></span></dt><dt><span class="section"><a href="sec-Listing_Packages.html">4.2.2. パッケージã®ä¸€è¦§</a></span></dt><dt><span class="section"><a href="sec-Displaying_Package_Information.html">4.2.3. ãƒ‘ãƒƒã‚±ãƒ¼ã‚¸æƒ…å ±ã®è¡¨ç¤º</a></span></dt><dt><span class="section"><a href="sec-Installing.html">4.2.4. パッケージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«</a></span></dt><dt><span class="section"><a href="sec-Removing.html">4.2.5. パッケージã®å‰Šé™¤</a></span></dt><dt><span class="section"><a href="sec-Yum-Transaction_History.html">4.2.6. 処ç†ã¨ãƒˆãƒ©ãƒ³ã‚¶ã‚¯ã‚·ãƒ§ãƒ³ã®å±¥æ´</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">4.3. Yum 㨠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¨å®š</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositor
ies.html#sec-Setting_main_Options">4.3.1. [main] オプションの設定</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">4.3.2. [repository] オプションの設定</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">4.3.3. Yum 変数の使い方</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Current_Configuration.html">4.3.4. 現在の設定の表示</a></span></dt><dt><span class="section"><a href="sec-Managing_Yum_Repositories.html">4.3.5. Yum リポジトリの追加・有効化および無効化</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">4.3.6. Yum リポジトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">4.4. Yum プラグイン</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Yum プラグインの無
効化、有効化、設定</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">4.4.2. 追加の Yum プラグインのインストール</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">4.4.3. プラグインの説明</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Additional_Resources.html">4.5. その他のリソース</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> は、パッケージに関する情報を問い合わせる、リポジトリからパッケージを取得する、自動的に依存解決を使用してパッケージをインストールおよびアンインストールする、システム全体を最新の利用可能なパッケージに更新することができる、The Fedora Project パッケージマネージャーです。Yum は更新、インストール、削除しているパッケージの依存解決を自動的に実行します。このように、利用可能な依存するパッケージをすべて自動的に決定、取得、インストールできます。Yum は新規リポジトリ、追加リポジトリ、または<em class="firstterm">パッケージソース</em>を用いて設定できます。また、機能を向上および拡張させる多くのプラグインも提供します。Yum は <span class="application"><strong>RPM</s
trong></span> ができるのと同じ作業の多くを実行できます。さらに、同様のコマンドラインオプションを持ちます。Yum は単独のマシンまたはそれらのグループにおいて簡単でシンプルなパッケージ管理をできるようにします。
+ </div><div class="important" id="important-Secure_Package_Management_with_GPG-Signed_Packages"><div class="admonition_header"><h2>GPG 署名パッケージを用いたセキュアなパッケージ管理</h2></div><div class="admonition"><div class="para">
+ Yum は GPG 署名されたパッケージにおいて GPG (Gnu Privacy Guard、GnuPGとしても知られています) 署名の検証を、すべてのパッケージリポジトリまたは個々のリポジトリに対して有効にすることによりセキュアなパッケージ管理を提供します。署名検証が有効にされたとき、Yum はリポジトリに対して正しいキーを用いて GPG 署名されていないあらゆるパッケージをインストールすることを拒否します。つまり、The Fedora Project のような信頼されたソースからシステムにダウンロードしてインストールして、転送中に変更されていないことを信頼できます。Yum を用いて署名検証を有効にすることに関する詳細は<a class="xref" href="sec-Configuring_Yum_and_Yum_Repositories.html">「Yum と Yum リポジトリーの設定」</a>を参照してください、または一般に GPG 署名さ
れた <span class="application"><strong>RPM</strong></span> パッケージを検証することについては<a class="xref" href="s1-check-rpm-sig.html">「パッケージの署名を確認する」</a>を参照してください。
+ </div></div></div><div class="para">
+ Yum は他のマシンにある <span class="application"><strong>RPM</strong></span> パッケージのダウンロードとインストールのために自身のリポジトリを簡単に設定することができます。
+ </div><div class="para">
+ Yum はシステム管理作業を実行する最も速い方法であり、<span class="application"><strong>PackageKit</strong></span> グラフィカルパッケージ管理アプリケーションにより提供されるものを超えた機能を提供するので、Yum を学習することは価値のある投資です。<span class="application"><strong>PackageKit</strong></span> の使い方の詳細は<a class="xref" href="ch-PackageKit.html">5章<em>PackageKit</em></a>を参照してください。
+ </div><div class="note" id="note-Note_Yum_and_Superuser_Privileges"><div class="admonition_header"><h2>Yum とスーパーユーザー権限</h2></div><div class="admonition"><div class="para">
+ インストールに <code class="command">yum</code> を使用するためには、スーパーユーザー権限を持っていなければいけません。本章にあるすべての例は、<code class="command">su</code> または <code class="command">sudo</code> コマンドを使用することにより、スーパーユーザー権限をすでに持っていることを前提にしています。
+ </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">4.1. パッケージの確認と更新</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">4.1.1. 更新の確認</h3></div></div></div><a id="idm46444576" class="indexterm"></a><div class="para">
+ システムにインストールされているパッケージが利用可能な更新があるかを確認するには、以下のコマンドを使用します
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">check-update</code></pre><div class="para">
+ 例:
+ </div><pre class="screen">~]# <code class="command">yum check-update</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+
+PackageKit.x86_64 0.6.14-2.fc15 fedora
+PackageKit-command-not-found.x86_64 0.6.14-2.fc15 fedora
+PackageKit-device-rebind.x86_64 0.6.14-2.fc15 fedora
+PackageKit-glib.x86_64 0.6.14-2.fc15 fedora
+PackageKit-gstreamer-plugin.x86_64 0.6.14-2.fc15 fedora
+PackageKit-gtk-module.x86_64 0.6.14-2.fc15 fedora
+PackageKit-gtk3-module.x86_64 0.6.14-2.fc15 fedora
+PackageKit-yum.x86_64 0.6.14-2.fc15 fedora
+PackageKit-yum-plugin.x86_64 0.6.14-2.fc15 fedora
+gdb.x86_64 7.2.90.20110429-36.fc15 fedora
+kernel.x86_64 2.6.38.6-26.fc15 fedora
+rpm.x86_64 4.9.0-6.fc15 fedora
+rpm-libs.x86_64 4.9.0-6.fc15 fedora
+rpm-python.x86_64 4.9.0-6.fc15 fedora
+yum.noarch 3.2.29-5.fc15 fedora</pre><div class="para">
+ 上の出力にあるパッケージは利用可能な更新があるものとして一覧化されています。一覧にある最初のパッケージは <span class="application"><strong>PackageKit</strong></span> というグラフィカルパッケージマネージャーです。出力例にある行は次のことを意味します:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">PackageKit</code> — パッケージの名前
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">x86_64</code> — パッケージがビルトされた対象の CPU アーキテクチャー
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">0.6.14</code> — インストールされる更新パッケージのバージョン
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">fedora</code> — 更新パッケージが置かれているリポジトリー
+ </div></li></ul></div><div class="para">
+ カーネル（kernel パッケージ）、Yum および <span class="application"><strong>RPM</strong></span> 自身（<code class="filename">yum</code> および <code class="filename">rpm</code> パッケージ）だけでなく、その依存物（<span class="package">kernel-firmware</span>, <span class="package">rpm-libs</span>, および <span class="package">rpm-python</span> パッケージのような）をすべて <code class="command">yum</code> を使用して更新できることを出力は示しています。
+ </div></div><div class="section" id="sec-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.2. パッケージの更新</h3></div></div></div><a id="idm65829104" class="indexterm"></a><div class="para">
+ 単一パッケージ、複数パッケージまたは全パッケージを一度に更新することを選べます。更新するパッケージに依存するあらゆるものに利用可能な更新があれば、それらも更新されます。
+ </div><h4 id="bh-Updating_a_Single_Package">シンプルなパッケージの更新</h4><a id="idm65826368" class="indexterm"></a><div class="para">
+ <code class="systemitem">root</code> で次のコマンドを実行し、ひとつのパッケージを更新します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">update</code> <em class="replaceable"><code>package_name</code></em></pre><div class="para">
+ たとえば、<span class="package">udev</span> パッケージを更新するには、次のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">yum update udev</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Updating Red Hat repositories.
+INFO:rhsm-app.repolib:repos updated: 0
+Setting up Update Process
+Resolving Dependencies
+--> Running transaction check
+---> Package gdb.x86_64 0:7.2.90.20110411-34.fc15 will be updated
+---> Package gdb.x86_64 0:7.2.90.20110429-36.fc15 will be an update
+--> Finished Dependency Resolution
+
+Dependencies Resolved
+
+================================================================================
+ Package Arch Version Repository Size
+================================================================================
+Updating:
+ gdb x86_64 7.2.90.20110429-36.fc15 fedora 1.9 M
+
+Transaction Summary
+================================================================================
+Upgrade 1 Package(s)
+
+Total download size: 1.9 M
+Is this ok [y/N]:</pre><div class="para">
+ この出力は関心がある項目をいくつか含んでいます:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="computeroutput">Loaded plugins:</code> — <code class="command">yum</code> はインストールされて有効にされている <span class="application"><strong>Yum</strong></span> プラグインを必ず通知します。ここでは、<code class="command">yum</code> が <span class="application"><strong>langpacks</strong></span>, <span class="application"><strong>presto</strong></span>, および <span class="application"><strong>refresh-packagekit</strong></span> プラグインを使用しています。<span class="application"><strong>Yum</strong></span> プラグインに関する一般的な情報は<a class="xref" href="sec-Yum_Plugins.html">「Yum プラグイン」</a>を参照してください、または特定のプラグインの説明は<a class="xref" href="sec-Plugin_Descriptions.html">「プラグインの説明」</a>を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">gdb.x86_64</code> — 新しい <span class="package">gdb</span> パッケージのダウンロードとインストールができます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum</code> は、更新の情報を表示して、更新を実行したいかどうかを確認します。<code class="command">yum</code> はデフォルトで対話的に動作します。どのトランザクションが実行する <code class="command">yum</code> 計画をすでに知っているならば、<code class="command">yum</code> が尋ねてくる質問にすべて <code class="command">yes</code> を答えるように <code class="option">-y</code> オプションを使用できます（非対話的に実行する場合です）。しかしながら、発生したあらゆる問題を簡単にトラブルシューティングできるように、どのような変更がシステムに対して行われるか <code class="command">yum</code> 計画を常に確認すべきです。
+ </div><div class="para">
+ トランザクションがうまくいかなければ、<a class="xref" href="sec-Yum-Transaction_History.html">「処理とトランザクションの履歴」</a> に説明されているように <code class="command">yum history</code> コマンドを使用することにより、 Yum のトランザクション履歴を表示することができます。
+ </div></li></ol></div><div class="important" id="important-Important-Updating_and_Installing_Kernels_with_Yum"><div class="admonition_header"><h2>Yum でのカーネルのインストールとアップグレード</h2></div><div class="admonition"><div class="para">
+ コマンド <code class="command">rpm -i kernel</code> を使用するときに <span class="application"><strong>RPM</strong></span> が新しいカーネルをインストールするのと同じ意味で、<code class="command">yum</code> は必ず新しいカーネルを<span class="emphasis"><em>インストール</em></span>します。そのため、<code class="command">yum</code> を使用するときにカーネルを<span class="emphasis"><em>インストール</em></span>するのか<span class="emphasis"><em>更新</em></span>するのかについて心配する必要がありません。 <code class="command">yum update</code> または <code class="command">yum install</code> コマンドのどちらを使用しているかに関わらず、適切なものを実行します。
+ </div><div class="para">
+ 一方、<span class="application"><strong>RPM</strong></span> を使用しているときは、<code class="command">rpm -u kernel</code> (現在のカーネルを<span class="emphasis"><em>置き換えます</em></span>) の代わりに、<code class="command">rpm -i kernel</code> コマンド (新しいカーネルをインストールします) を使用することが重要です。<span class="application"><strong>RPM</strong></span> を用いたカーネルのインストール/アップグレードの詳細は<a class="xref" href="sec-Installing_and_Upgrading.html">「インストールとアップグレード」</a>を参照してください。
+ </div></div></div><h4 id="bh-Updating_All_Packages_and_Their_Dependencies">全パッケージおよびそれらの依存性の更新</h4><a id="idm55134704" class="indexterm"></a><div class="para">
+ すべてのパッケージとそれに依存するものを更新するには、単に <code class="command">yum update</code> と入力します（引数は何もありません）:
+ </div><pre class="screen"><code class="command">yum update</code></pre><h4 id="bh-Updating_Security-Related_Packages">セキュリティ関連のパッケージの更新</h4><a id="idm75088288" class="indexterm"></a><a id="idm75086880" class="indexterm"></a><a id="idm75085504" class="indexterm"></a><div class="para">
+ 利用可能なセキュリティ更新を持つパッケージを発見すること、そしてそれらのパッケージを迅速かつ簡単に更新することは重要です。Yum はこの目的のためのプラグインを提供します。<span class="application"><strong>security</strong></span> プラグインはセキュリティ中心のコマンド、サブコマンドおよびオプションの組を用いて <code class="command">yum</code> コマンドを拡張します。具体的な情報は<a class="xref" href="sec-Plugin_Descriptions.html">「プラグインの説明」</a>を参照してください。
+ </div></div><div class="section" id="sec-Preserving_Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.3. 設定ファイル変更の保存</h3></div></div></div><a id="idm54064208" class="indexterm"></a><div class="para">
+ あなたは自分の Fedora システムを使用するので、パッケージによりインストールされた設定ファイルに必ず変更するでしょう。Yum がシステムに変更を実行するために使用する <span class="application"><strong>RPM</strong></span> は、それらの完全性を保証するためのメカニズムを提供します。パッケージの更新をまたがり設定ファイルへの変更を管理する方法の詳細は<a class="xref" href="sec-Installing_and_Upgrading.html">「インストールとアップグレード」</a>を参照してください。
+ </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>4.2. パッケージとパッケージ グループ</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch11s02s03.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch11s02s03.html
new file mode 100644
index 0000000..3b754f5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ch11s02s03.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-dhcp-configuring-server.html" title="11.2. DHCP サーバーの設定" /><link rel="prev" href="lease-database.html" title="11.2.2. リースデータベース" /><link rel="next" href="dhcp-relay-agent.html" title="11.2.4. DHCP リレーエージェント" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="lease-database.html"><strong>戻る</strong></a></l
i><li class="next"><a accesskey="n" href="dhcp-relay-agent.html"><strong>次へ</strong></a></li></ul><div class="section" id="idm38116608"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm38116608">11.2.3. サーバーの起動と停止</h3></div></div></div><a id="idm38115840" class="indexterm"></a><a id="idm38114240" class="indexterm"></a><a id="idm61581808" class="indexterm"></a><a id="idm61579696" class="indexterm"></a><div class="important"><div class="admonition_header"><h2>DHCP サーバーの始めての起動</h2></div><div class="admonition"><div class="para">
+ When the DHCP server is started for the first time, it fails unless the <code class="filename">dhcpd.leases</code> file exists. Use the command <code class="command">touch /var/lib/dhcpd/dhcpd.leases</code> to create the file if it does not exist.
+ </div><div class="para">
+ If the same server is also running BIND as a DNS server, this step is not necessary, as starting the <code class="command">named</code> service automatically checks for a <code class="filename">dhcpd.leases</code> file.
+ </div></div></div><div class="para">
+ DHCP サーバーを開始するには、次のとおり入力します:
+ </div><pre class="screen"><code class="command">systemctl start dhcpd.service</code></pre><div class="para">
+ DHCP サーバーを停止するには、次のとおり入力します:
+ </div><pre class="screen"><code class="command">systemctl stop dhcpd.service</code></pre><div class="para">
+ デフォルトで、DHCP サービスはブート時に開始しません。ブート時に自動的に開始するようデーモンを設定するには、以下を実行します:
+ </div><pre class="screen"><code class="command">systemctl enable dhcpd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法の詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div><a id="idm46679680" class="indexterm"></a><a id="idm46678048" class="indexterm"></a><div class="para">
+ If more than one network interface is attached to the system, but the DHCP server should only be started on one of the interfaces, configure the DHCP server to start only on that device. In <code class="filename">/etc/sysconfig/dhcpd</code>, add the name of the interface to the list of <code class="command">DHCPDARGS</code>:
+ </div><pre class="programlisting"># Command line options here
+DHCPDARGS=eth0</pre><div class="para">
+ これは、ネットワークカードが2つあるファイアウォールマシンに便利な機能です。一方のネットワークカードを DHCP クライアントとして設定してインターネット用の IP アドレスを取得します。もう一方のネットワークカードは、ファイアウォール内の内部ネットワーク用の DHCP サーバーとして使用できます。内部ネットワークに接続されたネットワークカードだけを指定することにより、ユーザーがインターネット経由でデーモンに接続できなくなるので、システムがより安全になります。
+ </div><div class="para">
+ Other command line options that can be specified in <code class="filename">/etc/sysconfig/dhcpd</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-p <em class="replaceable"><code>portnum</code></em> </code> — Specifies the UDP port number on which <code class="command">dhcpd</code> should listen. The default is port 67. The DHCP server transmits responses to the DHCP clients at a port number one greater than the UDP port specified. For example, if the default port 67 is used, the server listens on port 67 for requests and responses to the client on port 68. If a port is specified here and the DHCP relay agent is used, the same port on which the DHCP relay agent should listen must be specified. Refer to <a class="xref" href="dhcp-relay-agent.html">「DHCP リレーエージェント」</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f</code> — Runs the daemon as a foreground process. This is mostly used for debugging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> — Logs the DHCP server daemon to the standard error descriptor. This is mostly used for debugging. If this is not specified, the log is written to <code class="filename">/var/log/messages</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-cf <em class="replaceable"><code>filename</code></em> </code> — Specifies the location of the configuration file. The default location is <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-lf <em class="replaceable"><code>filename</code></em> </code> — Specifies the location of the lease database file. If a lease database file already exists, it is very important that the same file be used every time the DHCP server is started. It is strongly recommended that this option only be used for debugging purposes on non-production machines. The default location is <code class="filename">/var/lib/dhcpd/dhcpd.leases</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-q</code> — デーモンを起動するときに全体の著作権メッセージを表示しません。
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="lease-database.html"><strong>戻る</strong>11.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="dhcp-relay-agent.html"><strong>次へ</strong>11.2.4. DHCP リレーエージェント</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Configuring_Domains.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Configuring_Domains.html
new file mode 100644
index 0000000..11d2434
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Configuring_Domains.html
@@ -0,0 +1,290 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5. Configuring Domains</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Configuring_Services.html" title="9.2.4. サービスの設定" /><link rel="next" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html" title="9.2.6. Setting Up Kerberos 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="d
ocnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>次へ</strong></a></li></ul><div class="section" id="chap-SSSD_User_Guide-Configuring_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.5. Configuring Domains</h3></div></div></div><div class="para">
+ A domain is a database of user information. SSSD can use more than one domain at the same time, but at least one must be configured for SSSD to start. Using SSSD domains, it is possible to use several LDAP servers providing several unique namespaces. You can specify not only where users' identity information is stored, but how users authenticate against each of the specified domains.
+ </div><div class="para">
+ SSSD supports the following identity and authentication combinations:
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">LDAP/LDAP</span></dt><dd><div class="para">
+ This combination uses an LDAP back end as both the identity and authentication provider. For more information, refer to <a class="xref" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">「Configuring an LDAP Domain」</a>.
+ </div></dd><dt class="varlistentry"><span class="term">LDAP/KRB5</span></dt><dd><div class="para">
+ This combination uses an LDAP back end as the identity provider, and uses Kerberos to provide authentication. For more information, refer to <a class="xref" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">「Setting Up Kerberos Authentication」</a>.
+ </div></dd><dt class="varlistentry"><span class="term">proxy</span></dt><dd><div class="para">
+ Specifying a proxy identity or an authentication provider uses an existing NSS library or a customized PAM stack, but takes advantage of the SSSD caching mechanism. For more information, refer to <a class="xref" href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html">「Configuring a Proxy Domain」</a>.
+ </div></dd></dl></div>
+
+ </div><div class="para">
+ The following example assumes that SSSD is correctly configured and FOO is one of the domains in the <code class="literal">[sssd]</code> section. This example shows only the configuration of Kerberos authentication; it does not include any identity provider.
+ </div><pre class="screen">[domain/FOO]
+auth_provider = krb5
+krb5_server = 192.168.1.1
+krb5_realm = EXAMPLE.COM</pre><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Domain_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.5.1. Domain Configuration Options</h4></div></div></div><div class="para">
+ You can add new domain configurations to the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> sections of the <code class="filename">/etc/sssd/sssd.conf</code> file, and then add the list of domains to the <em class="parameter"><code>domains</code></em> attribute of the <code class="literal">[sssd]</code> section, in the order you want them to be queried.
+ </div><div class="section" id="sect-SSSD_User_Guide-Domain_Configuration_Options-General_Domain_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.5.1.1. General Domain Configuration Options</h5></div></div></div><div class="para">
+ You can use the following configuration options in a domain configuration section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">min_id,max_id <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the UID and GID limits for the domain. If a domain contains entries that are outside these limits, they are ignored.
+ </div><div class="para">
+ The default value for <code class="option">min_id</code> is <code class="literal">1</code>; the default value for <code class="option">max_id</code> is <code class="literal">0</code> (unbounded).
+ </div><div class="important"><div class="admonition_header"><h2>Avoid conflicts with users in /etc/passwd</h2></div><div class="admonition"><div class="para">
+ If <code class="option">min_id</code> is unspecified, it defaults to <code class="literal">1</code> for any back end. This default was chosen to provide compatibility with existing systems and to ease any migration attempts. LDAP administrators should be aware that granting identities in this range may conflict with users in the local <code class="filename">/etc/passwd</code> file. To avoid these conflicts, <code class="option">min_id</code> should be set to <code class="literal">1000</code> or higher wherever possible.
+ </div><div class="para">
+ The <code class="option">min_id</code> option determines the minimum acceptable value for both UID and GID numbers. Accounts with either UID or GID values below the <code class="option">min_id</code> value are filtered out and not made available on the client.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">enumerate <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not to enumerate (list) the users and groups of a domain.
+ </div><div class="para">
+ Enumeration means that the entire set of available users and groups on the remote source is cached on the local machine. When enumeration is disabled, users and groups are only cached as they are requested.
+ </div><div class="warning"><div class="admonition_header"><h2>Disable enumeration for domains with many users and groups</h2></div><div class="admonition"><div class="para">
+ If a client has enumeration enabled, reinitialization of the client results in a complete refresh of the entire set of available users and groups from the remote source. Similarly, when SSSD is connected to a new server, the entire set of available users and groups from the remote source is pulled and cached on the local machine. In a domain with a large amount of clients connected to a remote source, both aforementioned cases can affect the network performance due to frequent queries from the clients. If the set of available users and groups is large enough, it will affect the performance of clients as well. For performance reasons, it is recommended that you disable enumeration for domains with many users and groups.
+ </div></div></div><div class="para">
+ The default value for this parameter is <code class="literal">FALSE</code>. Set this value to <code class="literal">TRUE</code> to enable enumeration of users and groups of a domain.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the timeout in seconds for this particular domain.
+ </div><div class="para">
+ This is used to ensure that the back end process is alive and capable of answering requests. The default value for this parameter is <code class="literal">10</code> seconds. Raising this timeout might prove useful for slower back ends, such as distant LDAP servers.
+ </div><div class="note"><div class="admonition_header"><h2>Changing the timeout value to 0</h2></div><div class="admonition"><div class="para">
+ If you set <code class="option">timeout = 0</code>, SSSD reverts to the default value; you cannot force a timeout value of zero, because this would force the <code class="systemitem">sssd</code> daemon into a loop.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">cache_credentials <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not to store user credentials in the local SSSD domain database cache.
+ </div><div class="para">
+ The default value for this parameter is <code class="literal">FALSE</code>. You should set this value to <code class="literal">TRUE</code> for domains other than local if you want to enable offline authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">id_provider <span class="type">(string)</span> </code>
+ </div><div class="para">
+ Specifies the data provider identity back end to use for this domain. Currently supported identity back ends are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ proxy — Support a legacy <code class="systemitem">NSS</code> provider (for example, <span class="package">nss_nis</span>).
+ </div><div class="note"><div class="admonition_header"><h2>Changing the id_provider value to proxy</h2></div><div class="admonition"><div class="para">
+ SSSD needs to know which legacy NSS library to load in order to start successfully. If you set <code class="option">id_provider</code> to <code class="literal">proxy</code>, ensure that you also specify a value for <code class="option">proxy_lib_name</code>. Refer to <a class="xref" href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html">「Configuring a Proxy Domain」</a> for information on this attribute.
+ </div></div></div></li><li class="listitem"><div class="para">
+ local — <code class="systemitem">SSSD</code> internal local provider.
+ </div></li><li class="listitem"><div class="para">
+ ldap — <code class="systemitem">LDAP</code> provider.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_cache_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long the domain's data provider should cache positive cache hits (that is, queries for valid database entries) before asking the database again.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">use_fully_qualified_names <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not requests to this domain require fully-qualified domain names.
+ </div><div class="para">
+ If set to <code class="literal">TRUE</code>, all requests to this domain must use fully-qualified domain names. It also means that the output from the request displays the fully-qualified name.
+ </div><div class="para">
+ The ability to restrict requests in this way means that if you know you have multiple domains with conflicting usernames, then there is no doubt about which username the query will resolve.
+ </div><div class="para">
+ Consider the following examples, in which the IPA domain database contains a user named <code class="systemitem">ipauser01</code>, and the <em class="parameter"><code>use_fully_qualified_names</code></em> attribute is set to <code class="literal">TRUE</code>:
+ </div><pre class="screen">
+<code class="command"># getent passwd ipauser01</code>
+[no output]
+<code class="command"># getent passwd ipauser01 at IPA</code>
+ipauser01 at IPA:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+</pre><div class="para">
+ In the following examples, using the same IPA domain and user, the <em class="parameter"><code>use_fully_qualified_names</code></em> attribute is set to <code class="literal">FALSE</code>:
+ </div><pre class="screen">
+<code class="command"># getent passwd ipauser01</code>
+ipauser01:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+<code class="command"># getent passwd ipauser01 at IPA</code>
+ipauser01:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+</pre><div class="note"><div class="admonition_header"><h2>Changing the use_fully_qualified_names value to FALSE</h2></div><div class="admonition"><div class="para">
+ If <em class="parameter"><code>use_fully_qualified_names</code></em> is set to <code class="literal">FALSE</code>, you can continue to use the fully-qualified name in your requests, but only the simplified version is displayed in the output.
+ </div><div class="para">
+ SSSD can only parse <code class="systemitem">name at domain</code>, not <code class="systemitem">name at realm</code>. You can, however, use the same name for both your domain and your realm.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">auth_provider <span class="type">(string)</span> </code>
+ </div><div class="para">
+ The authentication provider used for the domain. The default value for this option is the value of <code class="option">id_provider</code> if it is set and can handle authentication requests.
+ </div><div class="para">
+ Currently supported authentication providers are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ldap — for native LDAP authentication. Refer to the sssd-ldap(5) manual page for more information on configuring LDAP.
+ </div></li><li class="listitem"><div class="para">
+ krb5 — for Kerberos authentication. Refer to the sssd-krb5(5) manual page for more information on configuring Kerberos.
+ </div></li><li class="listitem"><div class="para">
+ proxy — for relaying authentication to some other PAM target.
+ </div></li><li class="listitem"><div class="para">
+ none — explicitly disables authentication.
+ </div></li></ul></div>
+
+ </div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Proxy_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.5.1.2. Proxy Configuration Options</h5></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">proxy_pam_target</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">auth_provider</code> option is set to <code class="literal">proxy</code>, and specifies the target to which <acronym class="acronym">PAM</acronym> must proxy.
+ </div><div class="para">
+ This option has no default value. If proxy authentication is required, you need to specify your own <acronym class="acronym">PAM</acronym> target. This corresponds to a file containing <acronym class="acronym">PAM</acronym> stack information in the system's default <acronym class="acronym">PAM</acronym> configuration directory. On Fedora-based systems, this is the <code class="filename">/etc/pam.d/</code> directory.
+ </div><div class="important"><div class="admonition_header"><h2>Avoid recursive inclusion of pam_sss</h2></div><div class="admonition"><div class="para">
+ Ensure that your proxy PAM stack does <span class="emphasis"><em>not</em></span> recursively include <code class="filename">pam_sss.so</code>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">proxy_lib_name</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">id_provider</code> option is set to <code class="literal">proxy</code>, and specifies which existing NSS library to proxy identity requests through.
+ </div><div class="para">
+ This option has no default value. You need to manually specify an existing library to take advantage of this option. For example, set this value to <code class="literal">nis</code> to use the existing <code class="filename">libnss_nis.so</code> file.
+ </div></li></ul></div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.5.2. Configuring an LDAP Domain</h4></div></div></div><a id="idm38274336" class="indexterm"></a><div class="para">
+ An LDAP domain is one where the <code class="option">id_provider</code> option is set to <code class="literal">ldap</code> (<code class="option">id_provider = ldap</code>). Such a domain requires a running LDAP server against which to authenticate. This can be an open source LDAP server such as OpenLDAP or Microsoft Active Directory. SSSD currently supports Microsoft Active Directory 2003 (+Services for UNIX) and Active Directory 2008 (+Subsystem for UNIX-based Applications). In all cases, the client configuration is stored in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-How_to_Authenticate_Against_an_LDAP_Server"><h5 class="formalpara">How to Authenticate Against an LDAP Server</h5>
+ SSSD does not support authentication over an unencrypted channel. Consequently, if you want to authenticate against an LDAP server, either <code class="systemitem">TLS/SSL</code> or <code class="systemitem">LDAPS</code> is required. If the LDAP server is used only as an identity provider, an encrypted channel is not needed.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file to include the following settings:
+ </div><pre class="screen"># A native LDAP domain
+[domain/LDAP]
+enumerate = false
+cache_credentials = TRUE
+
+id_provider = ldap
+auth_provider = ldap
+ldap_schema = rfc2307
+chpass_provider = ldap
+
+ldap_uri = ldap://ldap.mydomain.org
+ldap_search_base = dc=mydomain,dc=org
+ldap_tls_reqcert = demand
+ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+</pre><div class="note"><div class="admonition_header"><h2>Creating a certificate with an IP address instead of the server name</h2></div><div class="admonition"><div class="para">
+ If you wish to use an IP address in the <code class="option">ldap_uri</code> option instead of the server name, for example, if <code class="systemitem">GSSAPI</code> is used to avoid time consuming <code class="systemitem">DNS</code> lookups, the <code class="systemitem">TSL</code>/<code class="systemitem">SSL</code> setup might fail. This is due to the fact that <code class="systemitem">TSL</code>/<code class="systemitem">SSL</code> certificates contain the server name only. However, a special field in the certificate, called <span class="emphasis"><em>Subject Alternative Name</em></span> (<code class="option">subjectAltName</code>), can be used to additionally set the IP address of the server.
+ </div><div class="para">
+ The following steps show how to create a certificate with a Subject Alternative Name being the IP address of your server:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Using your command line, execute the following command to convert an existing certificate (previously signed by the <em class="parameter"><code>key.pem</code></em> key) into a certificate request:
+ </div><pre class="screen">openssl x509 -x509toreq -in old_cert.pem -out req.pem -signkey key.pem</pre><div class="para">
+ Alternatively, if you are using a self-signed certificate(for example, one created by the Fedora OpenLDAP package in <code class="filename">/etc/pki/tls/certs/slapd.pem</code>), execute the following command:
+ </div><pre class="screen">openssl x509 -x509toreq -in old_cert.pem -out req.pem -signkey old_cert.pem</pre></li><li class="step"><div class="para">
+ Edit your <code class="filename">/etc/pki/tls/openssl.cnf</code> configuration file to include the following line under the <em class="parameter"><code>[ v3_ca ]</code></em> section:
+ </div><pre class="screen">subjectAltName = IP:10.0.0.10</pre><div class="para">
+ Replace the IP address with one of your choice.
+ </div></li><li class="step"><div class="para">
+ By executing the following command, use the previously generated certificate request to generate a new self-signed certificate that will contain your desired IP address:
+ </div><pre class="screen">openssl x509 -req -in req.pem -out new_cert.pem -extfile ./openssl.cnf -extensions v3_ca -signkey old_cert.pem</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="command">openssl x509</code> command creates the new certificate.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-req</code> option tells the command to expect a certificate request as an input.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-in</code> and <code class="option">-out</code> options specify the input and output files.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-extfile</code> option expects a file containing certificate extensions to use (in our case the <code class="option">subjectAltName</code> extension).
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-extensions</code> option specifies the section of the <code class="filename">openssl.cnf</code> file to add certificate extensions from (in this case, the <em class="parameter"><code>[ v3_ca ]</code></em> section).
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">-signkey</code> option tells the command to self-sign the input file using the supplied private key.
+ </div></li></ul></div><div class="para">
+ For more information on the <span class="application"><strong>x509</strong></span> utility and its parameters, refer to <code class="command">man x509</code>.
+ </div></li><li class="step"><div class="para">
+ Lastly, copy the private key block from the <code class="filename">old_cert.pem</code> file into the <code class="filename">new_cert.pem</code> file to keep all relevant information in one file.
+ </div></li></ol></div><div class="para">
+ When creating a certificate through the <span class="application"><strong>certutil</strong></span> utility provided by the <span class="package">nss-utils</span> package, note that <span class="application"><strong>certutil</strong></span> supports <code class="systemitem">DNS</code> subject alternative names for certificate creation only.
+ </div><div class="para">
+ It is advisable to use a Certificate Authority to issue your certificate. Consider using the Red Hat Certificate System; for more information on managing subject names and subject alternative names in your certificate, refer to the <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Certificate_System/8.0/html/Admin_Guide/Managing_Subject_Names_and_Subject_Alternative_Names.html">Red Hat Certificate System Admin Guide</a>.
+ </div></div></div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-Selecting_an_LDAP_Schema"><h5 class="formalpara">Selecting an LDAP Schema</h5><a id="idm45375440" class="indexterm"></a>
+ You can set the <em class="parameter"><code>ldap_schema</code></em> attribute to either <code class="literal">rfc2307</code> or <code class="literal">rfc2307bis</code>. These schema define how groups in <acronym class="acronym">LDAP</acronym> are specified. In <em class="citetitle">RFC 2307</em>, group objects use a multi-valued attribute, <em class="parameter"><code>memberuid</code></em>, which lists the names of the users that belong to that group. In <em class="citetitle">RFC 2307bis</em>, instead of the <em class="parameter"><code>memberuid</code></em>, group objects use the <em class="parameter"><code>member</code></em> attribute. Rather than just the name of the user, this attribute contains the full Distinguished Name (DN) of another object in the LDAP database. This means that groups can have other groups as members. That is, it adds support for nested groups.
+ </div><div class="para">
+ SSSD assumes that your LDAP server is using <em class="citetitle">RFC 2307</em>. If your LDAP server is using <em class="citetitle">RFC 2307bis</em>, and you do not update the <code class="filename">/etc/sssd/sssd.conf</code> file accordingly, this can impact how your users and groups are displayed. It also means that some groups will not be available and network resources may be inaccessible even though you have permissions to use them.
+ </div><div class="para">
+ For example, when using <em class="citetitle">RFC 2307bis</em> and you have configured both primary and secondary groups, or are using nested groups, you can use the <code class="command">id</code> command to display these groups:
+ </div><pre class="screen">[f12server at ipaserver ~]$ id
+uid=500(f12server) gid=500(f12server) groups=500(f12server),510(f12tester)
+</pre><div class="para">
+ If instead you have configured your client to use <em class="citetitle">RFC 2307</em> then only the primary group is displayed.
+ </div><div class="para">
+ Changes to this setting only affect how SSSD determines the groups to which a user belongs; there is no negative effect on the actual user data. If you do not know the correct value for this attribute, consult your System Administrator.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-Specifying_Timeout_Values"><h5 class="formalpara">Specifying Timeout Values</h5><a id="idm38113568" class="indexterm"></a>
+ SSSD supports a number of timeout values that apply when configuring an <acronym class="acronym">LDAP</acronym> domain. These are described below.
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">ldap_search_timeout (integer)</code> — Specifies the timeout (in seconds) that <acronym class="acronym">LDAP</acronym> searches are allowed to run before they are canceled and cached results are returned (and offline mode is entered). If not specified:
+ </div><div class="para">
+ Defaults to five when <code class="option">enumerate</code> = <code class="literal">False</code>
+ </div><div class="para">
+ Defaults to 30 when <code class="option">enumerate</code> = <code class="literal">True</code>. This option is forced to a minimum of 30 in this case.
+ </div><div class="note"><div class="admonition_header"><h2>The ldap_network_timeout option is going to be changed</h2></div><div class="admonition"><div class="para">
+ This option is subject to change in future versions of SSSD, where it may be replaced by a series of timeouts for specific look-up types.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">ldap_network_timeout (integer)</code> — Specifies the timeout (in seconds) after which the <code class="function">poll(2)</code>/<code class="function">select(2)</code> following a <code class="function">connect(2)</code> returns in case of no activity.
+ </div><div class="para">
+ If not specified, defaults to five.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ldap_opt_timeout (integer)</code> — Specifies the timeout (in seconds) after which calls to synchronous <acronym class="acronym">LDAP</acronym> APIs will abort if no response is received. This option also controls the timeout when communicating with the KDC in case of a SASL bind.
+ </div><div class="para">
+ If not specified, defaults to five.
+ </div></li></ul></div>
+
+ </div><div class="note"><div class="admonition_header"><h2>DNS Service Discovery</h2></div><div class="admonition"><div class="para">
+ The <code class="systemitem">DNS</code> service discovery feature allows the LDAP back end to automatically find the appropriate <code class="systemitem">DNS</code> servers to connect to using a special <code class="systemitem">DNS</code> query. For more information on the <code class="systemitem">DNS</code> service discovery feature, refer to <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">「Using SRV Records with Failover」</a>.
+ </div></div></div><h5 id="idm22196256"></h5><div class="para">
+
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.5.3. Configuring a Microsoft Active Directory Domain</h4></div></div></div><a id="idm61158816" class="indexterm"></a><div class="para">
+ You can configure SSSD to use Microsoft Active Directory as an LDAP back end, providing both identity and authentication services. If you are using Active Directory 2003, SSSD requires that you install Windows Services for UNIX (SFU) on the machine where Active Directory is installed. If instead you are using Active Directory 2008, you need to install the Subsystem for UNIX-based Applications (SUA) on the Active Directory machine.
+ </div><div class="note"><div class="admonition_header"><h2>SFU is not supported on 64-bit systems</h2></div><div class="admonition"><div class="para">
+ SFU is not supported on 64-bit operating systems. Refer to <a href="http://support.microsoft.com/kb/920751">http://support.microsoft.com/kb/920751</a> for more information about which Windows systems can provide a suitable platform for an SSSD LDAP back end.
+ </div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2003"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.5.3.1. Configuring Active Directory 2003 as an LDAP Back End</h5></div></div></div><div class="para">
+ The example <code class="filename">/etc/sssd/sssd.conf</code> file that ships with SSSD contains the following sample configuration for Active Directory 2003:
+ </div><pre class="screen"># Example LDAP domain where the LDAP server is an Active Directory 2003 server.
+
+[domain/AD]
+description = LDAP domain with AD server
+enumerate = false
+min_id = 1000
+;
+id_provider = ldap
+auth_provider = ldap
+ldap_uri = ldap://your.ad.server.com
+ldap_schema = rfc2307bis
+ldap_search_base = dc=example,dc=com
+ldap_default_bind_dn = cn=Administrator,cn=Users,dc=example,dc=com
+ldap_default_authtok_type = password
+ldap_default_authtok = YOUR_PASSWORD
+ldap_user_object_class = person
+ldap_user_name = msSFU30Name
+ldap_user_uid_number = msSFU30UidNumber
+ldap_user_gid_number = msSFU30GidNumber
+ldap_user_home_directory = msSFU30HomeDirectory
+ldap_user_shell = msSFU30LoginShell
+ldap_user_principal = userPrincipalName
+ldap_group_object_class = group
+ldap_group_name = msSFU30Name
+ldap_group_gid_number = msSFU30GidNumber</pre><div class="para">
+ This configuration is specific to Windows Active Directory 2003. Refer to <a class="xref" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008">「Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends」</a> for information on how to configure Active Directory 2003 R2 and Active Directory 2008.
+ </div><div class="para">
+ Note that the above configuration assumes that the certificates are stored in the default location (that is, in <code class="filename">/etc/openldap/cacerts</code>) and that the <code class="function">c_rehash</code> function has been used to create the appropriate symlinks.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm22191168">More Information</h5>
+ Refer to the <em class="citetitle">sssd-ldap(5)</em> manual page for a full description of all the options that apply to <acronym class="acronym">LDAP</acronym> domains.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.5.3.2. Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends</h5></div></div></div><div class="para">
+ The configuration of <code class="filename">/etc/sssd/sssd.conf</code> to support Active Directory 2003 R2 or Active Directory 2008 as a back end is similar to that for AD 2003. The following example configuration highlights the necessary changes.
+ </div><pre class="screen"># Example LDAP domain where the LDAP server is an Active Directory 2003 R2 or an Active Directory 2008 server.
+
+[domain/AD]
+description = LDAP domain with AD server
+; debug_level = 9
+enumerate = false
+
+id_provider = ldap
+auth_provider = ldap
+chpass_provider = ldap
+
+ldap_uri = ldap://your.ad.server.com
+ldap_tls_cacertdir = /etc/openldap/cacerts
+ldap_tls_cacert = /etc/openldap/cacerts/test.cer
+ldap_search_base = dc=example,dc=com
+ldap_default_bind_dn = cn=Administrator,cn=Users,dc=example,dc=com
+ldap_default_authtok_type = password
+ldap_default_authtok = YOUR_PASSWORD
+ldap_pwd_policy = none
+ldap_user_object_class = user
+ldap_group_object_class = group</pre><div class="para">
+ Note that the above configuration assumes that the certificates are stored in the default location (that is, in <code class="filename">/etc/openldap/cacerts</code>) and that the <code class="function">c_rehash</code> function has been used to create the appropriate symlinks.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>戻る</strong>9.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="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>次へ</strong>9.2.6. Setting Up Kerberos Authentication</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Configuring_Services.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Configuring_Services.html
new file mode 100644
index 0000000..2463e22
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Configuring_Services.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>9.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html" title="9.2.3. Setting Up SSSD" /><link rel="next" href="chap-SSSD_User_Guide-Configuring_Domains.html" title="9.2.5. Configuring Domains" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-SSSD_
User_Guide-Setting_Up_SSSD.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Configuring_Domains.html"><strong>次へ</strong></a></li></ul><div class="section" id="chap-SSSD_User_Guide-Configuring_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.4. サービスの設定</h3></div></div></div><div class="para">
+ Individual pieces of SSSD functionality are provided by special SSSD services that are started and stopped together with SSSD. The services provided by SSSD have their own configuration sections. The <code class="literal">[sssd]</code> section also lists the services that are active and should be started when <code class="systemitem">sssd</code> starts within the <code class="command">services</code> directive.
+ </div><div class="para">
+ SSSD currently provides several services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">NSS</code> — An NSS provider service that answers NSS requests from the <code class="systemitem">sssd_nss</code> module.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">PAM</code> — A PAM provider service that manages a PAM conversation through the <code class="systemitem">sssd_pam</code> PAM module.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">monitor</code> — A special service that monitors all other SSSD services, and starts or restarts them as needed. Its options are specified in the <code class="literal">[sssd]</code> section of the <code class="filename">/etc/sssd/sssd.conf</code> configuration file.
+ </div></li></ul></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Services-Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.4.1. Configuration Options</h4></div></div></div><div class="para">
+ The following sections cover the most important SSSD configuration options. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page that ships with SSSD for information on all the available configuration options.
+ </div><div class="section" id="sect-SSSD_User_Guide-Configuration_Options-General_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.4.1.1. General Configuration Options</h5></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">debug_level <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Sets the debug level for a particular service. This is a per-service setting (that is, it can appear in any of the <code class="literal">[service/<NAME>]</code> sections in the SSSD configuration file).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">reconnection_retries <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ In the event of a data provider crash or restart, this specifies the number of times that a service should attempt to reconnect.
+ </div><div class="note"><div class="admonition_header"><h2>DNS lookup of IPv6 addresses</h2></div><div class="admonition"><div class="para">
+ If a <code class="systemitem">DNS</code> lookup fails to return an <code class="systemitem">IPv4</code> address for a hostname, SSSD attempts to look up an <code class="systemitem">IPv6</code> address before returning a failure. Note that this only ensures that the async resolver identifies the correct address; there is currently a bug in the LDAP code that prevents SSSD from connecting to an LDAP server over IPv6. This is being investigated separately.
+ </div></div></div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Configuration_Options-NSS_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.4.1.2. NSS Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the <code class="systemitem">Name Service Switch (NSS)</code> service. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for full details about each option.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">enum_cache_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long (in seconds) <span class="package">sssd_nss</span> should cache enumerations (requests for information about all users).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_cache_nowait_percentage <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long <span class="package">sssd_nss</span> should return cached entries before initiating an out-of-band cache refresh (<code class="literal">0</code> disables this feature).
+ </div><div class="para">
+ You can configure the entry cache to automatically update entries in the background if they are requested beyond a percentage of the <code class="option">entry_cache_timeout</code> value for the domain.
+ </div><div class="para">
+ Valid values for this option are <code class="literal">0-99</code>, and represent a percentage of the <code class="option">entry_cache_timeout</code> value for each domain.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_negative_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long (in seconds) <span class="package">sssd_nss</span> should cache negative cache hits (that is, queries for invalid database entries, such as nonexistent ones) before asking the back end again.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">filter_users, filter_groups <span class="type">(string)</span> </code>
+ </div><div class="para">
+ Exclude certain users from being fetched from the sss NSS database. This is particularly useful for system accounts such as <code class="systemitem">root</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">filter_users_in_groups <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ If set to <code class="literal">TRUE</code>, specifies that users listed in the <code class="option">filter_users</code> list do not appear in group memberships when performing group lookups. If set to <code class="literal">FALSE</code>, group lookups return all users that are members of that group. If not specified, defaults to <code class="literal">TRUE</code>.
+ </div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Configuration_Options-PAM_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.4.1.3. PAM Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the <code class="systemitem">Pluggable Authentication Module (<acronym class="acronym">PAM</acronym>)</code> service.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">offline_credentials_expiration <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ If the authentication provider is offline, specifies for how long to allow cached log-ins (in days). This value is measured from the last successful online log-in. If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">offline_failed_login_attempts <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ If the authentication provider is offline, specifies how many failed log in attempts are allowed. If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">offline_failed_login_delay <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the time in minutes after the value of <code class="option">offline_failed_login_attempts</code> has been reached before a new log in attempt is possible.
+ </div><div class="para">
+ If set to <code class="literal">0</code>, the user cannot authenticate offline if the value of <code class="option">offline_failed_login_attempts</code> has been reached. Only a successful online authentication can re-enable offline authentication. If not specified, defaults to <code class="literal">5</code>.
+ </div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html"><strong>戻る</strong>9.2.3. Setting Up SSSD</a></li><li class="up"><a accesskey="u" href="#"><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-SSSD_User_Guide-Configuring_Domains.html"><strong>次へ</strong>9.2.5. Configuring Domains</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Introduction.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Introduction.html
new file mode 100644
index 0000000..7a6b16e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Introduction.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.2. The System Security Services Daemon (SSSD)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Configuring_Authentication.html" title="第9章 認証の設定" /><link rel="prev" href="ch-Configuring_Authentication.html" title="第9章 認証の設定" /><link rel="next" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html" title="9.2.2. SSIDの特徴" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_Authentication.html"><strong
>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="section" id="chap-SSSD_User_Guide-Introduction" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.2. The System Security Services Daemon (SSSD)</h2></div></div></div><div class="para">
+ This section provides an introduction to the <em class="firstterm">System Security Services Daemon (SSSD)</em>, the main features that it provides, and discusses the requirements and any limitations of a typical SSSD deployment.
+ </div><div class="para">
+ This section also describes how to configure SSSD, and how to use the features that it provides. It provides information on the types of services that it supports and how to configure them, and introduces and describes the most important configuration options. Sample configuration files are also provided to help you optimize your deployment.
+ </div><div class="section" id="sect-SSSD_User_Guide-Introduction-What_is_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.1. SSIDとは?</h3></div></div></div><div class="para">
+ The System Security Services Daemon (SSSD) is a service which provides access to different identity and authentication providers. You can configure SSSD to use a native LDAP domain (that is, an LDAP identity provider with LDAP authentication), or an LDAP identity provider with Kerberos authentication. It provides an NSS and PAM interface to the system, and a pluggable back-end system to connect to multiple different account sources.
+ </div><div class="para">
+ SSSD is also extensible; you can configure it to use new identity sources and authentication mechanisms should they arise. In addition, SSSD is fully IPv6-compatible, provided that it is built against <span class="package">c-ares 1.7.1</span> or later and <span class="package">krb5-libs 1.8.1</span> or later.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configuring_Authentication.html"><strong>戻る</strong>第9章 認証の設定</a></li><li class="up"><a accesskey="u" href="#"><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-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>次へ</strong>9.2.2. SSIDの特徴</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
new file mode 100644
index 0000000..9b8ebe4
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
@@ -0,0 +1,185 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Setting Up SSSD</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html" title="9.2.2. SSIDの特徴" /><link rel="next" href="chap-SSSD_User_Guide-Configuring_Services.html" title="9.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
="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>次へ</strong></a></li></ul><div class="section" id="chap-SSSD_User_Guide-Setting_Up_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.3. Setting Up SSSD</h3></div></div></div><div class="para">
+ This section describes how to install SSSD, how to run the service, and how to configure it for each type of supported information provider.
+ </div><div class="section" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Installing_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.3.1. SSSDのインストール</h4></div></div></div><div class="para">
+ Run the following command to install SSSD and any dependencies, including the SSSD client:
+ </div><div class="para">
+ <code class="command"># yum install sssd</code>
+ </div><div class="para">
+ SSSD requires very few dependencies and should install very quickly, depending on the speed of your network connection.
+ </div><div class="section" id="sect-SSSD_User_Guide-Installing_SSSD-Upgrading_from_a_Previous_Version"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.1.1. Upgrading from a Previous Version</h5></div></div></div><div class="formalpara" id="form-SSSD_User_Guide-Upgrading_from_a_Previous_Version-Upgrading_Using_RPM_Packages"><h5 class="formalpara">Upgrading Using RPM Packages</h5>
+ If you are upgrading using RPM packages, the script will run automatically when you upgrade to the new version. This will upgrade the <code class="filename">/etc/sssd/sssd.conf</code> file to the new format, and copy the existing version to <code class="filename">/etc/sssd/sssd.conf.bak</code>.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Upgrading_from_a_Previous_Version-Upgrading_Manually"><h5 class="formalpara">Upgrading Manually</h5>
+ It may be necessary to run the upgrade script manually, either because you built SSSD from source files, or because you are using a platform that does not support the use of RPM packages. The synopsis for the script is as follows:
+ </div><div class="cmdsynopsis"><p id="idm34988608"><code class="command">upgrade_config.py</code> [
+ -f INFILE
+ ] [
+ -o OUTFILE
+ ] [
+ -verbose
+ ] [
+ --no-backup
+ ]</p></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>-f INFILE</code></em> — the configuration file to upgrade. If not specified, this defaults to <code class="filename">/etc/sssd/sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>-o OUTFILE</code></em> — the name of the upgraded configuration file. If not specified, this defaults to <code class="filename">/etc/sssd/sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>-verbose</code></em> — produce more verbose output during the upgrade process
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>--no-backup</code></em> — do not produce a back-up file. If not specified, this defaults to <code class="filename"><em class="parameter"><code>INFILE</code></em>.bak</code>
+ </div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Installing_SSSD-Starting_and_Stopping_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.1.2. Starting and Stopping SSSD</h5></div></div></div><div class="note"><div class="admonition_header"><h2>Starting SSSD for the first time</h2></div><div class="admonition"><div class="para">
+ Before you start SSSD for the first time, you need to configure at least one domain. Refer to <a class="xref" href="chap-SSSD_User_Guide-Configuring_Domains.html">「Configuring Domains」</a> for information on how to configure an SSSD domain.
+ </div></div></div><div class="para">
+ You can use either the <code class="command">service</code> command or the <code class="filename">/etc/init.d/sssd</code> script to control SSSD. For example, run the following command to start <code class="systemitem">sssd</code>:
+ </div><div class="para">
+ <code class="command"># systemctl start sssd.service</code>
+ </div><div class="para">
+ By default, SSSD is configured not to start automatically. There are two ways to change this behavior; if you use the Authentication Configuration tool to configure SSSD, it will reconfigure the default behavior so that SSSD starts when the machine boots. Alternatively, you can use the <code class="command">systemctl</code> command, as follows:
+ </div><div class="para">
+ <code class="command"># systemctl enable sssd.service</code>
+ </div></div></div><div class="section" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Configuring_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.3.2. Configuring SSSD</h4></div></div></div><div class="para">
+ The global configuration of SSSD is stored in the <code class="filename">/etc/sssd/sssd.conf</code> file. This file consists of various sections, each of which contains a number of key/value pairs. Some keys accept multiple values; use commas to separate multiple values for such keys. This configuration file uses data types of <span class="type">string</span> (no quotes required), <span class="type">integer</span> and <span class="type">Boolean</span> (with values of <code class="literal">TRUE</code> or <code class="literal">FALSE</code>). Comments are indicated by either a hash sign (#) or a semicolon (;) in the first column. The following example illustrates some of this syntax:
+ </div><pre class="programlisting">[section]
+# Keys with single values
+key1 = value
+key2 = val2
+
+# Keys with multiple values
+key10 = val10,val11
+</pre><div class="note"><div class="admonition_header"><h2>Specifying a different configuration file</h2></div><div class="admonition"><div class="para">
+ You can use the <em class="parameter"><code>-c</code></em> (or <em class="parameter"><code>--config</code></em>) parameter on the command line to specify a different configuration file for SSSD.
+ </div></div></div><div class="para">
+ The format of the configuration file is described in <a class="xref" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">「SSSD Configuration File Format」</a>
+ </div><div class="para">
+ Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more information on global SSSD configuration options.
+ </div><div class="section" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.2.1. Configuring NSS</h5></div></div></div><div class="para">
+ SSSD provides a new NSS module, <code class="systemitem">sssd_nss</code>, so that you can configure your system to use SSSD to retrieve user information. Edit the <code class="filename">/etc/nsswitch.conf</code> file for your system to use the <code class="systemitem">sss</code> name database. For example:
+ </div><pre class="programlisting">passwd: files sss
+group: files sss
+</pre></div><div class="section" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.2.2. Configuring PAM</h5></div></div></div><div class="warning"><div class="admonition_header"><h2>Be careful when changing your PAM configuration</h2></div><div class="admonition"><div class="para">
+ Use extreme care when changing your PAM configuration. A mistake in the PAM configuration file can lock you out of the system completely. Always back up your configuration files before performing any changes, and keep a session open so that you can revert any changes you make should the need arise.
+ </div></div></div><div class="para">
+ To enable your system to use SSSD for PAM, you need to edit the default PAM configuration file. On Fedora—based systems, this is the <code class="filename">/etc/pam.d/system-auth</code> file. Edit this file to reflect the following example, and then restart <code class="systemitem">sssd</code>:
+ </div><pre class="programlisting">#%PAM-1.0
+# This file is auto-generated.
+# User changes will be destroyed the next time authconfig is run.
+auth required pam_env.so
+auth sufficient pam_unix.so nullok try_first_pass
+auth requisite pam_succeed_if.so uid >= 500 quiet
+auth sufficient pam_sss.so use_first_pass
+auth required pam_deny.so
+
+account required pam_unix.so broken_shadow
+account sufficient pam_localuser.so
+account sufficient pam_succeed_if.so uid < 500 quiet
+account [default=bad success=ok user_unknown=ignore] pam_sss.so
+account required pam_permit.so
+
+password requisite pam_cracklib.so try_first_pass retry=3
+password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok
+password sufficient pam_sss.so use_authtok
+password required pam_deny.so
+
+session required pam_mkhomedir.so umask=0022 skel=/etc/skel/
+session optional pam_keyinit.so revoke
+session required pam_limits.so
+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
+session sufficient pam_sss.so
+session required pam_unix.so
+</pre><div class="section" id="idm69894992"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="idm69894992">9.2.3.2.2.1. Using Custom Home Directories with SSSD</h6></div></div></div><div class="para">
+ If your LDAP users have home directories that are not in <code class="filename">/home</code>, and if your system is configured to create home directories the first time your users log in, then these directories will be created with the wrong permissions. For example, instead of a typical home directory such as <code class="filename">/home/<username></code>, your users might have home directories that include their locale, such as <code class="filename">/home/<locale>/<username></code>. If this is true for your system, the following steps need to be taken (preemptively):
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Apply the correct SELinux context and permissions from the <code class="filename">/home</code> directory to the home directory that you use on your system. In the example above, the following command would achieve this result (replace the directory names with those that apply to your system):
+<pre class="screen"># semanage fcontext -a -e /home /home/locale</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ Ensure the <span class="package">oddjob-mkhomedir</span> package is installed on your system and then re-run the Authentication Configuration tool.
+ </div><div class="para">
+ This package provides the <code class="systemitem">pam_oddjob_mkhomedir.so</code> library, which the Authentication Configuration tool will then use to create your custom home directories. You need to use this library to create your home directories, and not the default <code class="systemitem">pam_mkhomedir.so</code> library, because the latter cannot create SELinux labels.
+ </div><div class="note"><div class="admonition_header"><h2>The pam_oddjob_mkhomedir and pam_mkhomedir libraries</h2></div><div class="admonition"><div class="para">
+ The Authentication Configuration tool will automatically use the <code class="systemitem">pam_oddjob_mkhomedir.so</code> library if it is available. Otherwise, it will default to using <code class="systemitem">pam_mkhomedir.so</code>.
+ </div></div></div></li></ol></div><div class="para">
+ If the preceding steps were not performed before the custom home directories were created, you can use the following commands to correct the permissions and SELinux contexts (again, replace the directory names with those that apply to your system):
+<pre class="screen"># semanage fcontext -a -e /home /home/locale
+# restorecon -R -v /home/locale</pre>
+
+ </div></div><div class="section" id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title">9.2.3.2.2.2. Using "include" Statements in PAM Configurations</h6></div></div></div><div class="para">
+ Recent PAM implementations allow you to use <code class="literal">include</code> statements in PAM configurations. For example:
+ </div><pre class="programlisting">...
+session include system-auth
+session optional pam_console.so
+...
+</pre><div class="para">
+ In the preceding example, if a <em class="parameter"><code>sufficient</code></em> condition from <code class="filename">system-auth</code> returns <span class="returnvalue">PAM_SUCCESS</span>, <code class="filename">pam_console.so</code> will not be executed.
+ </div></div></div><div class="section" id="idm68223072"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm68223072">9.2.3.2.3. Configuring Access Control</h5></div></div></div><a id="idm17898144" class="indexterm"></a><div class="para">
+ SSSD provides a rudimentary access control mechanism, offering two solutions based on the value of the <code class="option">access_provider</code> option in the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> section in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="section" id="idm51977120"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="idm51977120">9.2.3.2.3.1. The Simple Access Provider</h6></div></div></div><div class="para">
+ The first of these solutions is known as the <em class="firstterm">Simple Access Provider</em>, and is based on the implementation of access or deny lists of usernames. To enable the Simple Access Provider, you need to set the <code class="option">access_provider</code> option to <code class="literal">simple</code>, and then add usernames as a comma-separated list to either the <code class="option">simple_allow_users</code> or <code class="option">simple_deny_users</code> options.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm55727184">Using the Simple Access Provider</h5>
+ By using the Simple Access Provider, you can continue to support a number of network logins to maintain common network accounts on company or department laptops, but you might want to restrict the use of a particular laptop to one or two users. This means that even if a different user authenticated successfully against the same authentication provider, the Simple Access Provider would prevent that user from gaining access.
+ </div><div class="para">
+ The following example demonstrates the use of the Simple Access Provider to grant access to two users. This example assumes that SSSD is correctly configured and <code class="systemitem">example.com</code> is one of the domains specified in the <code class="literal">[sssd]</code> section, and only shows the Simple Access Provider-specific options.
+ </div><pre class="screen">[domain/example.com]
+access_provider = simple
+simple_allow_users = user1, user2</pre><div class="note"><div class="admonition_header"><h2>Using the Local ID provider</h2></div><div class="admonition"><div class="para">
+ The Local ID provider does not support <code class="option">simple</code> as an access provider.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm69895504">Access Control Rules</h5><a id="idm50441520" class="indexterm"></a>
+ The Simple Access Provider adheres to the following three rules to determine which users should or should not be granted access:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If both lists are empty, access is granted.
+ </div></li><li class="listitem"><div class="para">
+ If <code class="option">simple_allow_users</code> is set, only users from this list are allowed access. This setting supersedes the <code class="option">simple_deny_users</code> list (which would be redundant).
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="option">simple_allow_users</code> list is empty, users are allowed access unless they appear in the <code class="option">simple_deny_users</code> list.
+ </div></li></ul></div>
+ <div class="important"><div class="admonition_header"><h2>Do not define both simple_allow_users and simple_deny_users</h2></div><div class="admonition"><div class="para">
+ Defining both <code class="option">simple_allow_users</code> and <code class="option">simple_deny_users</code> is a configuration error. If this occurs, SSSD will output an error to the <code class="filename">/var/log/sssd/sssd_default.log</code> log file when loading the back end, but continue to start normally. Future versions of SSSD will output an error and fail to start.
+ </div></div></div>
+
+ </div></div><div class="section" id="idm66584880"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="idm66584880">9.2.3.2.3.2. The LDAP Access Provider</h6></div></div></div><div class="para">
+ The second access control solution uses the LDAP server itself as the access provider (<code class="option">access_provider=ldap</code>) and the associated filter option (<code class="option">ldap_access_filter</code>) to specify which users are granted access to the specified host. Note that these two options are codependent; if you use LDAP as your access provider then you must specify a value for the <code class="option">ldap_access_filter</code> option, otherwise all users will be denied access. If you are not using LDAP as your access provider, then the <code class="option">ldap_access_filter</code> option has no effect.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm56730432">Using the LDAP Access Provider</h5>
+ The following example demonstrates the use of the LDAP Access Provider to grant access to members of the "allowedusers" group in LDAP. This example assumes that SSSD is correctly configured and <code class="systemitem">example.com</code> is one of the domains specified in the <code class="literal">[sssd]</code> section, and only shows the LDAP Access Provider-specific options.
+ </div><pre class="screen">[domain/example.com]
+access_provider = ldap
+ldap_access_filter = memberOf=cn=allowedusers,ou=Groups,dc=example,dc=com</pre><div class="note"><div class="admonition_header"><h2>Using offline caching</h2></div><div class="admonition"><div class="para">
+ Offline caching for this feature is limited to determining whether or not the user's last online login attempt was successful. If they were granted access during their last login, they will continue to be granted access while offline, and vice-versa.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">sssd-ldap</em> manual page for more information about using the LDAP Access Provider.
+ </div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.3.2.4. Configuring Failover</h5></div></div></div><div class="para">
+ The failover feature allows back ends to automatically switch to a different server if the primary server fails. These servers are entered as a case-insensitive, comma-separated list in the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> sections of the <code class="filename">/etc/sssd/sssd.conf</code> file, and listed in order of preference. This list can contain any number of servers.
+ </div><div class="para">
+ For example, if you have configured a native LDAP domain, you could specify the following as your <em class="parameter"><code>ldap_uri</code></em> values:
+ </div><pre class="screen">ldap_uri = ldap://ldap0.mydomain.org, ldap://ldap1.mydomain.org, ldap://ldap2.mydomain.org</pre><div class="para">
+ In this configuration, <code class="uri">ldap://ldap0.mydomain.org</code> functions as the primary server. If this server fails, the SSSD failover mechanism first attempts to connect to <code class="uri">ldap1.mydomain.org</code>, and if that server is unavailable, it then attempts to connect to <code class="uri">ldap2.mydomain.org</code>.
+ </div><div class="para">
+ If the parameter that specifies which server to connect to for the specific domain (for example, <em class="parameter"><code>ldap_uri</code></em>, <em class="parameter"><code>krb5_server</code></em>, …) is not specified, the back end defaults to using <em class="replaceable"><code>Use service discovery</code></em>. Refer to <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">「Using SRV Records with Failover」</a> for more information on service discovery.
+ </div><div class="important"><div class="admonition_header"><h2>Do not use multiple ldap_uri parameters</h2></div><div class="admonition"><div class="para">
+ Do not use multiple <em class="parameter"><code>ldap_uri</code></em> parameters to specify your failover servers. The failover servers must be entered as a comma-separated list of values for a single <em class="parameter"><code>ldap_uri</code></em> parameter. If you enter multiple <em class="parameter"><code>ldap_uri</code></em> parameters, SSSD only recognizes the last entry.
+ </div><div class="para">
+ Future versions of SSSD will throw an error upon receiving additional <em class="parameter"><code>ldap_uri</code></em> entries.
+ </div></div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title">9.2.3.2.4.1. Using SRV Records with Failover</h6></div></div></div><div class="para">
+ SSSD also supports the use of SRV records in its failover configuration. This means that you can specify a server that is later resolved into a list of specific servers using SRV requests. The <em class="parameter"><code>priority</code></em> and <em class="parameter"><code>weight</code></em> attributes of SRV records provide further opportunity for specifying which servers should be contacted first in the event that the primary server fails.
+ </div><div class="para">
+ For every service with which you want to use service discovery, you need to add a special DNS record to your DNS server using the following form:
+ </div><pre class="screen">_<em class="replaceable"><code>service</code></em>._<em class="replaceable"><code>protocol</code></em>._<em class="replaceable"><code>domain TTL priority weight port hostname</code></em>
+</pre><div class="para">
+ A typical configuration would contain multiple such records, each with a different priority (for failover) and different weights (for load balancing).
+ </div><div class="para">
+ The client then makes an SRV DNS query to retrieve a list of host names, their priorities, and weights. These queries are of the form _<em class="replaceable"><code>service</code></em>._<em class="replaceable"><code>protocol</code></em>._<em class="replaceable"><code>domain</code></em>, for example, <code class="literal">_ldap._tcp._redhat.com</code>. The client then sorts this list according to the priorities and weights, and connects to the first server in this sorted list.
+ </div><div class="para">
+ For more information on SRV records, refer to <a href="http://tools.ietf.org/html/rfc2782">RFC 2782</a>.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-How_the_Failover_Mechanism_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title">9.2.3.2.4.2. How the Failover Mechanism Works</h6></div></div></div><div class="para">
+ The failover mechanism distinguishes between machines and services. The back end first tries to resolve the hostname of a given machine; if this resolution attempt fails, the machine is considered offline. No further attempts are made to connect to this machine for any other service. If the resolution attempt succeeds, the back end tries to connect to a service on this machine. If the service connection attempt fails, then only this particular service is considered offline and the back end automatically switches over to the next service. The machine is still considered online and might still be tried for another service.
+ </div><div class="para">
+ The failover mechanism does not handle DNS A records with multiple IP addresses; instead it only uses the first address. DNS round-robin cannot be used for failover. Further, providing multiple A records does not provide failover. Only the first A record is used, and if a lookup attempt on the first record fails then the system attempts no further lookups. To find multiple servers with a single request, and thus implementing failover, SSSD relies on SRV resource records, as explained in <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">「Using SRV Records with Failover」</a>.
+ </div><div class="para">
+ Further connection attempts are made to machines or services marked as offline after a specified period of time; this is currently hard coded to 30 seconds. If there are no more machines to try, the back end as a whole switches to offline mode, and then attempts to reconnect every 30 seconds.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>戻る</strong>9.2.2. SSIDの特徴</a></li><li class="up"><a accesskey="u" href="#"><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-SSSD_User_Guide-Configuring_Services.html"><strong>次へ</strong>9.2.4. サービスの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Troubleshooting.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Troubleshooting.html
new file mode 100644
index 0000000..d6bd9eb
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/chap-SSSD_User_Guide-Troubleshooting.html
@@ -0,0 +1,121 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html" title="9.2.7. Configuring a Proxy Domain" /><link rel="next" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html" title="9.2.9. SSSD Configuration File 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" al
t="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>次へ</strong></a></li></ul><div class="section" id="chap-SSSD_User_Guide-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.8. トラブルシューティング</h3></div></div></div><div class="para">
+ This section lists some of the issues you may encounter when implementing SSSD, the possible causes of these issues, and how to resolve them. If you find further issues that are not covered here, refer to the <em class="citetitle">We Need Feedback</em> section in the <em class="citetitle">Preface</em> for information on how to file a bug report.
+ </div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Using_SSSD_Log_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.1. Using SSSD Log Files</h4></div></div></div><div class="para">
+ SSSD uses a number of log files to report information about its operation, and this information can help to resolve issues in the event of SSSD failure or unexpected behavior. The default location for these log files on Fedora—based systems is the <code class="filename">/var/log/sssd/</code> directory.
+ </div><div class="para">
+ SSSD produces a log file for each back end (that is, one log file for each domain specified in the <code class="filename">/etc/sssd/sssd.conf</code> file), as well as an <code class="filename">sssd_pam.log</code> and an <code class="filename">sssd_nss.log</code> file. This level of granularity can help you to quickly isolate and resolve any errors or issues you might experience with SSSD.
+ </div><div class="para">
+ You should also examine the <code class="filename">/var/log/secure</code> file, which logs authentication failures and the reason for the failure. For example, if you see <span class="errortext">Reason 4: System Error</span> reported against any failure, you should increase the debug level of the log files.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Using_SSSD_Log_Files-Producing_More_Verbose_Log_Files"><h5 class="formalpara">Producing More Verbose Log Files</h5>
+ If you are unable to identify and resolve any problems with SSSD after inspection of the default log files, you can configure SSSD to produce more verbose files. You can set the <code class="option">debug_level</code> option in the <code class="filename">/etc/sssd/sssd.conf</code> for the domain that is causing concern, and then restart SSSD. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more information on how to set the <code class="option">debug_level</code> for a specific domain.
+ </div><div class="para">
+ All log files include timestamps on debug messages by default. This can make it easier to understand any errors that may occur, why they occurred, and how to address them. If necessary, you can disable these timestamps by setting the appropriate parameter to <code class="literal">FALSE</code> in the <code class="filename">/etc/sssd/sssd.conf</code> file:
+ </div><pre class="screen">--debug-timestamps=FALSE
+</pre></div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.2. Problems with SSSD Configuration</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ SSSD fails to start
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ SSSD requires at least one properly configured domain before the service will start. Without such a domain, you might see the following error message when trying to start SSSD with the following command:
+ </div><div class="para">
+ <code class="command"># sssd -d4</code>
+ </div><pre class="screen">[sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
+
+[sssd] [confdb_get_domains] (0): No domains configured, fatal error!
+[sssd] [get_monitor_config] (0): No domains configured.
+</pre><div class="para">
+ You can ignore the <span class="errortext">"Unable to register control with rootdse!"</span> message, as it is erroneous. The other messages, however, indicate that SSSD is unable to locate any properly configured domains.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file and ensure you have at least one properly configured domain, and then try to start SSSD.
+ </div></li><li class="listitem"><div class="para">
+ SSSD requires at least one available service provider before it will start. With no available service providers, you might see the following error message when trying to start SSSD with the following command:
+ </div><div class="para">
+ <code class="command"># sssd -d4</code>
+ </div><pre class="screen">[sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
+
+[sssd] [get_monitor_config] (0): No services configured!
+</pre><div class="para">
+ You can ignore the <span class="errortext">"Unable to register control with rootdse!"</span> message, as it is erroneous. The other message, however, indicates that SSSD is unable to locate any available service providers.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file and ensure you have at least one available service providers, and then try to start SSSD.
+ </div><div class="important"><div class="admonition_header"><h2>Configuring the service providers</h2></div><div class="admonition"><div class="para">
+ SSSD requires that service providers be configured as a comma-separated list in a single <em class="parameter"><code>services</code></em> entry in the <code class="filename">/etc/sssd/sssd.conf</code> file. If services are listed in multiple entries, only the last entry is recognized by SSSD.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more options that might assist in troubleshooting issues with SSSD.
+ </div></li></ul></div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Service_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.3. Problems with SSSD Service Configuration</h4></div></div></div><div class="section" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_NSS"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.8.3.1. Problems with NSS</h5></div></div></div><div class="para">
+ This section describes some common problems with <code class="systemitem">NSS</code>, their symptoms, and how to resolve them.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">NSS</code> fails to return user information
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Ensure that NSS is running
+ </div><div class="para">
+ <code class="command"># systemctl is-active sssd.service</code>
+ </div><div class="para">
+ This command should return results similar to the following:
+ </div><pre class="screen">sssd (pid 21762) is running...
+</pre></li><li class="listitem"><div class="para">
+ Ensure that you have correctly configured the <code class="literal">[nss]</code> section of the <code class="filename">/etc/sssd/sssd.conf</code> file. For example, ensure that you have not misconfigured the <em class="parameter"><code>filter_users</code></em> or <em class="parameter"><code>filter_groups</code></em> attributes. Refer to the <em class="citetitle">NSS configuration options</em> section of the <em class="citetitle">sssd.conf(5)</em> manual page for information on how to configure these attributes.
+ </div></li><li class="listitem"><div class="para">
+ Ensure that you have included <code class="systemitem">nss</code> in the list of services that <code class="systemitem">sssd</code> should start
+ </div></li><li class="listitem"><div class="para">
+ Ensure that you have correctly configured the <code class="filename">/etc/nsswitch.conf</code> file. Refer to the section <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS">「Configuring NSS」</a> for information on how to correctly configure this file.
+ </div></li></ul></div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.8.3.2. Problems with PAM</h5></div></div></div><div class="para">
+ This section describes some common problems with <code class="systemitem">PAM</code>, their symptoms, and how to resolve them.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Setting the password for the local SSSD user prompts twice for the password
+ </div><div class="para">
+ When attempting to change a local SSSD user's password, you might see output similar to the following:
+ </div><pre class="screen">[root at clientF11 tmp]# passwd user1000
+Changing password for user user1000.
+New password:
+Retype new password:
+New Password:
+Reenter new Password:
+passwd: all authentication tokens updated successfully.
+</pre><div class="para">
+ This is the result of an incorrect PAM configuration. Refer to <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM">「Configuring PAM」</a>, and ensure that the <em class="parameter"><code>use_authtok</code></em> option is correctly configured in your <code class="filename">/etc/pam.d/system-auth</code> file.
+ </div></li></ul></div></div><div class="section" id="idm60313264"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm60313264">9.2.8.3.3. Problems with NFS and NSCD</h5></div></div></div><div class="para">
+ SSSD is not designed to be used with the <code class="systemitem">nscd</code> daemon, and will likely generate warnings in the SSSD log files. Even though SSSD does not directly conflict with <code class="systemitem">nscd</code>, the use of both at the same time can result in unexpected behavior (specifically with how long entries are being cached).
+ </div><div class="para">
+ If you are using Network Manager to manage your network connections, it may take several minutes for the network interface to come up. During this time, various services will attempt to start. If these services start before the network is up (that is, the DNS servers cannot yet be reached) they will fail to identify the forward or reverse DNS entries they might need. These services will be reading an incorrect or possibly empty <code class="filename">resolv.conf</code> file. This file is typically only read once, and so any changes made to this file are not automatically applied.
+ </div><div class="para">
+ This can result in the failure of some system services, and in particular can cause NFS locking to fail on the machine where the <code class="systemitem">nscd</code> service is running, unless that service is manually restarted.
+ </div><div class="para">
+ One method of working around this problem is to enable caching for <em class="parameter"><code>hosts</code></em> and <em class="parameter"><code>services</code></em> in the <code class="filename">/etc/nscd.conf</code> file, and to rely on the SSSD cache for the <em class="parameter"><code>passwd</code></em> and <em class="parameter"><code>group</code></em> entries. With <code class="systemitem">nscd</code> answering <em class="parameter"><code>hosts</code></em> and <em class="parameter"><code>services</code></em> requests, these entries would have been cached and returned by <code class="systemitem">nscd</code> during the boot process.
+ </div><div class="note"><div class="admonition_header"><h2>NSCD and later versions of SSSD</h2></div><div class="admonition"><div class="para">
+ Later versions of SSSD should negate any need for NSCD.
+ </div></div></div></div></div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Domain_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.4. Problems with SSSD Domain Configuration</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ NSS returns incorrect user information
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If your search for user information returns incorrect data, ensure that you do not have conflicting usernames in separate domains. If you use multiple domains, it is recommended that you set the <em class="parameter"><code>use_fully_qualified_domains</code></em> attribute to <code class="literal">TRUE</code> in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div></li></ul></div>
+
+ </div></li></ul></div></div><div class="section" id="sect-SSSD_User_Guide-Troubleshooting-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.8.5. その他のリソース</h4></div></div></div><div class="section" id="sect-SSSD_User_Guide-Additional_Resources-Manual_Pages"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.8.5.1. Manual Pages</h5></div></div></div><div class="para">
+ SSSD ships with a number of manual pages, all of which provide additional information about specific aspects of SSSD, such as configuration files, commands, and available options. SSSD currently provides the following manual pages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">sssd.conf(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-ipa(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-krb5(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-ldap(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd(8)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd_krb5_locator_plugin(8)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">pam_sss(8)</code>
+ </div></li></ul></div><div class="para">
+ You should refer to these manual pages for detailed information about all aspects of SSSD, its configuration, and associated tools and commands.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-Additional_Resources-Mailing_Lists"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">9.2.8.5.2. Mailing Lists</h5></div></div></div><div class="para">
+ You can subscribe to the SSSD mailing list to follow and become involved in the development of SSSD, or to ask questions about any issues you may be experiencing with your SSSD deployment.
+ </div><div class="para">
+ Visit <a href="https://fedorahosted.org/mailman/listinfo/sssd-devel">https://fedorahosted.org/mailman/listinfo/sssd-devel</a> to subscribe to this mailing list.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html"><strong>戻る</strong>9.2.7. Configuring a Proxy Domain</a></li><li class="up"><a accesskey="u" href="#"><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-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>次へ</strong>9.2.9. SSSD Configuration File Format</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/dhcp-relay-agent.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/dhcp-relay-agent.html
new file mode 100644
index 0000000..5712ff0
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/dhcp-relay-agent.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>11.2.4. DHCP リレーエージェント</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-dhcp-configuring-server.html" title="11.2. DHCP サーバーの設定" /><link rel="prev" href="ch11s02s03.html" title="11.2.3. サーバーの起動と停止" /><link rel="next" href="s1-dhcp-configuring-client.html" title="11.3. DHCP クライアントの設定" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02s03.html"><strong>戻る</strong></a>
</li><li class="next"><a accesskey="n" href="s1-dhcp-configuring-client.html"><strong>次へ</strong></a></li></ul><div class="section" id="dhcp-relay-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.2.4. DHCP リレーエージェント</h3></div></div></div><a id="idm36718752" class="indexterm"></a><a id="idm36717152" class="indexterm"></a><a id="idm31094464" class="indexterm"></a><div class="para">
+ DHCP リレーエージェント (<code class="command">dhcrelay</code>) は、DHCP と BOOTP 要求を DHCP サーバーを持つサブネットから他のサブネットにある1つ以上の DHCP サーバーまでリレーできます。
+ </div><div class="para">
+ DHCP クライアントが情報を要求すると、 DHCP リレーエージェントは自身の起動時に指定された一覧に含まれる DHCP サーバーに要求を転送します。 DHCP サーバーのいずれかから応答が返されると、その応答はオリジナルの要求を送信したネットワークにブロードキャストされたりユニキャストされたりします。
+ </div><div class="para">
+ The DHCP Relay Agent listens for DHCP requests on all interfaces unless the interfaces are specified in <code class="filename">/etc/sysconfig/dhcrelay</code> with the <code class="computeroutput">INTERFACES</code> directive.
+ </div><div class="para">
+ DHCP リレーエージェントを開始するには、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl start dhcrelay.service</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02s03.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="s1-dhcp-configuring-client.html"><strong>次へ</strong>11.3. DHCP クライアントの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Editing-VPN-connection-1.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Editing-VPN-connection-1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-All_applet_states.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-AppletStates_Gnome3.png b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-AppletStates_Gnome3.png
new file mode 100644
index 0000000..b451eb2
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-AppletStates_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Available_to_all_users_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-CableUnpluged-Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-IPv4_Settings_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Connections.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Network_Wireless_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-left-click_menu.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM-right-click_menu.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/Network_Interfaces-bridge-with-bond.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-alert.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-alert.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-applet_setting.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-applet_setting.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-applet_setting2.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-applet_setting2.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-event-configuration.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-event-configuration.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_access.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_access.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_backtrace_review.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_backtrace_review.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_event_configuration.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_event_configuration.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_main_screen.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_main_screen.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_problem_analyzing.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_problem_description.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_problem_description.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_report_confirmation.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_report_confirmation.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_configuration.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_reporting.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_rhtsupport_warning.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_select_analyzer.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_select_analyzer.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt-gui_select_reporter.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt-gui_select_reporter.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/abrt.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/abrt.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/add-remove-software-filters-available.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/add-remove-software-filters-available.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/add-remove-software-filters-end-user.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/add-remove-software-filters-end-user.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/add-remove-software-install.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/add-remove-software-install.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/add-remove-software-log.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/add-remove-software-log.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/add-remove-software-package-group.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/add-remove-software-package-group.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/add-remove-software-remove.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/add-remove-software-remove.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/add-remove-software.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/add-remove-software.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-01.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-02.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-03.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-04.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-05.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-06.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/apache-mod_ssl-genkey-07.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/authconfig_LDAP_kerb.png b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/authconfig_LDAP_kerb.png
new file mode 100644
index 0000000..7268d86
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/authconfig_LDAP_kerb.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/authconfig_advanced.png b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/authconfig_advanced.png
new file mode 100644
index 0000000..53ddd7c
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/authconfig_advanced.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/date-and-time-settings.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/date-and-time-settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/devicemngr.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/devicemngr.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/gnome-print-queue.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/gnome-print-queue.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/hwbrowser.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/hwbrowser.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-expert_settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration-target_settings.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/kdump-kernel_dump_configuration.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/oprof-start-config.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/oprof-start-config.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/oprof-start-setup.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/oprof-start-setup.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/print_conf_window.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/print_conf_window.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-add-printer.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-add-printer.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-config1.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-config1.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-config2.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-config2.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-config3.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-config3.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-config4.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-config4.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-config5.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-config5.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-config6.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-config6.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-ipp.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-ipp.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-jetdirect.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-jetdirect.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-lpd.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-lpd.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-main.png b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-main.png
new file mode 100644
index 0000000..dfd18c4
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-main.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-select-driver.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-select-driver.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-select-model.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-select-model.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/printconf-smb.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/printconf-smb.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/region-and-language-formats-add.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/region-and-language-formats-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/region-and-language-formats.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/region-and-language-formats.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/region-and-language-language-add.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/region-and-language-language-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/region-and-language-language.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/region-and-language-language.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/region-and-language-layouts-add.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/region-and-language-layouts-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/region-and-language-layouts-indicator.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/region-and-language-layouts-indicator.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/region-and-language-layouts.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/region-and-language-layouts.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/region-and-language-system.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/region-and-language-system.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/s-c-samba-basic.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/s-c-samba-basic.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/s-c-samba-create-share.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/s-c-samba-create-share.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/s-c-samba-security.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/s-c-samba-security.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/s-c-samba-users.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/s-c-samba-users.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/s-c-samba.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/s-c-samba.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/samba-nautilus-domain.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/samba-nautilus-domain.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/software-update-preferences.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/software-update-preferences.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/software-update-software-sources.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/software-update-software-sources.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/software-update.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/software-update.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/ssh-passphrase-prompt.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/ssh-passphrase-prompt.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/ssh-startup-applications-add.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/ssh-startup-applications-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/ssh-startup-applications-check.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/ssh-startup-applications-check.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/ssh-startup-applications.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/ssh-startup-applications.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/switchmail-gui.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/switchmail-gui.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-log-viewer-add.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-log-viewer-add.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-log-viewer-alerts.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-log-viewer-alerts.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-log-viewer-filters-define.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-log-viewer-filters-define.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-log-viewer-filters-enable.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-log-viewer-filters-enable.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-log-viewer-filters-manage.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-log-viewer-filters-manage.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-log-viewer.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-log-viewer.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-monitor-file-systems.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-monitor-file-systems.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-monitor-processes.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-monitor-processes.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/system-monitor-resources.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/system-monitor-resources.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-accounts-create.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-accounts-create.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-accounts-password-change.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-accounts-password-change.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-accounts-remove.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-accounts-remove.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-accounts.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-accounts.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-manager-add-group.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-manager-add-group.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-manager-add-user.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-manager-add-user.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-manager-edit-group.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-manager-edit-group.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-manager-edit-user.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-manager-edit-user.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/images/user-manager.png b/public_html/ja-JP/Fedora/17/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/17/html/System_Administrators_Guide/images/user-manager.png differ
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/index.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/index.html
new file mode 100644
index 0000000..2270d3f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><meta name="description" content="システム管理者ガイドは、Fedora 17 の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm53741680" lang="ja-JP"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="ce
nter"><span class="productname">Fedora</span> <span class="productnumber">17</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm53741680" class="title">システム管理者ガイド</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Fedora 17 の導入、設定および管理</h2></div><p class="edition">エディッション 1</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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:jhradilek at redhat.com">jhradilek at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:silas at redhat.com">silas at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="surname">Prpič</span> <s
pan class="firstname">Martin</span> [FAMILY Given]</h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mprpic at redhat.com">mprpic at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:swadeley at redhat.com">swadeley at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:eslobodo at redh
at.com">eslobodo at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:tcapek at redhat.com">tcapek at 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, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:pkovar at redhat.com">pkovar at 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, Inc.</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, Inc.</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, Inc.</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, Inc.</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="idm2970
1600" class="legalnotice"><h1 class="legalnotice">法律上の通知</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2012 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://creativecommons.org/licenses/by-sa/3.0/</a>. 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">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </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 17 の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。
+ </div></div></div></div><hr /></div><div class="toc"><dl><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#idm28337488">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="sect-Preface-Feedback.html">4. フィードバック</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-Configuring_the_Language_and_Keyboard.html">1. 言語とキーボードの設定</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Language_and_Keyboard.html#sect-Configuring_the_Language_and_Keyboard-Language">1.1. 言語の変更</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Language_and_Keyboard-Formats.html">1.2. 日付、時刻および数字の形式の変更</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Language_and_Keyboard-Layouts.html">1.3. キーボードのレイアウト変更</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Language_and_Keyboard-System.html">1.4. 現在の設定の表示</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Configuring_the_Date_and_Time.html">2. 日付と時刻の設定</a></s
pan></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">2.1. 日付と時刻の設定ツールの使い方</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html">2.2. コマンドラインツールの使用</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">2.2.1. 日付の変更方法</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html">2.2.2. 時刻の変更方法</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html">2.2.3. Network Time Protocol の設定</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_D
ate_and_Time-Additional_Resources.html">2.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Additional_Resources.html#sect-Configuring_the_Date_and_Time-Additional_Resources-Installed_Documentation">2.3.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Managing_Users_and_Groups.html">3. ユーザーとグループの管理</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">3.1. ユーザーとグループのイントロダクション</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">3.1.1. ユーザープライベートグループ</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">3.1.2. シャドウパスワード</a>
</span></dt></dl></dd><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts.html">3.2. ユーザー アカウントのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts.html#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.2.1. アカウントの設定</a></span></dt><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html">3.2.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html">3.2.3. ユーザーの削除</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">3.3. ユーザー管理のツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-configui.html#s2-redhat-config-users-list">3.3.1. ユーザーとグループを閲覧する</a></span></dt><dt><sp
an class="section"><a href="s2-redhat-config-users-user-new.html">3.3.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-group-new.html">3.3.3. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-user-properties.html">3.3.4. ユーザーのプロパティを変更する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-group-properties.html">3.3.5. グループのプロパティを変更する</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">3.4. コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">3.4.1. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">3.4.2. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="s2-users
-tools-password-aging.html">3.4.3. パスワードエージングの有効化</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">3.4.4. 自動ログアウトの有効化</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">3.4.5. グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-additional-resources.html">3.5. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">3.5.1. インストールされているドキュメント</a></span></dt></dl></dd></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-yum.html">4. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages"
>4.1. パッケージの確認と更新</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">4.1.1. 更新の確認</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">4.1.2. パッケージの更新</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">4.1.3. 設定ファイル変更の保存</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">4.2. パッケージとパッケージ グループ</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">4.2.1. パッケージの検索</a></span></dt><dt><span class="section"><a href="sec-Listing_Packages.html">4.2.2. パッケージの一覧</a></span></dt><dt><span class="section"><a href="sec-Displaying_Package_Information.html">4.2.3. パッケージ情報の表示</a></span></dt><dt><span cla
ss="section"><a href="sec-Installing.html">4.2.4. パッケージのインストール</a></span></dt><dt><span class="section"><a href="sec-Removing.html">4.2.5. パッケージの削除</a></span></dt><dt><span class="section"><a href="sec-Yum-Transaction_History.html">4.2.6. 処理とトランザクションの履歴</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">4.3. Yum と Yum リポジトリーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">4.3.1. [main] オプションの設定</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">4.3.2. [repository] オプションの設定</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">4.3.3. Yum 変数の使い方</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Current_Configuration.html">4.3.4. 現
在の設定の表示</a></span></dt><dt><span class="section"><a href="sec-Managing_Yum_Repositories.html">4.3.5. Yum リポジトリの追加・有効化および無効化</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">4.3.6. Yum リポジトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">4.4. Yum プラグイン</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Yum プラグインの無効化、有効化、設定</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">4.4.2. 追加の Yum プラグインのインストール</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">4.4.3. プラグインの説明</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Additional_Resources.html">4.5. その他のリソース</a></span></d
t></dl></dd><dt><span class="chapter"><a href="ch-PackageKit.html">5. PackageKit</a></span></dt><dd><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">5.1. ソフトウェアの更新を用いたパッケージの更新</a></span></dt><dd><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Setting_preferences_for_checking_for_updates">5.1.1. 更新の確認間隔の設定</a></span></dt><dt><span class="section"><a href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">5.1.2. ソフトウェアソースの設定</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html">5.2. ソフトウェアの追加/削除の使用</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. ソフトウェアソースの更新 (Yum リポジトリー)</a></span></dt><dt><span class="secti
on"><a href="sec-Finding_Packages_with_Filters.html">5.2.2. フィルターを用いたパッケージの検索</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Packages_and_Dependencies.html">5.2.3. パッケージ（および依存するもの）のインストールおよび削除</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Package_Groups.html">5.2.4. パッケージグループのインストールおよび削除</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Transaction_Log.html">5.2.5. トランザクションログの表示</a></span></dt></dl></dd><dt><span class="section"><a href="sec-PackageKit_Architecture.html">5.3. PackageKit アーキテクチャー</a></span></dt><dt><span class="section"><a href="ch-Graphical_Package_Management-sec-Additional_Resources.html">5.4. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="part-Networking.html">III
. ネットワーク</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-NetworkManager.html">6. NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="ch-NetworkManager.html#sec-The_NetworkManager_Daemon">6.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html">6.2. Interacting with NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">6.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">6.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.html">6.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-User_and_System_Connections.html">6.2.4. User and System Connections</a></s
pan></dt></dl></dd><dt><span class="section"><a href="sec-Establishing_Connections.html">6.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Establishing_Connections.html#sec-Establishing_a_Wired_Ethernet_Connection">6.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Wireless_Connection.html">6.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">6.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">6.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html">6.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_Routes.html">6.3.6. Establishing Routes</a></span></dt></dl></dd><dt><s
pan class="section"><a href="sec-Configuring_Connection_Settings.html">6.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html#sec-Configuring_802.1x_Security">6.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_Wireless_Security.html">6.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_PPP_Point-to-Point_Settings.html">6.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv4_Settings.html">6.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Settings.html">6.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sec-NetworkManager_Architecture.html">6.5. NetworkManager Architecture</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Networ
k_Interfaces.html">7. ネットワーク・インターフェース</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Network_Interfaces.html#s1-networkscripts-files">7.1. ネットワーク設定ファイル</a></span></dt><dt><span class="section"><a href="s1-networkscripts-interfaces.html">7.2. インターフェース設定ファイル</a></span></dt><dd><dl><dt><span class="section"><a href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">7.2.1. イーサネット インターフェース</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-chan.html">7.2.2. チャンネル・ボンディング・インターフェース</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces_network-bridge.html">7.2.3. ネットワークブリッジ</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html">7.2.4. Setting up 802.1q VLAN tagging</a></span></dt><
dt><span class="section"><a href="s2-networkscripts-interfaces-alias.html">7.2.5. エイリアス ファイルとクローン ファイル</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-ppp0.html">7.2.6. ダイヤルアップ インターフェース</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-other.html">7.2.7. 他のインターフェース</a></span></dt></dl></dd><dt><span class="section"><a href="s1-networkscripts-control.html">7.3. インターフェース制御スクリプト</a></span></dt><dt><span class="section"><a href="s1-networkscripts-static-routes.html">7.4. スタティック ルートの設定</a></span></dt><dt><span class="section"><a href="s1-networkscripts-functions.html">7.5. ネットワーク機能ファイル</a></span></dt><dt><span class="section"><a href="s1-networkscripts-resources.html">7.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ne
tworkscripts-resources.html#s2-networkscripts-docs-inst">7.6.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="part-Infrastructure_Services.html">IV. インフラストラクチャーサービス</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Services_and_Daemons.html">8. サービスおよびデーモン</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">8.1. サービスの設定</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">8.1.1. サービスの有効化</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">8.1.2. サービスの無効化</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">8.2. サービスの実行</a></span></dt><dd><dl><dt><spa
n class="section"><a href="s1-services-running.html#s3-services-running-checking">8.2.1. サービスの状態の確認</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">8.2.2. サービスの実行</a></span></dt><dt><span class="section"><a href="s3-services-running-stopping.html">8.2.3. サービスの停止</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">8.2.4. サービスの再起動</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">8.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">8.3.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">8.3.2. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configu
ring_Authentication.html">9. 認証の設定</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">9.1. 認証の設定ツール</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">9.1.1. 識別と認証</a></span></dt><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">9.1.2. 高度なオプション</a></span></dt><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">9.1.3. コマンドライン版</a></span></dt></dl></dd><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">9.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-SSSD_User_Guide-In
troduction.html#sect-SSSD_User_Guide-Introduction-What_is_SSSD">9.2.1. SSIDとは?</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html">9.2.2. SSIDの特徴</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Setting_Up_SSSD.html">9.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Services.html">9.2.4. サービスの設定</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Domains.html">9.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">9.2.6. Setting Up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html">9.2.7. Configuring a Proxy Domain</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Tr
oubleshooting.html">9.2.8. トラブルシューティング</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">9.2.9. SSSD Configuration File Format</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">10. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">10.1. SSH プロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">10.1.1. なぜ SSH を使うのか？</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-features">10.1.2. 主な機能</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">10.1.3. プロトコル・バージョン</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">10.1.4. SSH コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span cl
ass="section"><a href="s1-ssh-configuration.html">10.2. OpenSSH の設定</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">10.2.1. 設定ファイル</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">10.2.2. OpenSSH サーバーの起動</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">10.2.3. リモート接続に対する SSH の要求</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">10.2.4. キー認証の使用</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clients.html">10.3. OpenSSH クライアント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">10.3.1. ssh ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">10.3.2. <code class="command">scp</code> ユーティリティ
の使用方法</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">10.3.3. <code class="command">sftp</code> ユーティリティの使用方法</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-beyondshell.html">10.4. 安全なシェル以上のもの</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">10.4.1. X11 転送</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">10.4.2. ポート転送</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">10.5. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-openssh-additional-resources.html#s2-openssh-installed-docs">10.5.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-openssh-useful-websites.html">10.5.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></
dl></dd><dt><span class="part"><a href="part-Servers.html">V. サーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-DHCP_Servers.html">11. DHCP サーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DHCP_Servers.html#s1-dhcp-why">11.1. DHCP を使用ã™ã‚‹ç†ç”±</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">11.2. DHCP サーãƒãƒ¼ã®è¨å®š</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-configuring-server.html#config-file">11.2.1. è¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></span></dt><dt><span class="section"><a href="lease-database.html">11.2.2. リースデータベース</a></span></dt><dt><span class="section"><a href="ch11s02s03.html">11.2.3. サーãƒãƒ¼ã®èµ·å‹•ã¨åœæ¢</a></span></dt><dt><span class="section"><a href="dhcp-relay-agent.html">11.2.4. DHCP リレーエージェント</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp-configuring-client.html">11.3. DHCP クライã
‚¢ãƒ³ãƒˆã®è¨å®š</a></span></dt><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html">11.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configuration">11.4.1. ホストã®è¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">11.5. IPv6 å‘ã‘ DHCP (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">11.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">11.6.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-DNS_Servers.html">12. DNS サーãƒãƒ¼</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DNS_Servers.html#s1-Introduction_to_DNS">12.1. DNS ã®æ¦‚è¦</a></span></dt><dd><d
l><dt><span class="section"><a href="ch-DNS_Servers.html#s2-dns-introduction-zones">12.1.1. ネームサーバーゾーン</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">12.1.2. ネームサーバーのタイプ</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#s2-dns-introduction-bind">12.1.3. ネームサーバーとしての BIND</a></span></dt></dl></dd><dt><span class="section"><a href="s1-BIND.html">12.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="s1-BIND.html#s2-bind-namedconf">12.2.1. named サービスの設定</a></span></dt><dt><span class="section"><a href="s2-bind-zone.html">12.2.2. ゾーンファイルの編集</a></span></dt><dt><span class="section"><a href="s2-bind-rndc.html">12.2.3. rndc ユーティリティの使用法</a></span></dt><dt><span class="section"><a href="s2-bind-dig.html">12.2.4. dig ユーティリティの使用</a></span></dt><dt><span class="
section"><a href="s2-bind-features.html">12.2.5. BIND の高度な機能</a></span></dt><dt><span class="section"><a href="s2-bind-mistakes.html">12.2.6. よくある間違いを避けるために</a></span></dt><dt><span class="section"><a href="s2-bind-additional-resources.html">12.2.7. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Web_Servers.html">13. ウェブ サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">13.1. Apache HTTP サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-features">13.1.1. 新機能</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-changes">13.1.2. 注目すべき変更</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">13.1.3. 設定の更新</a></span></dt><dt><span class="section"><a
href="ch-Web_Servers.html#s2-apache-running">13.1.4. httpd サービスの実行方法</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-editing">13.1.5. 設定ファイルの編集</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">13.1.6. Working with Modules</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-virtualhosts">13.1.7. 仮想ホストのセットアップ</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">13.1.8. SSL サーバーのセットアップ</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">13.1.9. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Mail_Servers.html">14. メールサーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s1-email-protocols">14.1. 電子メールプロトコル</a></span>
</dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-send">14.1.1. メール トランスポートのプロトコル</a></span></dt><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-client">14.1.2. メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">14.2. 電子メールプログラム分類</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">14.2.1. メール転送エージェント (Mail Transport Agent)</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">14.2.2. メール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">14.2.3. メール ユーザー エージェント</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">14.3. Mail Transport Agent</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-email-mta.html#s2-email-mta-postfix">14.3.1. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-sendmail.html">14.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">14.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="s2-email-switchmail.html">14.3.4. Mail Transport Agent (MTA) の設定</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mda.html">14.4. メール配送エージェント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">14.4.1. Procmail の設定</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">14.4.2. Procmail レシピ</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">14.5. メールユーザーエージェント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">14.5.1. 通
信のセキュリティ</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">14.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">14.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">14.6.2. 役に立つ Web サイト</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">14.6.3. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Directory_Servers.html">15. ディレクトリー サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">15.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">15.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directo
ry_Servers.html#s2-ldap-installation">15.1.2. OpenLDAP 製品群のインストール</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">15.1.3. OpenLDAP サーバーの設定法</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-running">15.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam">15.1.5. システムが OpenLDAP を使用して認証を実行するように設定する</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-resources">15.1.6. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-File_and_Print_Servers.html">16. ファイルサーバーおよびプリントサーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">16.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a
href="ch-File_and_Print_Servers.html#samba-rgs-overview">16.1.1. Samba の概要</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">16.1.2. Samba デーモンと関連サービス</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-connect-share">16.1.3. Samba シェアへの接続</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-configuring">16.1.4. Samba サーバーの設定</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-startstop">16.1.5. Samba の開始と停止</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">16.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">16.1.7. Samba のセキュリティモード</a></spa
n></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">16.1.8. Samba のアカウント情報データベース</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">16.1.9. Samba ネットワークブラウジング</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-cups">16.1.10. CUPS 印刷サポートを使った Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-programs">16.1.11. Samba ディストリビューションプログラム</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-resources">16.1.12. その他のリソース</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">16.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-FTP.html#s2-ftp-protocol">16.2.1. ファイル伝送プロトコル</a></span></dt>
<dt><span class="section"><a href="s2-ftp-servers.html">16.2.2. FTP サーバー</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">16.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">16.2.4. <code class="command">vsftpd</code> の開始と停止</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">16.2.5. <code class="command">vsftpd</code> 設定オプション</a></span></dt><dt><span class="section"><a href="s2-ftp-resources.html">16.2.6. その他のリソース</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Printer_Configuration.html">16.3. プリンタの設定</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">16.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">16.3.2. Starting Pr
inter Setup</a></span></dt><dt><span class="section"><a href="sec-Adding_Other_Printer.html">16.3.3. ローカルプリンタの追加</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">16.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">16.3.5. IPP プリンタの追加</a></span></dt><dt><span class="section"><a href="sec-printing-LPDLPR-printer.html">16.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">16.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">16.3.8. プリンタモデルの選択と終了</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">16.3.9. Printing a test page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">16.3.10. 既存プリンタの変更</a></span></dt><
dt><span class="section"><a href="s1-printing-additional-resources.html">16.3.11. その他のリソース</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="part-Monitoring_and_Automation.html">VI. 監視および自動化</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></s
pan></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-fi
lesystems-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 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. Retrievin
g 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-configuring-rsyslog">18.1. rsyslog の設定法</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-global-directives">18.1.1. 全体ディレクティブ</a></span></dt><dt><span class="section"><a href="ch-Viewi
ng_and_Managing_Log_Files.html#s2-modules">18.1.2. モジュール</a></span></dt><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-rules">18.1.3. ルール</a></span></dt><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-rsyslog-cmd-options">18.1.4. <span class="application"><strong>rsyslog</strong></span> コマンドラインè¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="s1-logfiles-locating.html">18.2. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’探ã™</a></span></dt><dd><dl><dt><span class="section"><a href="s1-logfiles-locating.html#configuring-logrotate">18.2.1. logrotate ã®è¨å®šæ³•</a></span></dt></dl></dd><dt><span class="section"><a href="s1-logfiles-viewing.html">18.3. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º</a></span></dt><dt><span class="section"><a href="s1-logfiles-adding.html">18.4. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¿½åŠ </a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">18.5. ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’監è¦
–ã™ã‚‹</a></span></dt><dt><span class="section"><a href="s1-log-files-additional-resources.html">18.6. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="s1-log-files-additional-resources.html#s2-log-files-installed-docs">18.6.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt><dt><span class="section"><a href="s2-log-files-useful-websites.html">18.6.2. å½¹ã«ç«‹ã¤ Web サイト</a></span></dt></dl></dd></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#s2-autotasks-cron-service">19.1.1. サービスã®èµ·å‹•ã¨åœæ¢</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">
19.1.2. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">19.1.3. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">19.1.4. Cron ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ã®åˆ¶å¾¡</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">19.1.5. Black/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#s2-autotasks-at-configuring">19.2.1. At ジョブã®è¨å®š</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">19.2.2. batch ジョブã®è¨å®š</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">19.2.3. ä¿ç•™ã‚¸ãƒ§ãƒ–ã®è
¡¨ç¤º</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">19.2.4. ãã®ä»–ã®ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã‚ªãƒ—ション</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">19.2.5. at 㨠batch ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ã®åˆ¶å¾¡</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-service.html">19.2.6. サービスã®èµ·å‹•ã¨åœæ¢</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">19.3. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">19.3.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt></dl></dd></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><dt><s
pan class="section"><a href="s1-oprofile-configuring.html">20.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">20.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">20.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">20.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">20.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">20.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">20.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">20.5.1. Using <code class="command">opreport</code> </a></span></dt><dt
><span class="section"><a href="s2-oprofile-reading-opreport-single.html">20.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">20.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">20.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">20.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">20.7. 使用法の例</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">20.8. 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.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-gui
.html">20.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">20.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="s1-oprofile-additional-resources.html">20.11. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-docs">20.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="s2-oprofile-useful-websites.html">20.11.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="part-Kernel_Module_and_Driver_Configuration.html">VII. カーネル、モジュールおよびドライバーの設定</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Manually_Upgrading_the_Kernel.html">21. カーネルをアップグレードする</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">21
.1. カーネルパッケージの概要</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">21.2. アップグレードの準備</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">21.3. アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">21.4. アップグレードの実行</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">21.5. 初期RAMディスクイメージの確認</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">21.6. ブートローダの確認</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><sp
an class="section"><a href="s2-kernel-boot-loader-pseries.html">21.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">22. 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">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. モジュールの読み込み方法</a></span></dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22
.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sec-Specific_Kernel_Module_Capabilities.html">22.7. Specific Kernel Module Capabilities</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Specific_Kernel_Module_Capabilities.html#sec-Using_Multiple_Ethernet_Cards">22.7.1. 複数のイーサネットカードの使用</a></span></dt><dt><span class="section"><a href="sec-Using_Channel_Bonding.html">22.7.2. Using Channel Bonding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">22.8. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html#s2-kernel-modules-additional-resources-installed">22.8.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-kernel-modules-additional-resources-websites.html">22.8.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl>
</dd><dt><span class="chapter"><a href="ch-kdump.html">23. The kdump Crash Recovery Service</a></span></dt><dd><dl><dt><span class="section"><a href="ch-kdump.html#s1-kdump-installation">23.1. Installing the kdump Service</a></span></dt><dt><span class="section"><a href="s1-kdump-configuration.html">23.2. Configuring the kdump Service</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kdump-configuration.html#s2-kdump-configuration-firstboot">23.2.1. Configuring the kdump at First Boot</a></span></dt><dt><span class="section"><a href="s2-kdump-configuration-gui.html">23.2.2. Using the Kernel Dump Configuration Utility</a></span></dt><dt><span class="section"><a href="s2-kdump-configuration-cli.html">23.2.3. Configuring kdump on the Command Line</a></span></dt><dt><span class="section"><a href="s2-kdump-configuration-testing.html">23.2.4. Testing the Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kdump-crash.html">23.3. Analyzing the Co
re Dump</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kdump-crash.html#s2-kdump-crash-running">23.3.1. Running the crash Utility</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-log.html">23.3.2. Displaying the Message Buffer</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-backtrace.html">23.3.3. Displaying a Backtrace</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-processes.html">23.3.4. Displaying a Process Status</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-memory.html">23.3.5. Displaying Virtual Memory Information</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-files.html">23.3.6. Displaying Open Files</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-exit.html">23.3.7. Exiting the Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kdump-resources.html">23.4. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a
href="s1-kdump-resources.html#s2-kdump-resources-installed">23.4.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-kdump-resources-online.html">23.4.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="appendix"><a href="appe-Consistent_Network_Device_Naming.html">A. Consistent Network Device Naming</a></span></dt><dd><dl><dt><span class="section"><a href="appe-Consistent_Network_Device_Naming.html#sect-Consistent_Network_Device_Naming-Affected_Systems">A.1. Affected Systems</a></span></dt><dt><span class="section"><a href="sect-Consistent_Network_Device_Naming-System_Requirements.html">A.2. システム要求</a></span></dt><dt><span class="section"><a href="sect-Consistent_Network_Device_Naming-Enabling_and_Disabling.html">A.3. Enabling and Disabling the Feature</a></span></dt><dt><span class="section"><a href="sect-Consistent_Network_Device_Naming-Notes.html">A.4. Notes for Ad
ministrators</a></span></dt></dl></dd><dt><span class="appendix"><a href="ch-RPM.html">B. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="ch-RPM.html#s1-rpm-design">B.1. RPM の設計目標</a></span></dt><dt><span class="section"><a href="s1-rpm-using.html">B.2. RPMの使用法</a></span></dt><dd><dl><dt><span class="section"><a href="s1-rpm-using.html#s2-rpm-finding">B.2.1. RPM パッケージの検索</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Upgrading.html">B.2.2. インストールとアップグレード</a></span></dt><dt><span class="section"><a href="sec-Configuration_File_Changes.html">B.2.3. 設定ファイルの変更</a></span></dt><dt><span class="section"><a href="s2-rpm-uninstalling.html">B.2.4. アンインストール</a></span></dt><dt><span class="section"><a href="s2-rpm-freshening.html">B.2.5. インストール済みのアップグレードの実行</a></span></dt><dt><span class="section"><a href="s2-rpm-queryi
ng.html">B.2.6. å•ã„åˆã‚ã›</a></span></dt><dt><span class="section"><a href="s2-rpm-verifying.html">B.2.7. 検証</a></span></dt></dl></dd><dt><span class="section"><a href="s1-check-rpm-sig.html">B.3. パッケージã®ç½²åを確èªã™ã‚‹</a></span></dt><dd><dl><dt><span class="section"><a href="s1-check-rpm-sig.html#s2-keys-importing">B.3.1. Importing Keys</a></span></dt><dt><span class="section"><a href="s2-keys-checking.html">B.3.2. Verifying Signature of Packages</a></span></dt></dl></dd><dt><span class="section"><a href="s1-rpm-impressing.html">B.4. Practical and Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="s1-rpm-additional-resources.html">B.5. ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="s1-rpm-additional-resources.html#s2-rpm-installed-docs">B.5.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt><dt><span class="section"><a href="s2-rpm-useful-websites.html">B.5.2. å½¹ã
«ç«‹ã¤ Web サイト</a></span></dt><dt><span class="section"><a href="s2-rpm-related-books.html">B.5.3. 関連書ç±</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="ch-The_X_Window_System.html">C. X Window System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_X_Window_System.html#s1-x-server">C.1. The X Server</a></span></dt><dt><span class="section"><a href="s1-x-clients.html">C.2. デスクトップ環境ã¨ã‚¦ã‚£ãƒ³ãƒ‰ã‚¦ãƒžãƒãƒ¼ã‚¸ãƒ£</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-clients.html#s2-x-clients-desktop">C.2.1. デスクトップ環境</a></span></dt><dt><span class="section"><a href="s2-x-clients-winmanagers.html">C.2.2. ウィンドウマãƒãƒ¼ã‚¸ãƒ£</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-server-configuration.html">C.3. X サーãƒãƒ¼è¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf-stru
ct">C.3.1. The Structure of the Configuration</a></span></dt><dt><span class="section"><a href="s2-x-server-config-xorg.conf.d.html">C.3.2. The <code class="filename">xorg.conf.d</code> Directory</a></span></dt><dt><span class="section"><a href="s2-x-server-config-xorg.conf.html">C.3.3. The <code class="filename">xorg.conf</code> File</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-fonts.html">C.4. フォント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-fonts.html#s3-x-fonts-fontconfig-add">C.4.1. Fontconfig へのフォントの追加</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-additional-resources.html">C.5. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-additional-resources.html#s2-x-installed-documentation">C.5.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-x-useful-websites.html">C.5.2. 役に立つ Web サイト
</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="ch-The_sysconfig_Directory.html">D. sysconfig ディレクトリー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s1-sysconfig-files">D.1. Files in the /etc/sysconfig/ Directory</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-arpwatch">D.1.1. /etc/sysconfig/arpwatch </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-authconfig">D.1.2. /etc/sysconfig/authconfig </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-autofs">D.1.3. /etc/sysconfig/autofs </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-clock">D.1.4. /etc/sysconfig/clock </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-dhcpd">D.1.5. /etc/sysconfig/dhcpd </a></span
></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-firewall">D.1.6. /etc/sysconfig/firstboot </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-i18n">D.1.7. /etc/sysconfig/i18n </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-init">D.1.8. /etc/sysconfig/init </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ip6tables">D.1.9. /etc/sysconfig/ip6tables-config </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-kybd">D.1.10. /etc/sysconfig/keyboard </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ldap">D.1.11. /etc/sysconfig/ldap </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-named">D.1.12. /etc/sysconfig/named </a></span></dt><dt><span class="section"><a href="ch-
The_sysconfig_Directory.html#s2-sysconfig-network">D.1.13. /etc/sysconfig/network</a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ntpd">D.1.14. /etc/sysconfig/ntpd </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-quagga">D.1.15. /etc/sysconfig/quagga </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-radvd">D.1.16. /etc/sysconfig/radvd </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-samba">D.1.17. /etc/sysconfig/samba </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-selinux">D.1.18. /etc/sysconfig/selinux </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-sendmail">D.1.19. /etc/sysconfig/sendmail </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-spam
d">D.1.20. /etc/sysconfig/spamassassin </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-squid">D.1.21. /etc/sysconfig/squid </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-rcu">D.1.22. /etc/sysconfig/system-config-users </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-vncservers">D.1.23. /etc/sysconfig/vncservers </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-xinetd">D.1.24. /etc/sysconfig/xinetd </a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysconfig-etcsysconf-dir.html">D.2. Directories in the /etc/sysconfig/ Directory</a></span></dt><dt><span class="section"><a href="s1-sysconfig-additional-resources.html">D.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysconfig-additional-resources.html#s2-sysconfig-installed-document
ation">D.3.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="ch-proc.html">E. The proc File System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-proc.html#s1-proc-virtual">E.1. A Virtual File System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-proc.html#s2-proc-viewing">E.1.1. Viewing Virtual Files</a></span></dt><dt><span class="section"><a href="ch-proc.html#s2-proc-change">E.1.2. Changing Virtual Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-topfiles.html">E.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="s1-proc-topfiles.html#s2-proc-buddyinfo">E.2.1. /proc/buddyinfo </a></span></dt><dt><span class="section"><a href="s2-proc-cmdline.html">E.2.2. /proc/cmdline </a></span></dt><dt><span class="section"><a href="s2-proc-cpuinfo.html">E.2.3. /proc/cpuinf
o </a></span></dt><dt><span class="section"><a href="s2-proc-crypto.html">E.2.4. /proc/crypto </a></span></dt><dt><span class="section"><a href="s2-proc-devices.html">E.2.5. /proc/devices </a></span></dt><dt><span class="section"><a href="s2-proc-dma.html">E.2.6. /proc/dma </a></span></dt><dt><span class="section"><a href="s2-proc-execdomains.html">E.2.7. /proc/execdomains </a></span></dt><dt><span class="section"><a href="s2-proc-fb.html">E.2.8. /proc/fb </a></span></dt><dt><span class="section"><a href="s2-proc-filesystems.html">E.2.9. /proc/filesystems </a></span></dt><dt><span class="section"><a href="s2-proc-interrupts.html">E.2.10. /proc/interrupts </a></span></dt><dt><span class="section"><a href="s2-proc-iomem.html">E.2.11. /proc/iomem </a></span></dt><dt><span class="section"><a href="s2-proc-ioports.html">E.2.12. /proc/ioports </a></span></dt><dt><span class="section"><a href="s2-proc-kcore.html">E.2.13. /proc/kcore </a></span></dt><dt><span class="sectio
n"><a href="s2-proc-kmsg.html">E.2.14. /proc/kmsg </a></span></dt><dt><span class="section"><a href="s2-proc-loadavg.html">E.2.15. /proc/loadavg </a></span></dt><dt><span class="section"><a href="s2-proc-locks.html">E.2.16. /proc/locks </a></span></dt><dt><span class="section"><a href="s2-proc-mdstat.html">E.2.17. /proc/mdstat </a></span></dt><dt><span class="section"><a href="s2-proc-meminfo.html">E.2.18. /proc/meminfo </a></span></dt><dt><span class="section"><a href="s2-proc-misc.html">E.2.19. /proc/misc </a></span></dt><dt><span class="section"><a href="s2-proc-modules.html">E.2.20. /proc/modules </a></span></dt><dt><span class="section"><a href="s2-proc-mounts.html">E.2.21. /proc/mounts </a></span></dt><dt><span class="section"><a href="s2-proc-mtrr.html">E.2.22. /proc/mtrr </a></span></dt><dt><span class="section"><a href="s2-proc-partitions.html">E.2.23. /proc/partitions </a></span></dt><dt><span class="section"><a href="s2-proc-slabinfo.html">E.2.24. /proc
/slabinfo </a></span></dt><dt><span class="section"><a href="s2-proc-stat.html">E.2.25. /proc/stat </a></span></dt><dt><span class="section"><a href="s2-proc-swaps.html">E.2.26. /proc/swaps </a></span></dt><dt><span class="section"><a href="s2-proc-sysrq-trigger.html">E.2.27. /proc/sysrq-trigger </a></span></dt><dt><span class="section"><a href="s2-proc-uptime.html">E.2.28. /proc/uptime </a></span></dt><dt><span class="section"><a href="s2-proc-version.html">E.2.29. /proc/version </a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-directories.html">E.3. Directories within /proc/</a></span></dt><dd><dl><dt><span class="section"><a href="s1-proc-directories.html#s2-proc-processdirs">E.3.1. Process Directories</a></span></dt><dt><span class="section"><a href="s2-proc-dir-bus.html">E.3.2. /proc/bus/ </a></span></dt><dt><span class="section"><a href="s2-proc-pci.html">E.3.3. /proc/bus/pci </a></span></dt><dt><span class="section"><a href="s2-proc-dir-drive
r.html">E.3.4. /proc/driver/ </a></span></dt><dt><span class="section"><a href="s2-proc-dir-fs.html">E.3.5. /proc/fs </a></span></dt><dt><span class="section"><a href="s2-proc-dir-irq.html">E.3.6. /proc/irq/ </a></span></dt><dt><span class="section"><a href="s2-proc-dir-net.html">E.3.7. /proc/net/ </a></span></dt><dt><span class="section"><a href="s2-proc-dir-scsi.html">E.3.8. /proc/scsi/ </a></span></dt><dt><span class="section"><a href="s2-proc-dir-sys.html">E.3.9. /proc/sys/ </a></span></dt><dt><span class="section"><a href="s2-proc-dir-sysvipc.html">E.3.10. /proc/sysvipc/ </a></span></dt><dt><span class="section"><a href="s2-proc-tty.html">E.3.11. /proc/tty/ </a></span></dt><dt><span class="section"><a href="s2-proc-pid.html">E.3.12. /proc/<em class="replaceable"><code>PID</code></em>/ </a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-sysctl.html">E.4. Using the sysctl Command</a></span></dt><dt><span class="section"><a href="s1-proc-additiona
l-resources.html">E.5. 参考文献</a></span></dt></dl></dd><dt><span class="appendix"><a href="app-Revision_History.html">F. 改訂履歴</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/17/html/System_Administrators_Guide/ix01.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/ix01.html
new file mode 100644
index 0000000..0dd7997
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="付録F 改訂履歴" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="idm49751936"><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>サーバーオプション, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-server">サーバー オプション</a></dt><dt>ユーザーオプション, <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 /dev/oprofile/ </a></dt><dt>/dev/shm, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>/etc/named.conf (参照 BIND)</dt><dt> /etc/sysconfig/ ディレクトリー (参照 sysconfig ディレクトリー)</dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="ch11s02s03.html">サーバーの起動と停止</a></dt><dt> /proc/ directory (参照 proc file system)</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>イーサネット (参照 ネットワーク)</dt><dt>ウェブ サーバー (参照 Apache HTTP Server)</dt><dt>カーネル</dt><dd><dl><dt>RPM パッケージ, <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><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" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd></dl></dd><dt>キーボードの設定 (参照 地域と言語)</dt><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-directo
ries.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><dt>system-config-users, <a class="indexterm" href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">ユーザープライベートグループ</a></dt><dt>User Manager, <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="s1-users-groups-additional-resources.html">その他のリソース</a></dt><dd><dl><dt>インストールされているドキュメント, <a class="indexterm" href="s1-u
sers-groups-additional-resources.html#s2-users-groups-documentation">インストールされているドキュメント</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="s2-redhat-config-users-group-properties.html">グループのプロパティを変更する</a></dt><dt>グループのプロパティの変更, <a class="indexterm" href="s2-redhat-config-users-group-properties.html">グループのプロパティを変更する</a></dt><dt>グループの追加, <a class="indexterm" href="s2-redhat-config-users-group-new.html">新規グループを追加する</a></dt><dt>グループ一覧のフィルター, <a class="indexterm" href="s1-users-configui.html#s2-redhat-config-users-list">ユーザーとグループを閲覧する</a></dt><dt>グループ一覧の表示,
<a class="indexterm" href="s1-users-configui.html">ユーザー管理のツールを使う</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">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></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>セカンダリãƒãƒ¼ãƒ サーãƒãƒ¼ (å‚ç…§ BIND)</dt><dt> ã‚»ã‚ュリティ プラグイン (å‚ç…§ ã‚»ã‚ュリティ)</dt><dt>ã‚»ã‚ュリティ関連ã®ãƒ‘ッケージ</dt><dd><dl><dt>ã‚»ã‚ュリティ関連ã®ãƒ‘ッケージ更新, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">パッケージã®æ›´æ–°</a></dt></dl></dd><dt>タイムゾーン, <a class="indexterm" href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">日付ã¨æ™‚刻ã®è¨å®šãƒ„ールã®ä½¿ã„æ–¹</a></dt><dd><dl><dt>(å‚ç…§ 日付ã¨æ™‚刻)</dt></dl></dd><dt>ãƒãƒ£ãƒãƒ«ãƒ»ãƒœãƒ³ãƒ‡ã‚£ãƒ³ã‚°</dt><dd><dl><dt>インターフェース</dt><d
d><dl><dt>設定, <a class="indexterm" href="s2-networkscripts-interfaces-chan.html">チャンネル・ボンディング・インターフェース</a></dt></dl></dd></dl></dd><dt>ツール</dt><dd><dl><dt> 認証の設定ツール , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">認証の設定ツール</a></dt></dl></dd><dt>ディレクトリサーバー (参照 OpenLDAP)</dt><dt>ネットワーク</dt><dd><dl><dt>インターフェース</dt><dd><dl><dt>イーサネット, <a class="indexterm" href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">イーサネット インターフェース</a></dt><dt>エイリアス, <a class="indexterm" href="s2-networkscripts-interfaces-alias.html">エイリアス ファイルとクローン ファイル</a></dt><dt>クローン, <a class="indexterm" href="s2-networkscripts-interfaces-alias.html">エイリアス ファイルとクローン ファイル</a>
</dt><dt>ダイアルアップ, <a class="indexterm" href="s2-networkscripts-interfaces-ppp0.html">ダイヤルアップ インターフェース</a></dt><dt>チャネル・ボンディング, <a class="indexterm" href="s2-networkscripts-interfaces-chan.html">チャンネル・ボンディング・インターフェース</a></dt></dl></dd><dt>インターフェースの設定ファイル, <a class="indexterm" href="s1-networkscripts-interfaces.html">インターフェース設定ファイル</a></dt><dt>コマンド</dt><dd><dl><dt> /sbin/ifdown , <a class="indexterm" href="s1-networkscripts-control.html">インターフェース制御スクリプト</a></dt><dt> /sbin/ifup , <a class="indexterm" href="s1-networkscripts-control.html">インターフェース制御スクリプト</a></dt></dl></dd><dt>スクリプト, <a class="indexterm" href="ch-Network_Interfaces.html">ネットワーク・インターフェース</a></dt><dt>機能, <a class="indexterm" href="s1-networks
cripts-functions.html">ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æ©Ÿèƒ½ãƒ•ã‚¡ã‚¤ãƒ«</a></dt><dt>è¨å®š, <a class="indexterm" href="s1-networkscripts-interfaces.html">インターフェースè¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></dt><dt>è¨å®šãƒ•ã‚¡ã‚¤ãƒ«, <a class="indexterm" href="ch-Network_Interfaces.html#s1-networkscripts-files">ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯è¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></dt><dt>è¿½åŠ ãƒªã‚½ãƒ¼ã‚¹, <a class="indexterm" href="s1-networkscripts-resources.html">ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></dt></dl></dd><dt>ãƒãƒ¼ãƒ サーãƒãƒ¼ (å‚ç…§ DNS)</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>PackageKit を用ã„㟠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¡¨ç¤º, <a class="indexterm" href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">ソフトウェアソースã®è¨å®š</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®ã‚¢ãƒ³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a>, <a class="indexterm" href="sec-Installing_and_Removing_Packages_and_Dependencies.html">パッケージ（ãŠã‚ˆã³ä¾å˜ã™ã‚‹ã‚‚ã®ï¼‰ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></dt><dd><dl><dt>ä¾å˜æ€§, <a class="indexterm" href="sec-Installing_and_Removing_Packages_and_Dependencies.html">パッケージ（ãŠã‚ˆã³ä¾å˜ã™ã‚‹ã‚‚ã®ï¼‰ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã
³å‰Šé™¤</a></dt></dl></dd><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®å‰Šé™¤, <a class="indexterm" href="sec-Installing_and_Removing_Packages_and_Dependencies.html">パッケージ（ãŠã‚ˆã³ä¾å˜ã™ã‚‹ã‚‚ã®ï¼‰ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®æ›´æ–°, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dd><dl><dt>PolicyKit, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">ソフトウェアã®æ›´æ–°ã‚’用ã„ãŸãƒ‘ッケージã®æ›´æ–°</a></dt><dt>ソフトウェアã®æ›´æ–°, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">ソフトウェアã®æ›´æ–°ã‚’用ã„ãŸãƒ‘ッケージã®æ›´æ–°</a></dt></dl></dd><dt>PackageKit を用ã„ã
Ÿãƒ‘ッケージã®ç®¡ç†, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®è¡¨ç¤º, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>PackageKit を用ã„ãŸãƒ‘ッケージã®è¨å®š</dt><dd><dl><dt>確èªã®é–“éš”, <a class="indexterm" href="ch-PackageKit.html#sec-Setting_preferences_for_checking_for_updates">æ›´æ–°ã®ç¢ºèªé–“éš”ã®è¨å®š</a></dt></dl></dd><dt>PackageKit を用ã„ãŸãƒ•ã‚£ãƒ«ã‚¿ãƒ¼, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dd><dl><dt>Free, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>インストール済, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>インストール済ã®ç‰©ã®ã¿, <a class="indexterm" href="sec-Findin
g_Packages_with_Filters.html">フィルターを用いたパッケージの検索</a></dt><dt>エンドユーザーのファイルのみ, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用いたパッケージの検索</a></dt><dt>グラフィカルのみ, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用いたパッケージの検索</a></dt><dt>サブパッケージを隠す, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用いたパッケージの検索</a></dt><dt>ディストリ固有のパッケージのみ, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用いたパッケージの検索</a></dt><dt>フィルターをかけない, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用いたパッケージの検索</a></dt><dt>利用可能なもののみ, <a class="indexterm" href="sec
-Finding_Packages_with_Filters.html">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>最新パッケージã®ã¿, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>開発, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt><dt>開発版ã®ã¿, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">フィルターを用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</a></dt></dl></dd><dt>PackageKit を用ã„ãŸè¿½åŠ ã¨å‰Šé™¤, <a class="indexterm" href="sec-Using_Add_Remove_Software.html">ソフトウェアã®è¿½åŠ /削除ã®ä½¿ç”¨</a></dt><dt>RPM</dt><dd><dl><dt>アンインストール, <a class="indexterm" href="s2-rpm-uninstalling.html">アンインストール</a></dt><dt>インストール済ã¿ã®ã‚¢ãƒƒãƒ—グレードã®å®Ÿè¡Œ, <a class="indexterm" href="s2-rpm-freshening.html">インストール済ã¿ã
®ã‚¢ãƒƒãƒ—グレードã®å®Ÿè¡Œ</a></dt><dt>ティップス, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>削除, <a class="indexterm" href="s2-rpm-uninstalling.html">アンインストール</a></dt><dt>検証, <a class="indexterm" href="s2-rpm-verifying.html">検証</a></dt><dt>è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®å¤‰æ›´, <a class="indexterm" href="sec-Configuration_File_Changes.html">è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®å¤‰æ›´</a></dt></dl></dd><dt>RPM ã®ã‚¢ãƒƒãƒ—グレード, <a class="indexterm" href="sec-Installing_and_Upgrading.html">インストールã¨ã‚¢ãƒƒãƒ—グレード</a></dt><dt>RPM ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="sec-Installing_and_Upgrading.html">インストールã¨ã‚¢ãƒƒãƒ—グレード</a></dt><dt>RPM パッケージã®æ¤œç´¢, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">RPM パッケージã®æ¤œç´¢</a></dt><dt>Yum を用ã„ãŸã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="sec-Installing.htm
l">パッケージのインストール</a></dt><dt>Yum を用いたパッケージ グループのインストール, <a class="indexterm" href="sec-Installing.html">パッケージのインストール</a></dt><dt>Yum を用いたパッケージ グループの削除, <a class="indexterm" href="sec-Removing.html">パッケージの削除</a></dt><dt>Yum を用いたパッケージのアンインストール, <a class="indexterm" href="sec-Removing.html">パッケージの削除</a></dt><dt>Yum を用いたパッケージの一覧表示</dt><dd><dl><dt>yum grouplist, <a class="indexterm" href="sec-Listing_Packages.html">パッケージの一覧</a></dt><dt>yum list all, <a class="indexterm" href="sec-Listing_Packages.html">パッケージの一覧</a></dt><dt>yum list installed, <a class="indexterm" href="sec-Listing_Packages.html">パッケージの一覧</a></dt><dt>yum repolist, <a class="indexterm" href="sec-Listing_Packages.html">パッケージの一覧</a></dt><dt>yu
m search, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</dt><dd><dl><dt>yum search, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">パッケージã®æ¤œç´¢</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージã®è¡¨ç¤º</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Displaying_Package_Information.html">ãƒ‘ãƒƒã‚±ãƒ¼ã‚¸æƒ…å ±ã®è¡¨ç¤º</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージ一覧</dt><dd><dl><dt> Glob 表記, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt></dl></dd><dt>カーãƒãƒ« RPM, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">カーãƒãƒ«ã‚’アップグレードã™ã‚‹</a></dt><dt>トランザクションãƒã‚°ã®è¡¨ç¤º, <a class="indexterm" href="sec-Viewing_the_Transaction_Log.html">トランザクションãƒã‚°ã®è¡¨ç¤º</a></dt><dt>パッケージã¨ãƒ
‘ッケージ グループ, <a class="indexterm" href="sec-Packages_and_Package_Groups.html">パッケージã¨ãƒ‘ッケージ グループ</a></dt><dt>パッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤, <a class="indexterm" href="sec-Installing_and_Removing_Package_Groups.html">パッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å‰Šé™¤</a></dt><dt>ä¾å˜æ€§, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">未解決ã®ä¾å˜æ€§</a></dt><dt>削除, <a class="indexterm" href="s2-rpm-uninstalling.html">アンインストール</a></dt><dt>ç¾åœ¨ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るパッケージã®æ›´æ–°</dt><dd><dl><dt>利用å¯èƒ½ãªæ›´æ–°, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">ソフトウェアã®æ›´æ–°ã‚’用ã„ãŸãƒ‘ッケージã®æ›´æ–°</a></dt></dl></dd></dl></dd><dt>パッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«</dt><dd><dl><dt>PackageKit を用ã„ãŸãƒ‘ッケ
ージグループのインストール, <a class="indexterm" href="sec-Installing_and_Removing_Package_Groups.html">パッケージグループのインストールおよび削除</a></dt></dl></dd><dt>パッケージグループの削除</dt><dd><dl><dt>PackageKit を用いたパッケージグループの削除, <a class="indexterm" href="sec-Installing_and_Removing_Package_Groups.html">パッケージグループのインストールおよび削除</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="sect-Preface-Feedback.html">フィードバック</a></dt></dl></dd><dt>プライマリネームサーバー (参照 BIND)</dt><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_Users_and_Groups.html">ユーザーとグループの管理</a></dt><dt>管理ツール</dt><dd><dl><dt>User Manager, <a class="indexterm" href="s1-users-tools.html">コマンドラインのツールを使う</a></dt><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="s1-users-groups-additional-resources.html">その他のリソース</a></dt><dd><dl><dt>インストールされているドキュメント, <a class="indexterm" href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">インストールされているドキュメント</a></dt></dl></dd></dl></dd><dt>ユーザー アカウント (参照 ユーザーの設定)</dt><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="s2-redhat-config-users-user-properties.html">ユーザーã®ãƒ—ãƒãƒ‘ティを変更ã™ã‚‹</a></dt><dt>フルãƒãƒ¼ãƒ ã®å¤‰æ›´, <a class="indexterm" href="s2-redhat-config-users-user-properties.html">ユーザーã®ãƒ—ãƒãƒ‘ティを変更ã™ã‚‹</a></dt><dt>ホームディレクトリã®å¤‰æ›´, <a class="indexterm" href="s2-redhat-config-users-user-properties.html">ユーザーã®ãƒ—ãƒãƒ‘ティを変更ã™ã‚‹</a></dt><dt>ユーザーã®ã‚°ãƒ«ãƒ¼ãƒ—ã®å¤‰æ›´, <a class="indexterm" href="s2-redhat-config-users-user-properties.html">ユーザーã®ãƒ—ãƒãƒ‘ティをå¤
‰æ›´ã™ã‚‹</a></dt><dt>ユーザーã®ä¿®æ£, <a class="indexterm" href="s2-redhat-config-users-user-properties.html">ユーザーã®ãƒ—ãƒãƒ‘ティを変更ã™ã‚‹</a></dt><dt>ユーザーã®å‰Šé™¤, <a class="indexterm" href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html">ユーザーã®å‰Šé™¤</a></dt><dt>ユーザーã®è¿½åŠ , <a class="indexterm" href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html">æ–°è¦ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’è¿½åŠ ã™ã‚‹</a>, <a class="indexterm" href="s2-redhat-config-users-user-new.html">æ–°è¦ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’è¿½åŠ ã™ã‚‹</a></dt><dt>ユーザー一覧ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼, <a class="indexterm" href="s1-users-configui.html#s2-redhat-config-users-list">ユーザーã¨ã‚°ãƒ«ãƒ¼ãƒ—を閲覧ã™ã‚‹</a></dt><dt>ユーザー一覧ã®è¡¨ç¤º, <a class="indexterm" href="sect-Managing_Users_and_Groups-User_Accounts.html">ユーザー アカウントã®ãƒ„ールを使ã†</a>, <a class="indexterm" href="s1-users-configui.html">ユーã‚
¶ãƒ¼ç®¡ç†ã®ãƒ„ールを使ã†</a></dt><dt>ãƒã‚°ã‚¤ãƒ³ã‚·ã‚§ãƒ«ã®å¤‰æ›´, <a class="indexterm" href="s2-redhat-config-users-user-properties.html">ユーザーã®ãƒ—ãƒãƒ‘ティを変更ã™ã‚‹</a></dt></dl></dd><dt>リソースレコード (å‚ç…§ BIND)</dt><dt>ルートãƒãƒ¼ãƒ サーãƒãƒ¼ (å‚ç…§ BIND)</dt><dt>ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«</dt><dd><dl><dt> rsyslogd デーモン , <a class="indexterm" href="ch-Viewing_and_Managing_Log_Files.html">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤ºãŠã‚ˆã³ç®¡ç†</a></dt><dt>ãƒãƒ¼ãƒ†ãƒ¼ã‚·ãƒ§ãƒ³, <a class="indexterm" href="s1-logfiles-locating.html">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’探ã™</a></dt><dt>監視, <a class="indexterm" href="s1-logfiles-examining.html">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’監視ã™ã‚‹</a></dt><dt>表示, <a class="indexterm" href="s1-logfiles-viewing.html">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º</a></dt><dt>説明, <a class="indexterm" href="ch-Viewing_and_Managing_Log_Files.html">ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤ºãŠã‚ˆã³ç®¡ç†</a></dt><dt>è¿½åŠ ãƒªã‚½ãƒ¼ã‚¹</dt><dd><dl><dt
>インストールされているドキュメント, <a class="indexterm" href="s1-log-files-additional-resources.html#s2-log-files-installed-docs">インストールされているドキュメント</a></dt><dt>有用なウェブサイト, <a class="indexterm" href="s2-log-files-useful-websites.html">役に立つ Web サイト</a></dt></dl></dd></dl></dd><dt> ログファイルビューアー </dt><dd><dl><dt>フィルター, <a class="indexterm" href="s1-logfiles-viewing.html">ログファイルの表示</a></dt><dt>更新間隔, <a class="indexterm" href="s1-logfiles-viewing.html">ログファイルの表示</a></dt><dt>検索, <a class="indexterm" href="s1-logfiles-viewing.html">ログファイルの表示</a></dt><dt>監視, <a class="indexterm" href="s1-logfiles-examining.html">ログファイルを監視する</a></dt></dl></dd><dt>再帰ネームサーバー (参照 BIND)</dt><dt>地域と言語</dt><dd><dl><dt>キーボードの設定, <a class="indexterm" href="se
ct-Configuring_the_Language_and_Keyboard-Layouts.html">ã‚ーボードã®ãƒ¬ã‚¤ã‚¢ã‚¦ãƒˆå¤‰æ›´</a></dt><dt>システム全体ã®è¨å®š, <a class="indexterm" href="sect-Configuring_the_Language_and_Keyboard-System.html">ç¾åœ¨ã®è¨å®šã®è¡¨ç¤º</a></dt><dt>日付ã€æ™‚刻ãŠã‚ˆã³æ•°å—ã®ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã®è¨å®š, <a class="indexterm" href="sect-Configuring_the_Language_and_Keyboard-Formats.html">日付ã€æ™‚刻ãŠã‚ˆã³æ•°å—ã®å½¢å¼ã®å¤‰æ›´</a></dt><dt>言語ã®è¨å®š, <a class="indexterm" href="ch-Configuring_the_Language_and_Keyboard.html#sect-Configuring_the_Language_and_Keyboard-Language">言語ã®å¤‰æ›´</a></dt></dl></dd><dt>完全修飾ドメインå, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-zones">ãƒãƒ¼ãƒ サーãƒãƒ¼ã‚¾ãƒ¼ãƒ³</a></dt><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-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">日付ã¨æ™‚刻ã®è¨å®šãƒ„ールã®ä½¿ã„æ–¹</a>, <a class="indexterm" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">日付ã®å¤‰æ›´æ–¹æ³•</a></dt><dd><dl><dt>(å‚ç…§ 日付ã¨æ™‚刻)</dt></dl></dd><dt>日付ã¨æ™‚刻</dt><dd><dl><dt>システム日付, <a class="indexterm" href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">日付ã¨æ™‚刻ã®è¨å®šãƒ„ールã®ä½¿ã„æ–¹</a></dt><dt>システム時刻, <a class="indexterm" href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">日付ã¨æ™‚刻ã®è¨å®šãƒ„ールã®ä½¿ã„æ–¹</a></dt><dt>タイムゾーンã®è¨å®š,
<a class="indexterm" href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">日付と時刻の設定ツールの使い方</a></dt></dl></dd><dt>時刻, <a class="indexterm" href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">日付と時刻の設定ツールの使い方</a>, <a class="indexterm" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">日付の変更方法</a></dt><dd><dl><dt>(参照 日付と時刻)</dt></dl></dd><dt>権威ネームサーバー (参照 BIND)</dt><dt>現在インストールされているパッケージの更新</dt><dd><dl><dt>利用可能な更新, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">ソフトウェアの更新を用いたパッケージの更新</a></dt></dl></dd><dt>自動化タスク, <a class="indexterm" href="ch-Autom
ating_System_Tasks.html">システムタスクの自動化</a></dt><dt>言語の設定 (参照 地域と言語)</dt><dt>設定ファイルの変更, <a class="indexterm" href="ch-yum.html#sec-Preserving_Configuration_File_Changes">設定ファイル変更の保存</a></dt><dt>認証</dt><dd><dl><dt> スマートカード認証の使用 , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">高度なオプション</a></dt><dt> 指紋サポートの使用 , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">高度なオプション</a></dt><dt> 認証の設定ツール , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">認証の設定ツール</a></dt></dl></dd><dt> 認証の設定ツール </dt><dd><dl><dt> および Kerberos 認証 , <a class="indexterm" href="ch-Configuring_Aut
hentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">識別と認証</a></dt><dt> および LDAP , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">識別と認証</a></dt><dt> および NIS , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">識別と認証</a></dt><dt> および NIS 認証 , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">識別と認証</a></dt><dt> および Winbind , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">識別と認証</a></dt><dt> および Winbind 認証 , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_an
d_Authentication">è˜åˆ¥ã¨èªè¨¼</a></dt></dl></dd><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>æ´å², <a class="indexterm" href="ch-Mail_Servers.html">メールサーãƒãƒ¼</a></dt><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>Access Control</dt><dd><dl><dt>configuring in SSSD, <a class="indexterm" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#idm68223072">Configuring Access Control</a></dt><dt>in SSSD, rules, <a class="indexterm" href="chap-SSSD_User_Guide-Setting_Up_SSS
D.html#idm51977120">The Simple Access Provider</a></dt></dl></dd><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>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>virtual host, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-virtualhosts">仮想ホストã®ã‚»ãƒƒãƒˆã‚¢ãƒƒãƒ—</a></dt><dt>ディレクティブ</dt><dd><dl><dt><Directory>, <a class="indexte
rm" 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-Web_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="indext
erm" 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-httpdconf-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="c
h-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></dt><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-directives">一般的㪠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="indexterm" 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-directives">一般的㪠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-httpdc
onf-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="indexterm" 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.htm
l#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>/var/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>バージョン 2.2</dt><dd><dl><dt>バージョン 2.0 からのアップグレード, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-migrating">設定の更新</a></dt><dt>変更点, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-c
hanges">注目すべき変更</a></dt><dt>特徴, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-features">新機能</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_asis, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-changes">注目ã™ã¹ã変更</a></dt><dt>mod_cache, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-features">新機能</a></dt><dt>mod_cern_meta, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-changes">注目ã™ã¹ã変更</a></dt><dt>mod_disk_cache, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-features">新機能</a></dt><dt>mod_ext_filter, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-changes">注目ã™ã¹ã変更</a></dt><dt>mod_proxy_balancer, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-version2-features">新機能</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">サービスã®çŠ¶æ…‹ç¢ºèª</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#s3-apache-resources-web">å½¹ã«ç«‹ã¤ Web サイト</a></dt></dl></dd><dt>è¿½åŠ ãƒªã‚½ãƒ¼ã‚¹</dt><dd>
<dl><dt>インストールされているドキュメント, <a class="indexterm" href="ch-Web_Servers.html#s3-apache-resources-installed">インストールされているドキュメント</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><dt> authconfig (参照 認証の設定ツール )</dt><dd><dl><dt> コマンド , <a class="indexterm" href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">コマンドライン版</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>Berkeley Internet Name Domain (参照 BIND)</dt><dt>BIND</dt><dd><dl><dt>zones</dt><dd><dl><dt>$INCLUDE ディレクティブ, <a class="indexterm" href="s2-bind-zone.html#s3-bind-zone-directives">一般的なディレクティブ</a></dt><dt>$ORIGIN ディレクティブ, <a class="indexterm" href="s2-bind-zone.html#s3-bind-zone-directives">一般的なディレクティブ</a></dt><dt>$TTL ディレクティブ, <a class="indexterm" href="s2-bind-zone.html#s3-bind-zone-directives">一般的なディレクティブ</a></dt><dt>A (Address) リソースレコード, <a class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource Records</a></dt><dt>CNAME (Canonical Name) リソースレコード, <a class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource Records</a></dt><dt>MX (Ma
il Exchange) リソースレコード, <a class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource Records</a></dt><dt>NS (Nameserver) リソースレコード, <a class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource Records</a></dt><dt>PTR (Pointer) リソースレコード, <a class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource Records</a></dt><dt>SOA (Start of Authority) リソースレコード, <a class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource Records</a></dt><dt>コメントタグ, <a class="indexterm" href="s2-bind-zone.html#s3-bind-zone-comm">コメントタグ</a></dt><dt>使用例, <a class="indexterm" href="s2-bind-zone.html#s4-bind-zone-examples-basic">簡単なゾーンファイル</a>, <a class="indexterm" href="s2-bind-zone.html#s3-bind-configuration-zone-reverse">逆引き名前解決ゾーンファイル</a></dt></dl></dd><dt>ゾーン</dt><dd><dl><dt>説明, <a class=
"indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-zones">ネームサーバーゾーン</a></dt></dl></dd><dt>ディレクトリ</dt><dd><dl><dt>/etc/named/, <a class="indexterm" href="s1-BIND.html#s2-bind-namedconf">named サービスの設定</a></dt><dt>/var/named/, <a class="indexterm" href="s2-bind-zone.html">ゾーンファイルの編集</a></dt><dt>/var/named/data/, <a class="indexterm" href="s2-bind-zone.html">ゾーンファイルの編集</a></dt><dt>/var/named/dynamic/, <a class="indexterm" href="s2-bind-zone.html">ゾーンファイルの編集</a></dt><dt>/var/named/slaves/, <a class="indexterm" href="s2-bind-zone.html">ゾーンファイルの編集</a></dt></dl></dd><dt>ファイル</dt><dd><dl><dt>/etc/named.conf, <a class="indexterm" href="s1-BIND.html#s2-bind-namedconf">named サービスの設定</a>, <a class="indexterm" href="s2-bind-rndc.html#s3-bind-rndc-configuration">ユーティリティの設定法</a></dt><dt>/etc/rndc.conf, <a class="ind
exterm" href="s2-bind-rndc.html#s3-bind-rndc-configuration">ユーティリティの設定法</a></dt><dt>/etc/rndc.key, <a class="indexterm" href="s2-bind-rndc.html#s3-bind-rndc-configuration">ユーティリティの設定法</a></dt></dl></dd><dt>ユーティリティ</dt><dd><dl><dt>dig, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-bind">ネームサーバーとしての BIND</a>, <a class="indexterm" href="s2-bind-dig.html">dig ユーティリティの使用</a>, <a class="indexterm" href="s2-bind-features.html#s3-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>named, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-bind">ネームサーバーとしての BIND</a>, <a class="indexterm" href="s1-BIND.html#s2-bind-namedconf">named サービスの設定</a></dt><dt>rndc, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-bind">ネームサーバーとしての BIND</a>, <a class="indexterm" href="s2
-bind-rndc.html">rndc ユーティリティの使用法</a></dt></dl></dd><dt>リソースレコード, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-zones">ネームサーバーゾーン</a></dt><dt>一般的な誤り, <a class="indexterm" href="s2-bind-mistakes.html">よくある間違いを避けるために</a></dt><dt>機能</dt><dd><dl><dt>Automatic Zone Transfer (AXFR), <a class="indexterm" href="s2-bind-features.html#s3-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>DNS Security Extensions (DNSSEC), <a class="indexterm" href="s2-bind-features.html#s3-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>Incremental Zone Transfer (IXFR), <a class="indexterm" href="s2-bind-features.html#s3-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>Internet Protocol version 6 (IPv6), <a class="indexterm" href="s2-bind-features.html#s3-bind-features-ipv6">インターネットプロトコル・バージョン 6
(IPv6: Internet Protocol version 6)</a></dt><dt>multiple views, <a class="indexterm" href="s2-bind-features.html#s3-bind-features-views">複数ビュー</a></dt><dt>Transaction SIGnature (TSIG), <a class="indexterm" href="s2-bind-features.html#s3-bind-features-tsig">Transaction SIGnatures (TSIG)</a></dt></dl></dd><dt>種別</dt><dd><dl><dt>セカンダリ（スレーブ）ネームサーバー, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-zones">ネームサーバーゾーン</a>, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">ネームサーバーのタイプ</a></dt><dt>プライマリ（マスター）ネームサーバー, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-zones">ネームサーバーゾーン</a>, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">ネームサーバーのタイプ</a></dt><dt>再帰ネームサーバー, <a class="indexterm" href="ch-DNS_
Servers.html#s2-dns-introduction-nameservers">ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚¤ãƒ—</a></dt><dt>権å¨ãƒãƒ¼ãƒ サーãƒãƒ¼, <a class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">ãƒãƒ¼ãƒ サーãƒãƒ¼ã®ã‚¿ã‚¤ãƒ—</a></dt></dl></dd><dt>è¨å®š</dt><dd><dl><dt>acl ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state">一般的ãªã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®ã‚¿ã‚¤ãƒ—</a></dt><dt>controls ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>include ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state">一般的ãªã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®ã‚¿ã‚¤ãƒ—</a></dt><dt>key ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>logging ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ã
ƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>options ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state">一般的ãªã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®ã‚¿ã‚¤ãƒ—</a></dt><dt>server ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>trusted-keys ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>view ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state-other">ä»–ã®ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆå½¢å¼</a></dt><dt>zone ステートメント, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-state">一般的ãªã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®ã‚¿ã‚¤ãƒ—</a></dt><dt>コメントタグ, <a class="indexterm" href="s1-BIND.html#s3-bind-namedconf-comm">コメントタグ</a></dt></dl></dd><dt>è¿½åŠ ã®ãƒªã‚½ãƒ¼ã‚¹</dt><dd><dl><dt>インストールã•ã‚Œã¦ã„るドã‚ã
ƒ¥ãƒ¡ãƒ³ãƒˆ, <a class="indexterm" href="s2-bind-additional-resources.html#s3-bind-installed-docs">インストールã•ã‚Œã¦ã„るドã‚ュメント</a></dt><dt>有用ãªã‚¦ã‚§ãƒ–サイト, <a class="indexterm" href="s2-bind-additional-resources.html#s3-bind-useful-websites">å½¹ã«ç«‹ã¤ Web サイト</a></dt><dt>関連書ç±, <a class="indexterm" href="s2-bind-additional-resources.html#s3-bind-related-books">関連書ç±</a></dt></dl></dd></dl></dd><dt>blkid, <a class="indexterm" href="s2-sysinfo-filesystems-blkid.html">Using the blkid Command</a></dt><dt>block devices, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt><dd><dl><dt>(å‚ç…§ /proc/devices )</dt><dt>definition of, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt></dl></dd><dt>bonding (å‚ç…§ channel bonding)</dt><dt>boot loader</dt><dd><dl><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>全体オプション, <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>channel bonding</dt><dd><dl><dt>configuration, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dt>description, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>c
hannel bonding interface (参照 kernel module)</dt><dt>character devices, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt><dd><dl><dt>(参照 /proc/devices )</dt><dt>definition of, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt></dl></dd><dt>CPU usage, <a class="indexterm" href="s1-sysinfo-cpu.html">Viewing CPU Usage</a></dt><dt>crash</dt><dd><dl><dt>analyzing the dump</dt><dd><dl><dt>message buffer, <a class="indexterm" href="s2-kdump-crash-log.html">Displaying the Message Buffer</a></dt><dt>open files, <a class="indexterm" href="s2-kdump-crash-files.html">Displaying Open Files</a></dt><dt>processes, <a class="indexterm" href="s2-kdump-crash-processes.html">Displaying a Process Status</a></dt><dt>stack trace, <a class="indexterm" href="s2-kdump-crash-backtrace.html">Displaying a Backtrace</a></dt><dt>virtual memory, <a class="indexterm" href="s2-kdump-crash-memory.html">Displaying Virtual Memory Information</a></dt></dl><
/dd><dt>opening the dump image, <a class="indexterm" href="s1-kdump-crash.html#s2-kdump-crash-running">Running the crash Utility</a></dt><dt>system requirements, <a class="indexterm" href="s1-kdump-crash.html">Analyzing the Core Dump</a></dt></dl></dd><dt>Cron, <a class="indexterm" href="ch-Automating_System_Tasks.html">システムタスクの自動化</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>deleting cache files</dt><dd><dl><dt>in SSSD, <a class="indexterm" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html#sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">Support for Multiple Domains</a></dt></dl></dd><dt>Denial of Service attack, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-net"> /proc/sys/net/ </a></dt><dd><dl><dt>(参照 /proc/sys/net/ directory)</dt><dt>definition of, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-net"> /proc/sys/net/ </a></dt></dl></dd><dt>desktop environments (参照 X)</dt><dt>df, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>DHCP, <a class="indexterm" href="ch-DHCP_Servers.html">DHCP サーバー</a></dt><dd><dl><dt>dhcpd.conf, <a class="indexterm" href="s1-dhcp-configuring-server.html#c
onfig-file">設定ファイル</a></dt><dt> dhcpd.leases , <a class="indexterm" href="ch11s02s03.html">サーバーの起動と停止</a></dt><dt>dhcpd6.conf, <a class="indexterm" href="s1-dhcp_for_ipv6_dhcpv6.html">IPv6 向け DHCP (DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm" href="s1-dhcp_for_ipv6_dhcpv6.html">IPv6 向け DHCP (DHCPv6)</a></dt><dt> dhcrelay , <a class="indexterm" href="dhcp-relay-agent.html">DHCP リレーエージェント</a></dt><dt>group, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">設定ファイル</a></dt><dt> shared-network , <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">設定ファイル</a></dt><dt>subnet, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">設定ファイル</a></dt><dt>オプション, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">設定ファイル</a></dt><dt>クライアント設定, <a class="indexterm" href="s1-dhcp-co
nfiguring-client.html">DHCP クライアントの設定</a></dt><dt>コマンドラインオプション, <a class="indexterm" href="ch11s02s03.html">サーバーの起動と停止</a></dt><dt>サーバーの停止方法, <a class="indexterm" href="ch11s02s03.html">サーバーの起動と停止</a></dt><dt>サーバーの開始方法, <a class="indexterm" href="ch11s02s03.html">サーバーの起動と停止</a></dt><dt>サーバー設定, <a class="indexterm" href="s1-dhcp-configuring-server.html">DHCP サーバーの設定</a></dt><dt>リレーエージェント, <a class="indexterm" href="dhcp-relay-agent.html">DHCP リレーエージェント</a></dt><dt>使用する理由, <a class="indexterm" href="ch-DHCP_Servers.html#s1-dhcp-why">DHCP を使用する理由</a></dt><dt>全体パラメーター, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">設定ファイル</a></dt><dt>接続, <a class="indexterm" href="s1-dhcp-configuring-client.html">DHCP
クライアントの設定</a></dt><dt>追加のリソース, <a class="indexterm" href="s1-dhcp-additional-resources.html">その他のリソース</a></dt></dl></dd><dt>dhcpd.conf, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">設定ファイル</a></dt><dt>dhcpd.leases, <a class="indexterm" href="ch11s02s03.html">サーバーの起動と停止</a></dt><dt> dhcrelay , <a class="indexterm" href="dhcp-relay-agent.html">DHCP リレーエージェント</a></dt><dt>dig (参照 BIND)</dt><dt>DNS</dt><dd><dl><dt>定義, <a class="indexterm" href="ch-DNS_Servers.html">DNS サーバー</a></dt><dd><dl><dt>(参照 BIND)</dt></dl></dd></dl></dd><dt>documentation</dt><dd><dl><dt>finding installed, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt></dl></dd><dt>DoS attack (参照 Denial of Service attack)</dt><dt>drivers (参照 kernel module)</dt><dt>DSA キー</dt><dd><dl><dt>生成, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">éµãƒšã‚¢ã®ç”Ÿæˆ</a></dt></dl></dd><dt>du, <a class="indexterm" href="s2-sysinfo-filesystems-du.html">Using the du Command</a></dt><dt>Dynamic Host Configuration Protocol (å‚ç…§ DHCP)</dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>email</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>useful websites, <a class="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><dt>epoch, <a class="indexterm" href="s2-proc-stat.html"> /proc/stat </a></dt><dd><dl><dt>(å‚ç…§ /proc/stat )</dt><dt>definition of, <a class="indexterm" href="s2-proc-stat.html"> /proc/stat </a></dt></dl></dd><dt> exec-shield </dt><dd><dl><dt>enabling, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt>introducing, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt></dl></dd><dt>execution domains, <a class="indexterm" href="s2-proc-execdomains.html"> /proc/execdomains </a></dt><dd><dl><dt>(å‚ç…§ /proc/execdomains )</dt><dt>definition of, <a class="indexterm" href="s2-proc-execdomains.html"> /proc/execdomains </a></dt></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-rpm-using.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>special, <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-configuration-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>file system</dt><dd><dl><dt>virtual (å‚ç…§ proc file system)</dt></dl></dd><dt>files, proc file system</dt><dd><dl><dt>changing, <a class="indexterm" href="ch-proc.html#s2-proc-change">Changing Virtual Files</a>, <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt><dt>viewing, <a class="indexterm" href="ch-proc.html#s2-proc-viewing">Viewing Virtual Files</a>, <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</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>FQDN (参照 完全修飾ドメイン名)</dt><dt>frame buffer device, <a class="indexterm" href="s2-proc-fb.html"> /proc/fb </a></dt><dd><dl><dt>(参照 /proc/fb )</dt></dl></dd><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 Conten
t 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></dd></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>GNOME, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">デスクトップ環境</a></dt><dd><dl
><dt>(参照 X)</dt></dl></dd><dt> gnome-system-log (参照 Log File Viewer )</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">パッケージの署名を確認する</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-lo
ader.html#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>HTTP サーãƒãƒ¼ (å‚ç…§ Apache HTTP Server)</dt><dt>httpd (å‚ç…§ Apache HTTP Server)</dt><dt>hugepages</dt><dd><dl><dt>configuration of, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-vm"> /proc/sys/vm/ </a></dt></dl></dd></dl></div><div class="indexdiv"><h3>I</h3><dl><dt> ifdown , <a class="indexterm" href="s1-networkscripts-control.html">インターフェース制御スクリプト</a></dt><dt> ifup , <a class="indexterm" href="s1-networkscripts-control.html">インターフェース制御スクリプト</a></dt><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-rpm-using.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>KDE, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">デスクトップ環境</a></dt><dd><dl><dt>(å‚ç…§ X)</dt></dl></dd><dt>kdump</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documents, <a class="indexterm" href="s1-kdump-resources.html#s2-kdump-resources-installed">インストールã•ã‚Œã¦ã„るドã‚ュメント</a></dt><dt>manual pages, <a class="indexterm" href="s1-kdump-resources.html#s2-kdump-resources-installed">インストールã•ã‚Œã¦ã„るドã‚ュメント</a></dt><dt>websites, <a class="ind
exterm" href="s2-kdump-resources-online.html">役に立つ Web サイト</a></dt></dl></dd><dt>analyzing the dump (参照 crash)</dt><dt>configuring the service</dt><dd><dl><dt>default action, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-action">Changing the Default Action</a></dt><dt>dump image compression, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-filtering">Configuring the Core Collector</a></dt><dt>filtering level, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-filtering">The Filtering Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-filtering">Configuri
ng the Core Collector</a></dt><dt>initial RAM disk, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>kernel image, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>kernel options, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>memory usage, <a class="indexterm" href="s1-kdump-configuration.html#s3-kdump-configuration-firstboot-memory">Configuring the Memory
Usage</a>, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-basic">The Basic Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>supported targets, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-target">The Target Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-target">Configuring the Target Type</a></dt><dt>target location, <a class="indexterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-target">The Target Settings Tab</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-target">Configuring the Target Type</a></dt></dl></dd><dt>enabling the service, <a class="indexterm" href="s1-kdump-configuration.html#s3-kdump-configuration-firstboot-enable">サービスの有効化</a>, <a class="inde
xterm" href="s2-kdump-configuration-gui.html#s3-kdump-configuration-gui-enable">サービスの有効化</a>, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-enable">サービスの有効化</a></dt><dt>installing, <a class="indexterm" href="ch-kdump.html#s1-kdump-installation">Installing the kdump Service</a></dt><dt>running the service, <a class="indexterm" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-enable">サービスの有効化</a></dt><dt>system requirements, <a class="indexterm" href="s1-kdump-configuration.html">Configuring the kdump Service</a></dt><dt>testing the configuration, <a class="indexterm" href="s2-kdump-configuration-testing.html">Testing the Configuration</a></dt></dl></dd><dt>kernel</dt><dd><dl><dt>downloading, <a class="indexterm" href="s1-kernel-download.html">アップグレードされたカーネルをダウンロードする</a></dt><dt>performing kernel upgrade, <a class="indexterm" hre
f="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 Dump Configuration (参照 kdump)</dt><dt>kernel module</dt><dd><dl><dt>bonding module, <a class="indexterm" href="sec-Using_Channel_Bonding.h
tml">Using Channel Bonding</a></dt><dd><dl><dt>description, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><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/sysconfig/modules/ , <a class="indexterm" href="sec-Persistent_Module_Loading.html">Persistent Module Loading</a></dt><dt> /lib/modules/kernel_version/kernel/drivers/ , <a class="indexterm" href="sec-Loading_a_Module.html">モジュールの読み込み方法</a></dt></dl></dd><dt>Ethernet module</dt><dd><dl><dt>supporting multiple cards, <a class="indexterm" href="sec-Specific_Kernel_Module_Capabilities.html#sec-Using_Multiple_Ethernet_Cards">複数のイーサネットカードの使用</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>bonding module parameters, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Modu
le Directives</a></dt><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>ke
rnel package</dt><dd><dl><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-doc</dt><dd><dl><dt>documentation files, <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> kwin , <a class="indexterm" href="s2-x-clients-winmanagers.html">ウィンドウマネージャ</a></dt><dd><dl><dt>(参照 X)</dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LDAP (参照 OpenLDAP)</dt><dt>log files, <a class="indexterm" href="ch-Viewing_and_Managing_Log_Files.html">ログファイルの表示および管理</a></dt><dd><dl><dt>(参照 ログビューアー )</dt><dt>locating, <a class="indexterm" href="s1-logfiles-locating.html">ログファイルを探す</a></dt></dl></dd><dt> logrotate , <a class="indexterm" href="s1-logfiles-locating.html">ログファイルを探す</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-ls
cpu.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>, <a class="indexterm" href="s2-proc-pci.html"> /proc/bus/pci </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> metacity , <a class="indexterm" href="s2-x-clients-winmanagers.html">ウィンドウマネージャ<
/a></dt><dd><dl><dt>(参照 X)</dt></dl></dd><dt> modinfo , <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 Age
nt (MTA) の設定</a> (参照 メール ユーザー エージェント)</dt><dt>Multihomed DHCP</dt><dd><dl><dt>server configuration, <a class="indexterm" href="sect-Configuring_a_Multihomed_DHCP_Server.html">Configuring a Multihomed DHCP Server</a></dt><dt>ホストの設定, <a class="indexterm" href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configuration">ホストの設定</a></dt></dl></dd><dt>multiple domains</dt><dd><dl><dt>specifying in SSSD, <a class="indexterm" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html#sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">Support for Multiple Domains</a></dt></dl></dd><dt> mwm , <a class="indexterm" href="s2-x-clients-winmanagers.html">ウィンドウマネージャ</a></dt><dd><dl><dt>(参照 X)</dt></dl></dd></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>named (参照 BIND)</dt><dt> net program, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba
ディストリビューションプログラム</a></dt><dt>network</dt><dd><dl><dt>bridge</dt><dd><dl><dt>bridging, <a class="indexterm" href="s2-networkscripts-interfaces_network-bridge.html">ネットワークブリッジ</a></dt></dl></dd><dt>interfaces</dt><dd><dl><dt>802.1q, <a class="indexterm" href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html">Setting up 802.1q VLAN tagging</a></dt><dt>VLAN, <a class="indexterm" href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html">Setting up 802.1q VLAN tagging</a></dt></dl></dd></dl></dd><dt>Network Time Protocol, <a class="indexterm" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol の設定</a></dt><dd><dl><dt>ntpd, <a class="indexterm" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol の設定</a></dt><dt>ntpdate, <a class="indexterm" href="sect-Configuring_the_Date_and_Time
-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol の設定</a></dt></dl></dd><dt>NIC</dt><dd><dl><dt>binding into single channel, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt></dl></dd><dt> nmblookup program, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba ディストリビューションプログラム</a></dt><dt>NTP (参照 Network Time Protocol)</dt><dt>ntpd, <a class="indexterm" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol の設定</a></dt><dt>ntpdate, <a class="indexterm" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol の設定</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>インストール, <a class="inde
xterm" 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-Directory_Servers.html#s3-ldap-confi
guration-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="indexterm" 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 class="indexterm" href="ch-Director
y_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</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-restarting">サービスの再起動方法</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">サービスの状態の確認方法</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="indexterm" href="ch-Directory_Servers.html#s3-ldap-configuration-global">全体設定の変更方法</a></dt><dt>概要, <a class="indexterm" href="ch-Direct
ory_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>DSA キー</dt><dd><dl><dt>生成, <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>RSA バージョン 1 キー</dt><dd><dl><dt>生成, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">鍵ペアの生成
</a></dt></dl></dd><dt> ssh-add , <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">ssh-agent の設定</a></dt><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>DSA, <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><dt>RSA バージョン 1, <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">キー認証の使用</a></dt><dt>クライアント, <a class="indexterm" href="s1-ssh-clients.html">OpenSSH クライ
アント</a></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>サーバー, <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 /dev/oprofile/ </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</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">Specifying 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</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</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</a></dt><dd><dl><dt>log file, <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile</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</a></dt><dt>starting, <a
class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile</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>PackageKit, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dd><dl><dt>PolicyKit</dt><dd><dl><dt>認証, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Pa
ckages_with_Software_Update">ソフトウェアの更新を用いたパッケージの更新</a></dt></dl></dd><dt>アーキテクチャー, <a class="indexterm" href="sec-PackageKit_Architecture.html">PackageKit アーキテクチャー</a></dt><dt>トランザクションログの表示, <a class="indexterm" href="sec-Viewing_the_Transaction_Log.html">トランザクションログの表示</a></dt><dt>パッケージの, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>パッケージのアンインストール, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>パッケージの更新, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>パッケージの管理, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>パッケージの表示, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>パッケージグループのインストールおよび削除, <a class="indexterm" hre
f="sec-Installing_and_Removing_Package_Groups.html">パッケージグループのインストールおよび削除</a></dt><dt>追加と削除, <a class="indexterm" href="sec-Using_Add_Remove_Software.html">ソフトウェアの追加/削除の使用</a></dt></dl></dd><dt>PackageKit を用いたパッケージの更新</dt><dd><dl><dt>PolicyKit, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">ソフトウェアの更新を用いたパッケージの更新</a></dt></dl></dd><dt>packages</dt><dd><dl><dt>determining file ownership with, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>finding deleted files from, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>iFedora installation media, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">RPM パッケージの検索</a></dt><dt>initial RPM repositories, <a class="
indexterm" href="s1-rpm-using.html#s2-rpm-finding">RPM パッケージの検索</a></dt><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-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-doc</dt><dd><dl><dt>documentation files, <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_Up
grading_the_Kernel.html#s1-kernel-packages">カーネルパッケージの概要</a></dt></dl></dd><dt>locating documentation for, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>obtaining list of files, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</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-impressing.html">Practical and 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="sec-Installing_and_Upgrading.html#s3-rpm-errors">すでにインストールされているパッケージ</a></dt><dt>conflict, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-
conflicting-files">ファイルの競合</a></dt><dt>failed dependencies, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">未解決の依存性</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-rpm-querying.html">問い合わせ</a></dt><dt>source and binary packages, <a class="indexterm" href="ch-RPM.html">RPM</a></dt></dl></dd><dt>Yum instead of RPM, <a class="indexterm" href="ch-RPM.html">RPM</a></dt><dt>Yum を用いたパッケージのアンインストール</dt><dd><dl><dt>yum remove package_name, <a class="indexterm" href="sec-Removing.html">パッケージの削除</a></dt></dl></dd><dt>Yum を用いたパッケージの一覧表示</dt><dd><dl><dt>yum list available, <a class="indexterm" href="sec-Listing_Packages.html">パッケージの一覧</a></dt></dl></dd><dt>パッケージの表示</dt><dd><dl><dt>yum info, <
a class="indexterm" href="sec-Displaying_Package_Information.html">パッケージ情報の表示</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>PolicyKit, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">ソフトウェアの更新を用いたパッケージの更新</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#idm42798032">The Settings Page</a></dt><dt>Sharing Printers, <a class="indexterm" href="s1-printing-edit.html#sec-Sharing_Print
ers">Sharing Printers</a></dt></dl></dd><dt>printers (参照 Printer Configuration)</dt><dt> proc file system</dt><dd><dl><dt> /proc/buddyinfo , <a class="indexterm" href="s1-proc-topfiles.html#s2-proc-buddyinfo"> /proc/buddyinfo </a></dt><dt> /proc/bus/ directory, <a class="indexterm" href="s2-proc-dir-bus.html"> /proc/bus/ </a></dt><dt> /proc/bus/pci </dt><dd><dl><dt>viewing using lspci , <a class="indexterm" href="s2-proc-pci.html"> /proc/bus/pci </a></dt></dl></dd><dt> /proc/cmdline , <a class="indexterm" href="s2-proc-cmdline.html"> /proc/cmdline </a></dt><dt> /proc/cpuinfo , <a class="indexterm" href="s2-proc-cpuinfo.html"> /proc/cpuinfo </a></dt><dt> /proc/crypto , <a class="indexterm" href="s2-proc-crypto.html"> /proc/crypto </a></dt><dt> /proc/devices </dt><dd><dl><dt>block devices, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt><dt>character devices, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt></dl></dd><dt> /p
roc/dma , <a class="indexterm" href="s2-proc-dma.html"> /proc/dma </a></dt><dt> /proc/driver/ directory, <a class="indexterm" href="s2-proc-dir-driver.html"> /proc/driver/ </a></dt><dt> /proc/execdomains , <a class="indexterm" href="s2-proc-execdomains.html"> /proc/execdomains </a></dt><dt> /proc/fb , <a class="indexterm" href="s2-proc-fb.html"> /proc/fb </a></dt><dt> /proc/filesystems , <a class="indexterm" href="s2-proc-filesystems.html"> /proc/filesystems </a></dt><dt> /proc/fs/ directory, <a class="indexterm" href="s2-proc-dir-fs.html"> /proc/fs </a></dt><dt> /proc/interrupts , <a class="indexterm" href="s2-proc-interrupts.html"> /proc/interrupts </a></dt><dt> /proc/iomem , <a class="indexterm" href="s2-proc-iomem.html"> /proc/iomem </a></dt><dt> /proc/ioports , <a class="indexterm" href="s2-proc-ioports.html"> /proc/ioports </a></dt><dt> /proc/irq/ directory, <a class="indexterm" href="s2-proc-dir-irq.html"> /proc/irq/ </a></dt><dt> /proc/kcore , <a class="indexterm" hr
ef="s2-proc-kcore.html"> /proc/kcore </a></dt><dt> /proc/kmsg , <a class="indexterm" href="s2-proc-kmsg.html"> /proc/kmsg </a></dt><dt> /proc/loadavg , <a class="indexterm" href="s2-proc-loadavg.html"> /proc/loadavg </a></dt><dt> /proc/locks , <a class="indexterm" href="s2-proc-locks.html"> /proc/locks </a></dt><dt> /proc/mdstat , <a class="indexterm" href="s2-proc-mdstat.html"> /proc/mdstat </a></dt><dt> /proc/meminfo , <a class="indexterm" href="s2-proc-meminfo.html"> /proc/meminfo </a></dt><dt> /proc/misc , <a class="indexterm" href="s2-proc-misc.html"> /proc/misc </a></dt><dt> /proc/modules , <a class="indexterm" href="s2-proc-modules.html"> /proc/modules </a></dt><dt> /proc/mounts , <a class="indexterm" href="s2-proc-mounts.html"> /proc/mounts </a></dt><dt> /proc/mtrr , <a class="indexterm" href="s2-proc-mtrr.html"> /proc/mtrr </a></dt><dt> /proc/net/ directory, <a class="indexterm" href="s2-proc-dir-net.html"> /proc/net/ </a></dt><dt> /proc/partitions , <a class="index
term" href="s2-proc-partitions.html"> /proc/partitions </a></dt><dt> /proc/PID/ directory, <a class="indexterm" href="s2-proc-pid.html"> /proc/PID/ </a></dt><dt> /proc/scsi/ directory, <a class="indexterm" href="s2-proc-dir-scsi.html"> /proc/scsi/ </a></dt><dt> /proc/self/ directory, <a class="indexterm" href="s1-proc-directories.html#s3-proc-self"> /proc/self/ </a></dt><dt> /proc/slabinfo , <a class="indexterm" href="s2-proc-slabinfo.html"> /proc/slabinfo </a></dt><dt> /proc/stat , <a class="indexterm" href="s2-proc-stat.html"> /proc/stat </a></dt><dt> /proc/swaps , <a class="indexterm" href="s2-proc-swaps.html"> /proc/swaps </a></dt><dt> /proc/sys/ directory, <a class="indexterm" href="s2-proc-dir-sys.html"> /proc/sys/ </a>, <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt><dd><dl><dt>(参照 sysctl )</dt><dt> /proc/sys/dev/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-dev"> /proc/sys/dev/ </a></dt><dt> /proc/sys/f
s/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-fs"> /proc/sys/fs/ </a></dt><dt> /proc/sys/kernel/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt> /proc/sys/kernel/exec-shield , <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt>/proc/sys/kernel/sysrq (参照 system request key)</dt><dt> /proc/sys/net/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-net"> /proc/sys/net/ </a></dt><dt> /proc/sys/vm/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-vm"> /proc/sys/vm/ </a></dt></dl></dd><dt> /proc/sysrq-trigger , <a class="indexterm" href="s2-proc-sysrq-trigger.html"> /proc/sysrq-trigger </a></dt><dt> /proc/sysvipc/ directory, <a class="indexterm" href="s2-proc-dir-sysvipc.html"> /proc/sysvipc/ </a></dt><dt> /proc/tty/ directory, <a class="indexterm" href="s2-proc-tty.html"> /proc/tty/ </a></dt><dt
> /proc/uptime , <a class="indexterm" href="s2-proc-uptime.html"> /proc/uptime </a></dt><dt> /proc/version , <a class="indexterm" href="s2-proc-version.html"> /proc/version </a></dt><dt>additional resources, <a class="indexterm" href="s1-proc-additional-resources.html">参考文献</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-proc-additional-resources.html#s2-proc-installed-documentation">インストールされているドキュメント</a></dt><dt>useful websites, <a class="indexterm" href="s1-proc-additional-resources.html#s2-proc-useful-websites">役に立つ Web サイト</a></dt></dl></dd><dt>changing files within, <a class="indexterm" href="ch-proc.html#s2-proc-change">Changing Virtual Files</a>, <a class="indexterm" href="s2-proc-dir-sys.html"> /proc/sys/ </a>, <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt><dt>files within, top-level, <a class="indexterm" href="s1-proc-topfiles.html">Top-level Files w
ithin the proc File System</a></dt><dt>introduced, <a class="indexterm" href="ch-proc.html">The proc File System</a></dt><dt>process directories, <a class="indexterm" href="s1-proc-directories.html#s2-proc-processdirs">Process Directories</a></dt><dt>subdirectories within, <a class="indexterm" href="s1-proc-directories.html">Directories within /proc/</a></dt><dt>viewing files within, <a class="indexterm" href="ch-proc.html#s2-proc-viewing">Viewing Virtual Files</a></dt></dl></dd><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-ema
il-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>rndc (参照 BIND)</dt><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 instal
led, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-errors">すでにインストールされているパッケージ</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">パッケージの署名を確認する</a></dt><dt>configuration file changes</dt><dd><dl><dt>conf.rpmsave, <a class="indexterm" href="sec-Configuration_File_Changes.html">設定ファイルの変更</a></dt></dl></dd><dt>conflicts, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-conflicting-files">ファイルの競合</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-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>failed dependencies, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">未解決の依存性</a></dt><dt>file name, <a class="indexterm" href="sec-Installing_and_Upgrading.html">インストールとアップグレード</a></dt><dt>finding deleted files with, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>GnuPG, <a class="indexterm" href="s1-check-rpm-sig.html">パッケージの署名を確認する</a></dt><dt>md5sum, <a class="indexterm" href="s1-check-rpm-sig.html">パッケージの署名を確認する</a></dt><dt>querying, <a class="indexterm" href="s2-rpm-querying.html">問い合わせ</a></dt><dt>querying uninstalled packages, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Commo
n Examples of RPM Usage</a></dt><dt>RPM パッケージã®æ¤œç´¢, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">RPM パッケージã®æ¤œç´¢</a></dt><dt>アップグレード, <a class="indexterm" href="sec-Installing_and_Upgrading.html">インストールã¨ã‚¢ãƒƒãƒ—グレード</a></dt><dt>アンインストール, <a class="indexterm" href="s2-rpm-uninstalling.html">アンインストール</a></dt><dt>インストール, <a class="indexterm" href="sec-Installing_and_Upgrading.html">インストールã¨ã‚¢ãƒƒãƒ—グレード</a></dt><dt>インストール済ã¿ã®ã‚¢ãƒƒãƒ—グレードã®å®Ÿè¡Œ, <a class="indexterm" href="s2-rpm-freshening.html">インストール済ã¿ã®ã‚¢ãƒƒãƒ—グレードã®å®Ÿè¡Œ</a></dt><dt>ウェブサイト, <a class="indexterm" href="s2-rpm-useful-websites.html">å½¹ã«ç«‹ã¤ Web サイト</a></dt><dt>ティップス, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>ドã‚ュã
ƒ¡ãƒ³ãƒˆ, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>ファイルã®ç«¶åˆ</dt><dd><dl><dt>解決, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-conflicting-files">ファイルã®ç«¶åˆ</a></dt></dl></dd><dt>ファイル一覧ã®å•ã„åˆã‚ã›, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>ä¾å˜æ€§, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">未解決ã®ä¾å˜æ€§</a></dt><dt>書ç±ã«ã¤ã„ã¦, <a class="indexterm" href="s2-rpm-related-books.html">関連書ç±</a></dt><dt>検証, <a class="indexterm" href="s2-rpm-verifying.html">検証</a></dt><dt>è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®å¤‰æ›´, <a class="indexterm" href="sec-Configuration_File_Changes.html">è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®å¤‰æ›´</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>RSA ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 1 ã‚ー</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="inde
xterm" 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_Pr
int_Servers.html#s2-samba-account-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="indexterm" 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-File_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>St
and 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-File_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">Samb
a サーバーの設定</a>, <a class="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 (参照 O
penSSH)</dt><dt>slab pools (å‚ç…§ /proc/slabinfo )</dt><dt>slapd (å‚ç…§ OpenLDAP)</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 class="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-requir
ing.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-add , <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">ssh-agent の設定</a></dt><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_Ser
vers.html#s2-apache-mod_ssl">SSL サーバーのセットアップ</a></dt><dd><dl><dt>(参照 Apache HTTP Server)</dt></dl></dd><dt>SSL サーバー (参照 Apache HTTP Server)</dt><dt>SSSD</dt><dd><dl><dt>Configuring a Microsoft Active Directory Domain for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">Configuring a Microsoft Active Directory Domain</a></dt><dt>Configuring a proxy domain for, <a class="indexterm" href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html">Configuring a Proxy Domain</a></dt><dt>Configuring an LDAP domain for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt><dt>Selecting an LDAP schema for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sec
t-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt><dt>Setting Up Kerberos authentication for, <a class="indexterm" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">Setting Up Kerberos Authentication</a></dt><dt>Specifying timeout values for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt></dl></dd><dt> stunnel , <a class="indexterm" href="s1-email-mua.html#s3-email-security-servers">安全な電子クライアント通信</a></dt><dt> sysconfig directory</dt><dd><dl><dt> /etc/sysconfig/apm-scripts/ directory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/arpwatch , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-arpwatch"> /etc/sysconfig
/arpwatch </a></dt><dt> /etc/sysconfig/authconfig , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-authconfig"> /etc/sysconfig/authconfig </a></dt><dt> /etc/sysconfig/autofs , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-autofs"> /etc/sysconfig/autofs </a></dt><dt> /etc/sysconfig/cbq/ directory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/clock , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-clock"> /etc/sysconfig/clock </a></dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-dhcpd"> /etc/sysconfig/dhcpd </a></dt><dt> /etc/sysconfig/firstboot , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-firewall"> /etc/sysconfig/firstboot </a></dt><dt> /etc/sysconfig/init , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-in
it"> /etc/sysconfig/init </a></dt><dt> /etc/sysconfig/ip6tables-config , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-ip6tables"> /etc/sysconfig/ip6tables-config </a></dt><dt> /etc/sysconfig/keyboard , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-kybd"> /etc/sysconfig/keyboard </a></dt><dt> /etc/sysconfig/ldap , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-ldap"> /etc/sysconfig/ldap </a></dt><dt> /etc/sysconfig/named , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-named"> /etc/sysconfig/named </a></dt><dt> /etc/sysconfig/network , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-network">/etc/sysconfig/network</a></dt><dt> /etc/sysconfig/network-scripts/ directory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dd><dl><dt>(参照 network)</dt></dl></dd><dt> /etc/sysconfig/networki
ng/ directory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/ntpd , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-ntpd"> /etc/sysconfig/ntpd </a></dt><dt> /etc/sysconfig/quagga , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-quagga"> /etc/sysconfig/quagga </a></dt><dt> /etc/sysconfig/radvd , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-radvd"> /etc/sysconfig/radvd </a></dt><dt> /etc/sysconfig/samba , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-samba"> /etc/sysconfig/samba </a></dt><dt> /etc/sysconfig/selinux , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-selinux"> /etc/sysconfig/selinux </a></dt><dt> /etc/sysconfig/sendmail , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-sendmail"> /etc/sysconfig/sendmail </a></dt><dt> /etc/sysconf
ig/spamassassin , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-spamd"> /etc/sysconfig/spamassassin </a></dt><dt> /etc/sysconfig/squid , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-squid"> /etc/sysconfig/squid </a></dt><dt> /etc/sysconfig/system-config-users , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-rcu"> /etc/sysconfig/system-config-users </a></dt><dt> /etc/sysconfig/vncservers , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-vncservers"> /etc/sysconfig/vncservers </a></dt><dt> /etc/sysconfig/xinetd , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-xinetd"> /etc/sysconfig/xinetd </a></dt><dt>additional resources, <a class="indexterm" href="s1-sysconfig-additional-resources.html">その他のリソース</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-sysconfig-additional-resources.html#s2-sysconfig-installed-docume
ntation">インストールされているドキュメント</a></dt></dl></dd><dt>directories in, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt></dl></dd><dt>sysconfig ディレクトリー</dt><dd><dl><dt> /etc/sysconfig/network-scripts/ ディレクトリー, <a class="indexterm" href="ch-Network_Interfaces.html">ネットワーク・インターフェース</a></dt><dt>含まれるファイル, <a class="indexterm" href="ch-The_sysconfig_Directory.html#s1-sysconfig-files">Files in the /etc/sysconfig/ Directory</a></dt><dt>追加情報, <a class="indexterm" href="ch-The_sysconfig_Directory.html">sysconfig ディレクトリー</a></dt></dl></dd><dt> sysctl </dt><dd><dl><dt>configuring with /etc/sysctl.conf , <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt><dt>controlling /proc/sys/ , <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt></dl></dd
><dt>SysRq (参照 system request key)</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 request key</dt><dd><dl><dt>enabling, <a class="indexterm" href="s2-proc-dir-sys.html"> /proc/sys/ </a></dt></dl></dd><dt>System Request Key</dt><dd><dl><dt>definition of, <a class="indexterm" href="s2-proc-dir-sys.html"> /proc/sys/ </a></dt><dt>setting timing for, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt></dl></dd><dt> system-config-authentication (参照 認証の設定ツール )</dt><dt>system-config-kdump (参照 kdump)</dt><dt>system-config-users (参照 ユーザーの設定およびグループの設定)</dt><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>TLB cache (参照 hugepages)</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><dt> twm , <a class="indexterm" href="s2-x-clients-winmanagers.html">ウィンドウマネージャ</a></dt><dd><dl><dt>(参照 X)</dt></dl></dd></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>User Manager (参照 ユーザーの設定)</dt><dt>useradd コマンド</dt><dd><dl><dt>ユーザーアカウント作成, <a class="indexterm" href="s1-users-tools.html#s2-users-tools-users-add">新規ユーザーを追加する</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>virtual file system (参照 proc fil
e system)</dt><dt>virtual files (参照 proc file system)</dt><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" hr
ef="s2-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><d
t>security 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>window managers (å‚ç…§ X)</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_P
rint_Servers.html#s3-samba-encrypted-passwords">暗合化されたパスワード</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</dt><dd><dl><dt> /etc/X11/xorg.conf </dt><dd><dl><dt>boolean values for, <a class="indexterm" href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf-struct">The Structure of the Configu
ration</a></dt><dt> Device , <a class="indexterm" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-device">The Device section</a></dt><dt> DRI , <a class="indexterm" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-dri">The DRI section</a></dt><dt> Files section, <a class="indexterm" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-files">The Files section</a></dt><dt> InputDevice section, <a class="indexterm" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-inputd">The InputDevice section</a></dt><dt>introducing, <a class="indexterm" href="s2-x-server-config-xorg.conf.d.html">The xorg.conf.d Directory</a>, <a class="indexterm" href="s2-x-server-config-xorg.conf.html">The xorg.conf File</a></dt><dt> Monitor , <a class="indexterm" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-monitor">The Monitor section</a></dt><dt> Screen , <a class="indexterm" href="s2-x-server-config-xor
g.conf.html#s3-x-server-config-xorg.conf-screen">The Screen section</a></dt><dt> Section tag, <a class="indexterm" href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf-struct">The Structure of the Configuration</a></dt><dt> ServerFlags section, <a class="indexterm" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-serverf">The ServerFlags section</a></dt><dt> ServerLayout section, <a class="indexterm" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-serverl">ServerLayout</a></dt><dt>structure of, <a class="indexterm" href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf-struct">The Structure of the Configuration</a></dt></dl></dd><dt>additional resources, <a class="indexterm" href="s1-x-additional-resources.html">ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-x-additional-resources.html#s2-x-installed-documentation">インストールã•ã‚Œã¦ã„るドã‚ュãƒ
¡ãƒ³ãƒˆ</a></dt><dt>useful websites, <a class="indexterm" href="s2-x-useful-websites.html">å½¹ã«ç«‹ã¤ Web サイト</a></dt></dl></dd><dt>configuration directory</dt><dd><dl><dt> /etc/X11/xorg.conf.d , <a class="indexterm" href="s2-x-server-config-xorg.conf.d.html">The xorg.conf.d Directory</a></dt></dl></dd><dt>configuration files</dt><dd><dl><dt> /etc/X11/ directory, <a class="indexterm" href="s1-x-server-configuration.html">X サーãƒãƒ¼è¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></dt><dt> /etc/X11/xorg.conf , <a class="indexterm" href="s2-x-server-config-xorg.conf.html">The xorg.conf File</a></dt><dt>options within, <a class="indexterm" href="s1-x-server-configuration.html">X サーãƒãƒ¼è¨å®šãƒ•ã‚¡ã‚¤ãƒ«</a></dt><dt>server options, <a class="indexterm" href="s2-x-server-config-xorg.conf.d.html">The xorg.conf.d Directory</a>, <a class="indexterm" href="s2-x-server-config-xorg.conf.html">The xorg.conf File</a></dt></dl></dd><dt>desktop environments</dt><dd><dl><dt>GNOME, <a class="indexter
m" href="s1-x-clients.html#s2-x-clients-desktop">デスクトップ環境</a></dt><dt>KDE, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">デスクトップ環境</a></dt></dl></dd><dt>fonts</dt><dd><dl><dt>Fontconfig, <a class="indexterm" href="s1-x-fonts.html">フォント</a></dt><dt>Fontconfig, adding fonts to, <a class="indexterm" href="s1-x-fonts.html#s3-x-fonts-fontconfig-add">Fontconfig へのフォントの追加</a></dt><dt>FreeType, <a class="indexterm" href="s1-x-fonts.html">フォント</a></dt><dt>introducing, <a class="indexterm" href="s1-x-fonts.html">フォント</a></dt><dt>Xft, <a class="indexterm" href="s1-x-fonts.html">フォント</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="ch-The_X_Window_System.html">X Window System</a></dt><dt>window managers</dt><dd><dl><dt> kwin , <a class="indexterm" href="s2-x-clients-winmanagers.html">ウィンドウマネージャ</a></dt><dt> metacity , <a class="indexterm" href="s2-x-clie
nts-winmanagers.html">ウィンドウマネージャ</a></dt><dt> mwm , <a class="indexterm" href="s2-x-clients-winmanagers.html">ウィンドウマネージャ</a></dt><dt> twm , <a class="indexterm" href="s2-x-clients-winmanagers.html">ウィンドウマネージャ</a></dt></dl></dd><dt>X clients, <a class="indexterm" href="ch-The_X_Window_System.html">X Window System</a>, <a class="indexterm" href="s1-x-clients.html">デスクトップ環境とウィンドウマネージャ</a></dt><dd><dl><dt>desktop environments, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">デスクトップ環境</a></dt><dt>window managers, <a class="indexterm" href="s2-x-clients-winmanagers.html">ウィンドウマネージャ</a></dt></dl></dd><dt>X server, <a class="indexterm" href="ch-The_X_Window_System.html">X Window System</a></dt><dd><dl><dt>features of, <a class="indexterm" href="ch-The_X_Window_System.html#s1-x-server">The X Server</a></dt></dl></dd></dl></dd><dt>X Wi
ndow System (参照 X)</dt><dt>X.500 (参照 OpenLDAP)</dt><dt>X.500 Lite (参照 OpenLDAP)</dt><dt>Xorg (参照 Xorg)</dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>Yum</dt><dd><dl><dt>Yum と Yum リポジトリーの設定, <a class="indexterm" href="sec-Configuring_Yum_and_Yum_Repositories.html">Yum と Yum リポジトリーの設定</a></dt><dt>Yum を用いたインストール, <a class="indexterm" href="sec-Installing.html">パッケージのインストール</a></dt><dt>Yum を用いたパッケージ グループのアンインストール, <a class="indexterm" href="sec-Removing.html">パッケージの削除</a></dt><dt>Yum を用いたパッケージのアンインストール, <a class="indexterm" href="sec-Removing.html">パッケージの削除</a></dt><dd><dl><dt>yum remove package_name, <a class="indexterm" href="sec-Removing.html">パッケージの削除</a></dt></dl></dd><dt>Yum を用いたパッケージの一覧表示</dt><dd><dl><dt>yum gro
uplist, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt><dt>yum list, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt><dt>yum list all, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt><dt>yum list available, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt><dt>yum list installed, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt><dt>yum repolist, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージã®æ¤œç´¢</dt><dd><dl><dt>yum search, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">パッケージã®æ¤œç´¢</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージã®è¡¨ç¤º</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Displaying_Package_Information.html">パッã‚
±ãƒ¼ã‚¸æƒ…å ±ã®è¡¨ç¤º</a></dt></dl></dd><dt>Yum を用ã„ãŸãƒ‘ッケージグループã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«, <a class="indexterm" href="sec-Installing.html">パッケージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«</a></dt><dt>Yum を用ã„ãŸãƒ‘ッケージ一覧</dt><dd><dl><dt>Glob 表記, <a class="indexterm" href="sec-Listing_Packages.html">パッケージã®ä¸€è¦§</a></dt></dl></dd><dt>Yum プラグイン, <a class="indexterm" href="sec-Yum_Plugins.html">Yum プラグイン</a></dt><dt>Yum リãƒã‚¸ãƒˆãƒªãƒ¼</dt><dd><dl><dt>Yum 㨠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¨å®š, <a class="indexterm" href="sec-Configuring_Yum_and_Yum_Repositories.html">Yum 㨠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¨å®š</a></dt></dl></dd><dt>[main] オプションã®è¨å®š, <a class="indexterm" href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">[main] オプションã®è¨å®š</a></dt><dt>[repository] オプションã®è¨å®š, <a class="indexterm" href="sec-Setting_repository_Options.html">[repository] オ
プションの設定</a></dt><dt>パッケージとパッケージ グループ, <a class="indexterm" href="sec-Packages_and_Package_Groups.html">パッケージとパッケージ グループ</a></dt><dt>パッケージの表示</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Displaying_Package_Information.html">パッケージ情報の表示</a></dt></dl></dd><dt>プラグイン</dt><dd><dl><dt>fs-snapshot, <a class="indexterm" href="sec-Plugin_Descriptions.html">プラグインの説明</a></dt><dt>presto, <a class="indexterm" href="sec-Plugin_Descriptions.html">プラグインの説明</a></dt><dt>refresh-packagekit, <a class="indexterm" href="sec-Plugin_Descriptions.html">プラグインの説明</a></dt><dt>rhnplugin, <a class="indexterm" href="sec-Plugin_Descriptions.html">プラグインの説明</a></dt><dt>security, <a class="indexterm" href="sec-Plugin_Descriptions.html">プラグインの説明</a></dt></dl></dd><dt>プラグインの有効化, <a class
="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Yum プラグインの無効化、有効化、設定</a></dt><dt>プラグインの無効化, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Yum プラグインの無効化、有効化、設定</a></dt><dt>プラグインの設定, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Yum プラグインの無効化、有効化、設定</a></dt><dt>リポジトリー, <a class="indexterm" href="sec-Managing_Yum_Repositories.html">Yum リポジトリの追加・有効化および無効化</a>, <a class="indexterm" href="sec-Creating_a_Yum_Repository.html">Yum リポジトリーの作成</a></dt><dt>変数, <a class="indexterm" href="sec-Using_Yum_Variables.html">Yum 変数の使い方</a></dt><dt>追加リソース, <a class="indexterm" href="sec-Additional_Resources.html">その他のリ
ソース</a></dt></dl></dd><dt>Yum での更新</dt><dd><dl><dt>セキュリティ関連のパッケージ更新, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">パッケージの更新</a></dt><dt>パッケージの更新, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">パッケージの更新</a></dt><dt>全パッケージと依存性の更新, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">パッケージの更新</a></dt><dt>単一パッケージの更新, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">パッケージの更新</a></dt><dt>更新の確認, <a class="indexterm" href="ch-yum.html#sec-Checking_For_Updates">更新の確認</a></dt></dl></dd><dt>Yum リポジトリー</dt><dd><dl><dt>PackageKit を用いた Yum リポジトリーの表示, <a class="indexterm" href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">ソフトウェアソースの設定</a></dt></dl></dd></dl></div></div
></div><ul class="docnav"><li class="previous"><a accesskey="p" href="app-Revision_History.html"><strong>戻る</strong>付録F 改訂履歴</a></li><li class="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/17/html/System_Administrators_Guide/lease-database.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/lease-database.html
new file mode 100644
index 0000000..c83ad6c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/lease-database.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>11.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-dhcp-configuring-server.html" title="11.2. DHCP サーバーの設定" /><link rel="prev" href="s1-dhcp-configuring-server.html" title="11.2. DHCP サーバーの設定" /><link rel="next" href="ch11s02s03.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-dhcp-configuring-server.html"><strong>戻る</s
trong></a></li><li class="next"><a accesskey="n" href="ch11s02s03.html"><strong>次へ</strong></a></li></ul><div class="section" id="lease-database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.2.2. リースデータベース</h3></div></div></div><div class="para">
+ On the DHCP server, the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> stores the DHCP client lease database. Do not change this file. DHCP lease information for each recently assigned IP address is automatically stored in the lease database. The information includes the length of the lease, to whom the IP address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card that was used to retrieve the lease.
+ </div><div class="para">
+ リースデータベースにおける時刻はすべて、ローカル時でなく UTC (Coordinated Universal Time) を使用します。
+ </div><div class="para">
+ The lease database is recreated from time to time so that it is not too large. First, all known leases are saved in a temporary lease database. The <code class="filename">dhcpd.leases</code> file is renamed <code class="filename">dhcpd.leases~</code> and the temporary lease database is written to <code class="filename">dhcpd.leases</code>.
+ </div><div class="para">
+ The DHCP daemon could be killed or the system could crash after the lease database has been renamed to the backup file but before the new file has been written. If this happens, the <code class="filename">dhcpd.leases</code> file does not exist, but it is required to start the service. Do not create a new lease file. If you do, all old leases are lost which causes many problems. The correct solution is to rename the <code class="filename">dhcpd.leases~</code> backup file to <code class="filename">dhcpd.leases</code> and then start the daemon.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-configuring-server.html"><strong>戻る</strong>11.2. DHCP サーバーの設定</a></li><li class="up"><a accesskey="u" href="#"><strong>上に戻る</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>ホーム</strong></a></li><li class="next"><a accesskey="n" href="ch11s02s03.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/17/html/System_Administrators_Guide/part-Basic_System_Configuration.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Basic_System_Configuration.html
new file mode 100644
index 0000000..7cb7970
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-Configuring_the_Language_and_Keyboard.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-Acknowledgments.html"><strong>戻る</strong></a></li><
li class="next"><a accesskey="n" href="ch-Configuring_the_Language_and_Keyboard.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="idm55093664"><div></div><div class="para">
+ このパートは、キーボードの設定、日付と時刻の設定、およびユーザーとグループの管理のような基本的なシステムの管理作業を取り扱います。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="ch-Configuring_the_Language_and_Keyboard.html">1. 言語とキーボードの設定</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Language_and_Keyboard.html#sect-Configuring_the_Language_and_Keyboard-Language">1.1. 言語の変更</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Language_and_Keyboard-Formats.html">1.2. 日付、時刻および数字の形式の変更</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Language_and_Keyboard-Layouts.html">1.3. キーボードのレイアウト変更</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Language_and_Keyboard-System.html">1.4. 現在の設定の表示</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Configuring_the_Date_and_Time.html">2. 日付と時刻の設定</a></span></dt><dd><dl><dt><span class="section"><a href
="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-Date_and_Time">2.1. 日付ã¨æ™‚刻ã®è¨å®šãƒ„ールã®ä½¿ã„æ–¹</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html">2.2. コマンドラインツールã®ä½¿ç”¨</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html#sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date">2.2.1. 日付ã®å¤‰æ›´æ–¹æ³•</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html">2.2.2. 時刻ã®å¤‰æ›´æ–¹æ³•</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html">2.2.3. Network Time Protocol ã®è¨å®š</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Additional_Resources.html">2.3. ãã
®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-Additional_Resources.html#sect-Configuring_the_Date_and_Time-Additional_Resources-Installed_Documentation">2.3.1. インストールã•ã‚Œã¦ã„るドã‚ュメント</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Managing_Users_and_Groups.html">3. ユーザーã¨ã‚°ãƒ«ãƒ¼ãƒ—ã®ç®¡ç†</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">3.1. ユーザーã¨ã‚°ãƒ«ãƒ¼ãƒ—ã®ã‚¤ãƒ³ãƒˆãƒãƒ€ã‚¯ã‚·ãƒ§ãƒ³</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">3.1.1. ユーザープライベートグループ</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">3.1.2. シャドウパスワード</a></span></dt></dl></dd><dt><span class="section"><a
href="sect-Managing_Users_and_Groups-User_Accounts.html">3.2. ユーザー アカウントのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts.html#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.2.1. アカウントの設定</a></span></dt><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html">3.2.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html">3.2.3. ユーザーの削除</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">3.3. ユーザー管理のツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-configui.html#s2-redhat-config-users-list">3.3.1. ユーザーとグループを閲覧する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users
-user-new.html">3.3.2. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-group-new.html">3.3.3. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-user-properties.html">3.3.4. ユーザーのプロパティを変更する</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-group-properties.html">3.3.5. グループのプロパティを変更する</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">3.4. コマンドラインのツールを使う</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">3.4.1. 新規ユーザーを追加する</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">3.4.2. 新規グループを追加する</a></span></dt><dt><span class="section"><a href="s2-users-tools-password-aging.html">3.4.3. パスワード
エージングの有効化</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">3.4.4. 自動ログアウトの有効化</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">3.4.5. グループ用ディレクトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-additional-resources.html">3.5. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">3.5.1. インストールされているドキュメント</a></span></dt></dl></dd></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 cl
ass="next"><a accesskey="n" href="ch-Configuring_the_Language_and_Keyboard.html"><strong>次へ</strong>第1章 言語とキーボードの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Infrastructure_Services.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Infrastructure_Services.html
new file mode 100644
index 0000000..622b7d7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>パート 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s1-networkscripts-resources.html" title="7.6. その他のリソース" /><link rel="next" href="ch-Services_and_Daemons.html" title="第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="s1-networkscripts-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">パート IV. インフラストラクチャーサービス</h1></div></div></div><div class="partintro" id="idm35695680"><div></div><div class="para">
+ このパートはサービスとデーモンの設定、認証の設定、およびリモートログインを有効にする方法に関する情報を提供します。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="ch-Services_and_Daemons.html">8. サービスおよびデーモン</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">8.1. サービスの設定</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">8.1.1. サービスの有効化</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">8.1.2. サービスの無効化</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">8.2. サービスの実行</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s3-services-running-checking">8.2.1. サービスの状態の確認</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">8.2.2. サービスの実行</a></spa
n></dt><dt><span class="section"><a href="s3-services-running-stopping.html">8.2.3. サービスの停止</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">8.2.4. サービスの再起動</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">8.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">8.3.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">8.3.2. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_Authentication.html">9. 認証の設定</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">9.1. 認証の設定ツール</a></span></dt><dd><dl><dt><s
pan class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">9.1.1. 識別と認証</a></span></dt><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">9.1.2. 高度なオプション</a></span></dt><dt><span class="section"><a href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">9.1.3. コマンドライン版</a></span></dt></dl></dd><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">9.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html#sect-SSSD_User_Guide-Introduction-What_is_SSSD">9.2.1. SSIDとは?</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html">9.2.2. SSIDの特徴</a></span></dt><dt><span class="s
ection"><a href="chap-SSSD_User_Guide-Setting_Up_SSSD.html">9.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Services.html">9.2.4. サービスの設定</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Domains.html">9.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">9.2.6. Setting Up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html">9.2.7. Configuring a Proxy Domain</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Troubleshooting.html">9.2.8. トラブルシューティング</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">9.2.9. SSSD Configuration File Format</
a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">10. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">10.1. SSH プロトコル</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">10.1.1. なぜ SSH を使うのか？</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-features">10.1.2. 主な機能</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">10.1.3. プロトコル・バージョン</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">10.1.4. SSH コネクションのイベント・シーケンス</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">10.2. OpenSSH の設定</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">10.2.1. 設定ファイル</a></span></dt><dt><span c
lass="section"><a href="s2-ssh-configuration-sshd.html">10.2.2. OpenSSH サーバーの起動</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">10.2.3. リモート接続に対する SSH の要求</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">10.2.4. キー認証の使用</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clients.html">10.3. OpenSSH クライアント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">10.3.1. ssh ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">10.3.2. <code class="command">scp</code> ユーティリティの使用方法</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">10.3.3. <code class="command">sftp</code> ユーティリティの使用方法</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-bey
ondshell.html">10.4. 安全なシェル以上のもの</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">10.4.1. X11 転送</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">10.4.2. ポート転送</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">10.5. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-openssh-additional-resources.html#s2-openssh-installed-docs">10.5.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-openssh-useful-websites.html">10.5.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-resources.html"><strong>戻る</strong>7.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="ch-Services_and_Daemons.html"><strong>次へ</strong>第8章 サービスおよびデーモン</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html
new file mode 100644
index 0000000..cf74e00
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>パート VII. カーネル、モジュールおよびドライバーの設定</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s2-oprofile-useful-websites.html" title="20.11.2. 役に立つ Web サイト" /><link rel="next" href="ch-Manually_Upgrading_the_Kernel.html" title="第21章 カーネルをアップグレードする" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-useful-websites.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="part" id="part-Kernel_Module_and_Driver_Configuration"><div class="titlepage"><div><div text-align="center"><h1 class="title">パート VII. カーネル、モジュールおよびドライバーの設定</h1></div></div></div><div class="partintro" id="idm55382800"><div></div><div class="para">
+ このパートは管理者にカーネルのカスタマイズを支援するさまざまなツールを取り扱います。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="ch-Manually_Upgrading_the_Kernel.html">21. カーネルをアップグレードする</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">21.1. カーネルパッケージの概要</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">21.2. アップグレードの準備</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">21.3. アップグレードされたカーネルをダウンロードする</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">21.4. アップグレードの実行</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">21.5. 初期RAMディスクイメージの確認</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">21.6. ブートローダの確認</a></spa
n></dt><dd><dl><dt><span class="section"><a href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-pseries.html">21.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">22. 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">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. モジュールの読み込み方法</a></span><
/dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sec-Specific_Kernel_Module_Capabilities.html">22.7. Specific Kernel Module Capabilities</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Specific_Kernel_Module_Capabilities.html#sec-Using_Multiple_Ethernet_Cards">22.7.1. 複数のイーサネットカードの使用</a></span></dt><dt><span class="section"><a href="sec-Using_Channel_Bonding.html">22.7.2. Using Channel Bonding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">22.8. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kernel-modules-additi
onal-resources.html#s2-kernel-modules-additional-resources-installed">22.8.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-kernel-modules-additional-resources-websites.html">22.8.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-kdump.html">23. The kdump Crash Recovery Service</a></span></dt><dd><dl><dt><span class="section"><a href="ch-kdump.html#s1-kdump-installation">23.1. Installing the kdump Service</a></span></dt><dt><span class="section"><a href="s1-kdump-configuration.html">23.2. Configuring the kdump Service</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kdump-configuration.html#s2-kdump-configuration-firstboot">23.2.1. Configuring the kdump at First Boot</a></span></dt><dt><span class="section"><a href="s2-kdump-configuration-gui.html">23.2.2. Using the Kernel Dump Configuration Utility</a></span></dt><dt><span class="section"><a href="s2-k
dump-configuration-cli.html">23.2.3. Configuring kdump on the Command Line</a></span></dt><dt><span class="section"><a href="s2-kdump-configuration-testing.html">23.2.4. Testing the Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kdump-crash.html">23.3. Analyzing the Core Dump</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kdump-crash.html#s2-kdump-crash-running">23.3.1. Running the crash Utility</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-log.html">23.3.2. Displaying the Message Buffer</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-backtrace.html">23.3.3. Displaying a Backtrace</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-processes.html">23.3.4. Displaying a Process Status</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-memory.html">23.3.5. Displaying Virtual Memory Information</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-files.html">23.
3.6. Displaying Open Files</a></span></dt><dt><span class="section"><a href="s2-kdump-crash-exit.html">23.3.7. Exiting the Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kdump-resources.html">23.4. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kdump-resources.html#s2-kdump-resources-installed">23.4.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-kdump-resources-online.html">23.4.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-useful-websites.html"><strong>戻る</strong>20.11.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-Manually_Upgrading_the
_Kernel.html"><strong>次へ</strong>第21章 カーネルをアップグレードする</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Monitoring_and_Automation.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Monitoring_and_Automation.html
new file mode 100644
index 0000000..53abf74
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>パート 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s1-printing-additional-resources.html" title="16.3.11. その他のリソース" /><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="s1-printing-additional-resources.html"><strong>戻ã‚
‹</strong></a></li><li class="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">パート VI. 監視ãŠã‚ˆã³è‡ªå‹•åŒ–</h1></div></div></div><div class="partintro" id="idm44013312"><div></div><div class="para">
+ このパートは、システム管理者がシステムのパフォーマンスを監視する、システムタスクを自動化する、およびバグを報告することができる、さまざまなツールを説明しています。
+ </div><div class="toc"><p><strong>目次</strong></p><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 Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-memory-usage.html#s2-sysinfo-memo
ry-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 href="s2-sysinf
o-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-configuring-rsyslog">18.1. rsyslog の設定法</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-global-directives">18.1.1. 全体ディレクティブ</a></span></dt><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-modules">18.1.2. モジュール</a></span></dt><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-rules">18.1.3. ルール</a></span></dt><dt><span clas
s="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s2-rsyslog-cmd-options">18.1.4. <span class="application"><strong>rsyslog</strong></span> コマンドライン設定</a></span></dt></dl></dd><dt><span class="section"><a href="s1-logfiles-locating.html">18.2. ログファイルを探す</a></span></dt><dd><dl><dt><span class="section"><a href="s1-logfiles-locating.html#configuring-logrotate">18.2.1. logrotate の設定法</a></span></dt></dl></dd><dt><span class="section"><a href="s1-logfiles-viewing.html">18.3. ログファイルの表示</a></span></dt><dt><span class="section"><a href="s1-logfiles-adding.html">18.4. ログファイルの追加</a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">18.5. ログファイルを監視する</a></span></dt><dt><span class="section"><a href="s1-log-files-additional-resources.html">18.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-log-files-additional-re
sources.html#s2-log-files-installed-docs">18.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-log-files-useful-websites.html">18.6.2. 役に立つ Web サイト</a></span></dt></dl></dd></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#s2-autotasks-cron-service">19.1.1. サービスの起動と停止</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">19.1.2. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">19.1.3. Configuring Cron Jobs</a></span></dt><dt><span class="section"><
a href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">19.1.4. Cron へのアクセスの制御</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">19.1.5. Black/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#s2-autotasks-at-configuring">19.2.1. At ジョブの設定</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">19.2.2. batch ジョブの設定</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">19.2.3. 保留ジョブの表示</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">19.2.4. その他のコマンドラインオプション</a></span></dt><dt><span class="section"><a href="s2-autotask
s-at-batch-controlling-access.html">19.2.5. at と batch へのアクセスの制御</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-service.html">19.2.6. サービスの起動と停止</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">19.3. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">19.3.1. インストールされているドキュメント</a></span></dt></dl></dd></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><dt><span class="section"><a href="s1-oprofile-configuring.html">20.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">20.2.1. Specifying t
he Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">20.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">20.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">20.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">20.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">20.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">20.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">20.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">20.5.3. Get
ting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">20.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">20.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">20.7. 使用法の例</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">20.8. 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.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-gui.html">20.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">20.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="s1-oprofile-additi
onal-resources.html">20.11. 追加のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-docs">20.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="s2-oprofile-useful-websites.html">20.11.2. 役に立つ Web サイト</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-additional-resources.html"><strong>戻る</strong>16.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="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/17/html/System_Administrators_Guide/part-Networking.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Networking.html
new file mode 100644
index 0000000..8c3b010
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Networking.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="ch-Graphical_Package_Management-sec-Additional_Resources.html" title="5.4. その他のリソース" /><link rel="next" href="ch-NetworkManager.html" title="第6章 NetworkManager" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Graphical_Package_Management-sec-Additional_Resource
s.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ch-NetworkManager.html"><strong>次へ</strong></a></li></ul><div class="part" id="part-Networking"><div class="titlepage"><div><div text-align="center"><h1 class="title">パート III. ネットワーク</h1></div></div></div><div class="partintro" id="idm37158672"><div></div><div class="para">
+ このパートは Fedora においてネットワークを設定する方法を説明しています。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="ch-NetworkManager.html">6. NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="ch-NetworkManager.html#sec-The_NetworkManager_Daemon">6.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html">6.2. Interacting with NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">6.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">6.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.html">6.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-User_and_System_Connections.html">6.2.4. User and System Co
nnections</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Establishing_Connections.html">6.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Establishing_Connections.html#sec-Establishing_a_Wired_Ethernet_Connection">6.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Wireless_Connection.html">6.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">6.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">6.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html">6.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_Routes.html">6.3.6. Establishing Routes</a></span></dt>
</dl></dd><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">6.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html#sec-Configuring_802.1x_Security">6.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_Wireless_Security.html">6.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_PPP_Point-to-Point_Settings.html">6.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv4_Settings.html">6.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Settings.html">6.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sec-NetworkManager_Architecture.html">6.5. NetworkManager Architecture</a></span></dt></dl></dd><dt><span class="chapter"><a
href="ch-Network_Interfaces.html">7. ネットワーク・インターフェース</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Network_Interfaces.html#s1-networkscripts-files">7.1. ネットワーク設定ファイル</a></span></dt><dt><span class="section"><a href="s1-networkscripts-interfaces.html">7.2. インターフェース設定ファイル</a></span></dt><dd><dl><dt><span class="section"><a href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">7.2.1. イーサネット インターフェース</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-chan.html">7.2.2. チャンネル・ボンディング・インターフェース</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces_network-bridge.html">7.2.3. ネットワークブリッジ</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html">7.2.4. Setting up 802.1q VLAN tagging<
/a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-alias.html">7.2.5. エイリアス ファイルとクローン ファイル</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-ppp0.html">7.2.6. ダイヤルアップ インターフェース</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-other.html">7.2.7. 他のインターフェース</a></span></dt></dl></dd><dt><span class="section"><a href="s1-networkscripts-control.html">7.3. インターフェース制御スクリプト</a></span></dt><dt><span class="section"><a href="s1-networkscripts-static-routes.html">7.4. スタティック ルートの設定</a></span></dt><dt><span class="section"><a href="s1-networkscripts-functions.html">7.5. ネットワーク機能ファイル</a></span></dt><dt><span class="section"><a href="s1-networkscripts-resources.html">7.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section
"><a href="s1-networkscripts-resources.html#s2-networkscripts-docs-inst">7.6.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>戻る</strong>5.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="ch-NetworkManager.html"><strong>次へ</strong>第6章 NetworkManager</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Package_Management.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Package_Management.html
new file mode 100644
index 0000000..7aec587
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s1-users-groups-additional-resources.html" title="3.5. その他のリソース" /><link rel="next" href="ch-yum.html" title="第4章 Yum" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-groups-additional-resources.html"><strong>戻る</strong></a></li><li class="next"><a ac
cesskey="n" href="ch-yum.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="idm33246480"><div></div><div class="para">
+ Fedora システムにおいてすべてのソフトウェアは、インストール、更新、または削除できる RPM パッケージに分割されています。このパートは Fedora において <span class="application"><strong>Yum</strong></span> およびグラフィカルなパッケージ管理ツールの <span class="application"><strong>PackageKit</strong></span> 製品群を使用してパッケージを管理する方法を説明しています。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="ch-yum.html">4. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">4.1. パッケージの確認と更新</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">4.1.1. 更新の確認</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">4.1.2. パッケージの更新</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">4.1.3. 設定ファイル変更の保存</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">4.2. パッケージとパッケージ グループ</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">4.2.1. パッケージの検索</a></span></dt><dt><span class="section"><
a href="sec-Listing_Packages.html">4.2.2. パッケージの一覧</a></span></dt><dt><span class="section"><a href="sec-Displaying_Package_Information.html">4.2.3. パッケージ情報の表示</a></span></dt><dt><span class="section"><a href="sec-Installing.html">4.2.4. パッケージのインストール</a></span></dt><dt><span class="section"><a href="sec-Removing.html">4.2.5. パッケージの削除</a></span></dt><dt><span class="section"><a href="sec-Yum-Transaction_History.html">4.2.6. 処理とトランザクションの履歴</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">4.3. Yum と Yum リポジトリーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">4.3.1. [main] オプションの設定</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">4.3.2. [repository] オプション
の設定</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">4.3.3. Yum 変数の使い方</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Current_Configuration.html">4.3.4. 現在の設定の表示</a></span></dt><dt><span class="section"><a href="sec-Managing_Yum_Repositories.html">4.3.5. Yum リポジトリの追加・有効化および無効化</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">4.3.6. Yum リポジトリーの作成</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">4.4. Yum プラグイン</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Yum プラグインの無効化、有効化、設定</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">4.4.2. 追加の Yum プラグインのインストール</a></span></dt><dt><sp
an class="section"><a href="sec-Plugin_Descriptions.html">4.4.3. プラグインの説明</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Additional_Resources.html">4.5. その他のリソース</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-PackageKit.html">5. PackageKit</a></span></dt><dd><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">5.1. ソフトウェアの更新を用いたパッケージの更新</a></span></dt><dd><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Setting_preferences_for_checking_for_updates">5.1.1. 更新の確認間隔の設定</a></span></dt><dt><span class="section"><a href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">5.1.2. ソフトウェアソースの設定</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html">5.2. ソフトウェアの追加/削除の使用</a></span></dt><dd><dl><d
t><span class="section"><a href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. ソフトウェアソースの更新 (Yum リポジトリー)</a></span></dt><dt><span class="section"><a href="sec-Finding_Packages_with_Filters.html">5.2.2. フィルターを用いたパッケージの検索</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Packages_and_Dependencies.html">5.2.3. パッケージ（および依存するもの）のインストールおよび削除</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Package_Groups.html">5.2.4. パッケージグループのインストールおよび削除</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Transaction_Log.html">5.2.5. トランザクションログの表示</a></span></dt></dl></dd><dt><span class="section"><a href="sec-PackageKit_Architecture.html">5.3. PackageKit アーキテクチャー</a></span><
/dt><dt><span class="section"><a href="ch-Graphical_Package_Management-sec-Additional_Resources.html">5.4. その他のリソース</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-additional-resources.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="ch-yum.html"><strong>次へ</strong>第4章 Yum</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Servers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/part-Servers.html
new file mode 100644
index 0000000..845dd50
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>パート 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="index.html" title="システム管理者ガイド" /><link rel="prev" href="s2-openssh-useful-websites.html" title="10.5.2. 役に立つ Web サイト" /><link rel="next" href="ch-DHCP_Servers.html" title="第11章 DHCP サーバー" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-openssh-useful-websites.html"><strong>戻る</strong></a></li><li class="ne
xt"><a accesskey="n" href="ch-DHCP_Servers.html"><strong>次へ</strong></a></li></ul><div class="part" id="part-Servers"><div class="titlepage"><div><div text-align="center"><h1 class="title">パート V. サーバー</h1></div></div></div><div class="partintro" id="idm69534944"><div></div><div class="para">
+ このパートは、ウェブサーバーを導入する、またはネットワーク上にファイルとディレクトリを共有する方法のようなサーバーに関連したさまざまな話題を説明しています。
+ </div><div class="toc"><p><strong>目次</strong></p><dl><dt><span class="chapter"><a href="ch-DHCP_Servers.html">11. DHCP サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DHCP_Servers.html#s1-dhcp-why">11.1. DHCP を使用する理由</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">11.2. DHCP サーバーの設定</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-configuring-server.html#config-file">11.2.1. 設定ファイル</a></span></dt><dt><span class="section"><a href="lease-database.html">11.2.2. リースデータベース</a></span></dt><dt><span class="section"><a href="ch11s02s03.html">11.2.3. サーバーの起動と停止</a></span></dt><dt><span class="section"><a href="dhcp-relay-agent.html">11.2.4. DHCP リレーエージェント</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp-configuring-client.html">11.3. DHCP クライアントの設定</a></span></dt><dt><
span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html">11.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configuration">11.4.1. ホストの設定</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">11.5. IPv6 向け DHCP (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">11.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">11.6.1. インストールされているドキュメント</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-DNS_Servers.html">12. DNS サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DNS_Servers.html#s1-Introduction_to_DNS">12.1. DNS の概要</a></span></dt><dd><dl><dt><span class="section"><a href="c
h-DNS_Servers.html#s2-dns-introduction-zones">12.1.1. ネームサーバーゾーン</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">12.1.2. ネームサーバーのタイプ</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#s2-dns-introduction-bind">12.1.3. ネームサーバーとしての BIND</a></span></dt></dl></dd><dt><span class="section"><a href="s1-BIND.html">12.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="s1-BIND.html#s2-bind-namedconf">12.2.1. named サービスの設定</a></span></dt><dt><span class="section"><a href="s2-bind-zone.html">12.2.2. ゾーンファイルの編集</a></span></dt><dt><span class="section"><a href="s2-bind-rndc.html">12.2.3. rndc ユーティリティの使用法</a></span></dt><dt><span class="section"><a href="s2-bind-dig.html">12.2.4. dig ユーティリティの使用</a></span></dt><dt><span class="section"><a href="s2-bind-features.htm
l">12.2.5. BIND の高度な機能</a></span></dt><dt><span class="section"><a href="s2-bind-mistakes.html">12.2.6. よくある間違いを避けるために</a></span></dt><dt><span class="section"><a href="s2-bind-additional-resources.html">12.2.7. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Web_Servers.html">13. ウェブ サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">13.1. Apache HTTP サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-features">13.1.1. 新機能</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-changes">13.1.2. 注目すべき変更</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">13.1.3. 設定の更新</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-r
unning">13.1.4. httpd サービスの実行方法</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-editing">13.1.5. 設定ファイルの編集</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">13.1.6. Working with Modules</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-virtualhosts">13.1.7. 仮想ホストのセットアップ</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">13.1.8. SSL サーバーのセットアップ</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">13.1.9. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Mail_Servers.html">14. メールサーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s1-email-protocols">14.1. 電子メールプロトコル</a></span></dt><dd><dl><dt><span class="section"
><a href="ch-Mail_Servers.html#s2-email-protocols-send">14.1.1. メール トランスポートのプロトコル</a></span></dt><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-client">14.1.2. メール アクセスのプロトコル</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">14.2. 電子メールプログラム分類</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">14.2.1. メール転送エージェント (Mail Transport Agent)</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">14.2.2. メール配送エージェント (Mail Delivery Agent)</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">14.2.3. メール ユーザー エージェント</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">14.3. Mail Transport Agent</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.
html#s2-email-mta-postfix">14.3.1. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-sendmail.html">14.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">14.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="s2-email-switchmail.html">14.3.4. Mail Transport Agent (MTA) の設定</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mda.html">14.4. メール配送エージェント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">14.4.1. Procmail の設定</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">14.4.2. Procmail レシピ</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">14.5. メールユーザーエージェント</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">14.5.1. 通信のセキュリティ</a></span></d
t></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">14.6. その他のリソース</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">14.6.1. インストールされているドキュメント</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">14.6.2. 役に立つ Web サイト</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">14.6.3. 関連書籍</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Directory_Servers.html">15. ディレクトリー サーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">15.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">15.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-installation">
15.1.2. OpenLDAP 製品群のインストール</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">15.1.3. OpenLDAP サーバーの設定法</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-running">15.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam">15.1.5. システムが OpenLDAP を使用して認証を実行するように設定する</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-resources">15.1.6. その他のリソース</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-File_and_Print_Servers.html">16. ファイルサーバーおよびプリントサーバー</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">16.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#
samba-rgs-overview">16.1.1. Samba の概要</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">16.1.2. Samba デーモンと関連サービス</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-connect-share">16.1.3. Samba シェアへの接続</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-configuring">16.1.4. Samba サーバーの設定</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-startstop">16.1.5. Samba の開始と停止</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">16.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">16.1.7. Samba のセキュリティモード</a></span></dt><dt><span class="section"><a hr
ef="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">16.1.8. Samba のアカウント情報データベース</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">16.1.9. Samba ネットワークブラウジング</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-cups">16.1.10. CUPS 印刷サポートを使った Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-programs">16.1.11. Samba ディストリビューションプログラム</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-resources">16.1.12. その他のリソース</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">16.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-FTP.html#s2-ftp-protocol">16.2.1. ファイル伝送プロトコル</a></span></dt><dt><span class="section"><a href="s2-
ftp-servers.html">16.2.2. FTP サーバー</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">16.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">16.2.4. <code class="command">vsftpd</code> の開始と停止</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">16.2.5. <code class="command">vsftpd</code> 設定オプション</a></span></dt><dt><span class="section"><a href="s2-ftp-resources.html">16.2.6. その他のリソース</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Printer_Configuration.html">16.3. プリンタの設定</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">16.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">16.3.2. Starting Printer Setup</a></span></dt><dt><span c
lass="section"><a href="sec-Adding_Other_Printer.html">16.3.3. ローカルプリンタの追加</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">16.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">16.3.5. IPP プリンタの追加</a></span></dt><dt><span class="section"><a href="sec-printing-LPDLPR-printer.html">16.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">16.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">16.3.8. プリンタモデルの選択と終了</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">16.3.9. Printing a test page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">16.3.10. 既存プリンタの変更</a></span></dt><dt><span class="section"><a href="s1-p
rinting-additional-resources.html">16.3.11. その他のリソース</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-openssh-useful-websites.html"><strong>戻る</strong>10.5.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-DHCP_Servers.html"><strong>次へ</strong>第11章 DHCP サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/pr01.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/pr01.html
new file mode 100644
index 0000000..2f93306
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/pr01.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>序文</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm20085920" lang="ja-JP"><div class="titlepage"><div><div><h1 id="idm20085920" 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 17 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">
+ パッケージのインストールや管理に使用する <span class="application"><strong>PackageKit</strong></span> やコマンドライン <span class="application"><strong>Yum</strong></span> パッケージ マネージャー
+ </div></li><li class="listitem"><div class="para">
+ Setting up a network—from establishing an Ethernet connection using <span class="application"><strong>NetworkManager</strong></span> to configuring channel bonding interfaces to increase server bandwidth
+ </div></li><li class="listitem"><div class="para">
+ Configuring <code class="systemitem">DHCP</code>, <span class="application"><strong>BIND</strong></span>, <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">
+ Gathering information about your system, including obtaining kernel-space crash data with <code class="systemitem">kdump</code>
+ </div></li><li class="listitem"><div class="para">
+ Easily 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">Deployment 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/en-US/Fedora/16/html/Installation_Guide/index.html">Fedora 17 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/17/html/System_Administrators_Guide/pr01s03.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/pr01s03.html
new file mode 100644
index 0000000..aca4099
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm44288640" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm44288640">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="idm28337488"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm28337488">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 at 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/17/html/System_Administrators_Guide/pr01s03s02.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/pr01s03s02.html
new file mode 100644
index 0000000..3a3f10b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm57852224"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm57852224">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/17/html/System_Administrators_Guide/pr01s03s03.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/pr01s03s03.html
new file mode 100644
index 0000000..1ffe0b8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="sect-Preface-Feedback.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="pr01s03s02.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Preface-
Feedback.html"><strong>次へ</strong></a></li></ul><div class="section" id="idm35060304"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm35060304">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="sect-Preface-Feedback.html"><strong>次へ</strong>4. フィードバック</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/pref-Acknowledgments.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/pref-Acknowledgments.html
new file mode 100644
index 0000000..2276c16
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="pr01.html" title="序文" /><link rel="prev" href="sect-Preface-Feedback.html" title="4. フィードバック" /><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="sect-Preface-Feedback.html"><strong>戻る</strong></a></li><li class="next"><a acc
esskey="n" href="part-Basic_System_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">Deployment Guide</em>, copyright © 2007 Red Hat, Inc., available at <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/index.html">http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/index.html</a>.
+ </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="sect-Preface-Feedback.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="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/17/html/System_Administrators_Guide/s1-BIND.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-BIND.html
new file mode 100644
index 0000000..ceb2486
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-BIND.html
@@ -0,0 +1,347 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.2. BIND</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-DNS_Servers.html" title="第12章 DNS サーバー" /><link rel="prev" href="ch-DNS_Servers.html" title="第12章 DNS サーバー" /><link rel="next" href="s2-bind-zone.html" title="12.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-DNS_Servers.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n"
href="s2-bind-zone.html"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="section" id="s1-BIND" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.2. BIND</h2></div></div></div><a id="idm17611408" class="indexterm"></a><div class="para">
+ 本章は Fedora に含まれる DNS サーバーである <code class="systemitem">BIND</code> (Berkeley Internet Name Domain) を取り扱います。その設定ファイルの構造に焦点を当て、ローカルおよびリモートで管理する方法について説明しています。
+ </div><div class="section" id="s2-bind-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.1. named サービスの設定</h3></div></div></div><a id="idm48881120" class="indexterm"></a><div class="para">
+ <code class="systemitem">named</code> サービスが起動するとき、<a class="xref" href="s1-BIND.html#table-bind-namedconf-files">表12.1「named サービス設定ファイル」</a>において説明されているように、ファイルから設定が読み込まれます。
+ </div><a id="idm48885856" class="indexterm"></a><a id="idm48887536" class="indexterm"></a><a id="idm48889488" class="indexterm"></a><div class="table" id="table-bind-namedconf-files"><h6>表12.1 named サービス設定ファイル</h6><div class="table-contents"><table summary="named サービス設定ファイル" border="1"><colgroup><col width="38%" class="path" /><col width="63%" class="description" /></colgroup><thead><tr><th class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="filename">/etc/named.conf</code>
+ </td><td class="">
+ 主要な設定ファイル。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/named/</code>
+ </td><td class="">
+ 主要な設定ファイルから取り込まれる設定ファイルのための補助ディレクトリ。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The configuration file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (that is, <code class="literal">{</code> and <code class="literal">}</code>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <code class="systemitem">named</code> service will not start. A typical <code class="filename">/etc/named.conf</code> file is organized as follows:
+ </div><pre class="programlisting"><em class="replaceable"><code>statement-1</code></em> ["<em class="replaceable"><code>statement-1-name</code></em>"] [<em class="replaceable"><code>statement-1-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-2</code></em> ["<em class="replaceable"><code>statement-2-name</code></em>"] [<em class="replaceable"><code>statement-2-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-N</code></em> ["<em class="replaceable"><code>statement-N-name</code></em>"] [<em class="replaceable"><code>statement-N-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};</pre><div class="note"><div class="admonition_header"><h2>chroot 環境における BIND の実行</h2></div><div class="admonition"><div class="para">
+ If you have installed the <span class="package">bind-chroot</span> package, the BIND service will run in the <code class="filename">/var/named/chroot</code> environment. In that case, the initialization script will mount the above configuration files using the <code class="command">mount --bind</code> command, so that you can manage the configuration outside this environment.
+ </div></div></div><div class="section" id="s3-bind-namedconf-state"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.1.1. 一般的なステートメントのタイプ</h4></div></div></div><div class="para">
+ 以下の種類の宣言が一般的に <code class="filename">/etc/named.conf</code> において使用されます:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm59346160" class="indexterm"></a>
+ <code class="option">acl</code></span></dt><dd><div class="para">
+ <code class="option">acl</code> (Access Control List) ステートメントによりホストのグループを定義できます。それにより、ネームサーバーへのアクセスを許可および拒否できます。これは以下の形式をとります:
+ </div><pre class="programlisting">acl <em class="replaceable"><code>acl-name</code></em> {
+ <em class="replaceable"><code>match-element</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>acl-name</code></em> statement name is the name of the access control list, and the <em class="replaceable"><code>match-element</code></em> option is usually an individual IP address (such as <code class="literal">10.0.1.1</code>) or a CIDR network notation (for example, <code class="literal">10.0.1.0/24</code>). For a list of already defined keywords, see <a class="xref" href="s1-BIND.html#table-bind-namedconf-common-acl">表12.2「事前定義済みアクセス制御リスト」</a>.
+ </div><div class="table" id="table-bind-namedconf-common-acl"><h6>表12.2 事前定義済みアクセス制御リスト</h6><div class="table-contents"><table summary="事前定義済みアクセス制御リスト" border="1"><colgroup><col width="25%" class="keyword" /><col width="75%" class="description" /></colgroup><thead><tr><th class="">
+ キーワード
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">any</code>
+ </td><td class="">
+ すべての IP アドレスに一致します。
+ </td></tr><tr><td class="">
+ <code class="option">localhost</code>
+ </td><td class="">
+ ローカルシステムにおいて使用中のすべての IP アドレスに一致します。
+ </td></tr><tr><td class="">
+ <code class="option">localnets</code>
+ </td><td class="">
+ ローカルシステムが接続されているすべてのネットワークにある IP アドレスに一致します。
+ </td></tr><tr><td class="">
+ <code class="option">none</code>
+ </td><td class="">
+ どの IP アドレスにも一致しません。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="option">acl</code> statement can be especially useful with conjunction with other statements such as <code class="option">options</code>. <a class="xref" href="s1-BIND.html#example-bind-namedconf-common-acl">例12.1「オプションと併用した ACL の使用」</a> defines two access control lists, <code class="literal">black-hats</code> and <code class="literal">red-hats</code>, and adds <code class="literal">black-hats</code> on the blacklist while granting <code class="literal">red-hats</code> a normal access.
+ </div><div class="example" id="example-bind-namedconf-common-acl"><h6>例12.1 オプションと併用した ACL の使用</h6><div class="example-contents"><pre class="programlisting">acl black-hats {
+ 10.0.2.0/24;
+ 192.168.0.0/24;
+ 1234:5678::9abc/24;
+};
+acl red-hats {
+ 10.0.1.0/24;
+};
+options {
+ blackhole { black-hats; };
+ allow-query { red-hats; };
+ allow-query-cache { red-hats; };
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm70093248" class="indexterm"></a>
+ <code class="option">include</code></span></dt><dd><div class="para">
+ The <code class="option">include</code> statement allows you to include files in the <code class="filename">/etc/named.conf</code>, so that potentially sensitive data can be placed in a separate file with restricted permissions. It takes the following form:
+ </div><pre class="programlisting">include "<em class="replaceable"><code>file-name</code></em>"</pre><div class="para">
+ The <em class="replaceable"><code>file-name</code></em> statement name is an absolute path to a file.
+ </div><div class="example" id="example-bind-namedconf-common-include"><h6>例12.2 /etc/named.conf へのファイルの取り込み</h6><div class="example-contents"><pre class="programlisting">include "/etc/named.rfc1912.zones";</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm70103936" class="indexterm"></a>
+ <code class="option">options</code></span></dt><dd><div class="para">
+ The <code class="option">options</code> statement allows you to define global server configuration options as well as to set defaults for other statements. It can be used to specify the location of the <code class="systemitem">named</code> working directory, the types of queries allowed, and much more. It takes the following form:
+ </div><pre class="programlisting">options {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ For a list of frequently used <em class="replaceable"><code>option</code></em> directives, see <a class="xref" href="s1-BIND.html#table-bind-namedconf-common-options">表12.3「一般的に使用されるオプション」</a> below.
+ </div><div class="table" id="table-bind-namedconf-common-options"><h6>表12.3 一般的に使用されるオプション</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">allow-query</code>
+ </td><td class="">
+ ネームサーバーに権威リソースレコードを問い合わせできるホストを指定します。アクセス制御リスト、IP アドレスの組、または CIDR 表記のネットワークを受け付けます。すべてのホストがデフォルトで許可されます。
+ </td></tr><tr><td class="">
+ <code class="option">allow-query-cache</code>
+ </td><td class="">
+ ネームサーバーに再帰問い合わせのような権威のないデータを問い合わせできるホストを指定します。<code class="literal">localhost</code> および <code class="literal">localnets</code> のみがデフォルトで許可されます。
+ </td></tr><tr><td class="">
+ <code class="option">blackhole</code>
+ </td><td class="">
+ ネームサーバーに問い合わせを許可され<span class="emphasis"><em>ない</em></span>ホストを指定します。このオプションは特定のホストやネットワークがサーバーをリクエストであふれさせるときに使われるべきです。デフォルトのオプションは <code class="literal">none</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">directory</code>
+ </td><td class="">
+ <code class="systemitem">named</code> サービスの作業ディレクトリを指定します。デフォルトオプションは <code class="literal">/var/named/</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">dnssec-enable</code>
+ </td><td class="">
+ DNSSEC 関連リソースレコードを返すかどうかを指定します。デフォルトオプションは <code class="literal">yes</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">dnssec-validation</code>
+ </td><td class="">
+ リソースレコードが DNSSEC 経由で認証されることを検証するかどうかを指定します。初期オプションは <code class="option">yes</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">forwarders</code>
+ </td><td class="">
+ 要求を解決するために転送されるネームサーバーの有効な IP アドレス一覧を指定します。
+ </td></tr><tr><td class="">
+ <code class="option">forward</code>
+ </td><td class="">
+ <div class="para">
+ <code class="option">forwarders</code> ディレクティブの挙動を指定します。以下のオプションを受け取ります:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">first</code> — The server will query the nameservers listed in the <code class="option">forwarders</code> directive before attempting to resolve the name on its own.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">only</code> — When unable to query the nameservers listed in the <code class="option">forwarders</code> directive, the server will not attempt to resolve the name on its own.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">listen-on</code>
+ </td><td class="">
+ 問い合わせを受け付ける IPv4 ネットワークインターフェースを指定します。ゲートウェイとしても動作する DNS サーバーにおいて、単一のネットワークのみから問い合わせを受け付けるために、このオプションを使用できます。すべての IPv4 インターフェースがデフォルトで使用されます。
+ </td></tr><tr><td class="">
+ <code class="option">listen-on-v6</code>
+ </td><td class="">
+ 問い合わせを受け付ける IPv6 ネットワークインターフェースを指定します。ゲートウェイとしても動作する DNS サーバーにおいて、単一のネットワークのみから問い合わせを受け付けるために、このオプションを使用できます。すべての IPv6 インターフェースがデフォルトで使用されます。
+ </td></tr><tr><td class="">
+ <code class="option">max-cache-size</code>
+ </td><td class="">
+ サーバーキャッシュのために使用されるメモリーの最大量を指定します。制限に達するとき、制限を越えないように、サーバーはレコードを早めに期限切れさせます。複数のビューを持つサーバーにおいては、制限は各ビューのキャッシュにそれぞれ適用されます。デフォルトのオプションは <code class="literal">32M</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">notify</code>
+ </td><td class="">
+ <div class="para">
+ ゾーンが更新されたときに、セカンダリーネームサーバーに通知するかどうかを指定します。以下のオプションを受け付けます:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — サーバーはすべてのセカンダリーネームサーバーに通知します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — サーバーはどのセカンダリーネームサーバーにも通知<span class="emphasis"><em>しません</em></span>。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — サーバーはゾーンのマスターサーバーのみに通知します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — zone 文の中の <code class="option">also-notify</code> 一覧に指定されているセカンダリーサーバーのみに通知します。
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">pid-file</code>
+ </td><td class="">
+ <code class="systemitem">named</code> サービスにより作成されるプロセス ID ファイルの位置を指定します。
+ </td></tr><tr><td class="">
+ <code class="option">recursion</code>
+ </td><td class="">
+ 再帰的サーバーとして動作するかどうかを指定します。オプションの初期値は <code class="literal">yes</code> です。
+ </td></tr><tr><td class="">
+ <code class="option">statistics-file</code>
+ </td><td class="">
+ 統計ファイルの代替位置を指定します。<code class="filename">/var/named/named.stats</code> ファイルが標準で使用されます。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="important"><div class="admonition_header"><h2>Restrict recursive servers to selected clients only</h2></div><div class="admonition"><div class="para">
+ To prevent distributed denial of service (DDoS) attacks, it is recommended that you use the <code class="option">allow-query-cache</code> option to restrict recursive DNS services for a particular subset of clients only.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="s2-bind-additional-resources.html#s3-bind-installed-docs">「インストールされているドキュメント」</a>, and the <code class="filename">named.conf</code> manual page for a complete list of available options.
+ </div><div class="example" id="example-bind-namedconf-common-options"><h6>例12.3 options 宣言の使用法</h6><div class="example-contents"><pre class="programlisting">options {
+ allow-query { localhost; };
+ listen-on port 53 { 127.0.0.1; };
+ listen-on-v6 port 53 { ::1; };
+ max-cache-size 256M;
+ directory "/var/named";
+ statistics-file "/var/named/data/named_stats.txt";
+
+ recursion yes;
+ dnssec-enable yes;
+ dnssec-validation yes;
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm52209904" class="indexterm"></a>
+ <code class="option">zone</code></span></dt><dd><div class="para">
+ The <code class="option">zone</code> statement allows you to define the characteristics of a zone, such as the location of its configuration file and zone-specific options, and can be used to override the global <code class="option">options</code> statements. It takes the following form:
+ </div><pre class="programlisting">zone <em class="replaceable"><code>zone-name</code></em> [<em class="replaceable"><code>zone-class</code></em>] {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is the name of the zone, <em class="replaceable"><code>zone-class</code></em> is the optional class of the zone, and <em class="replaceable"><code>option</code></em> is a <code class="option">zone</code> statement option as described in <a class="xref" href="s1-BIND.html#table-bind-namedconf-common-zone">表12.4「一般的に使用されるオプション」</a>.
+ </div><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is particularly important, as it is the default value assigned for the <code class="option">$ORIGIN</code> directive used within the corresponding zone file located in the <code class="filename">/var/named/</code> directory. The <code class="systemitem">named</code> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file. For example, if a <code class="option">zone</code> statement defines the namespace for <code class="literal">example.com</code>, use <code class="literal">example.com</code> as the <em class="replaceable"><code>zone-name</code></em> so that it is placed at the end of hostnames within the <code class="literal">example.com</code> zone file.
+ </div><div class="para">
+ For more information about zone files, refer to <a class="xref" href="s2-bind-zone.html">「ゾーンファイルの編集」</a>.
+ </div><div class="table" id="table-bind-namedconf-common-zone"><h6>表12.4 一般的に使用されるオプション</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">allow-query</code>
+ </td><td class="">
+ Specifies which clients are allowed to request information about this zone. This option overrides global <code class="option">allow-query</code> option. All query requests are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-transfer</code>
+ </td><td class="">
+ Specifies which secondary servers are allowed to request a transfer of the zone's information. All transfer requests are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-update</code>
+ </td><td class="">
+ <div class="para">
+ Specifies which hosts are allowed to dynamically update information in their zone. The default option is to deny all dynamic update requests.
+ </div>
+ <div class="para">
+ Note that you should be careful when allowing hosts to update information about their zone. Do not set IP addresses in this option unless the server is in the trusted network. Instead, use TSIG key as described in <a class="xref" href="s2-bind-features.html#s3-bind-features-tsig">「Transaction SIGnatures (TSIG)」</a>.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="option">file</code>
+ </td><td class="">
+ Specifies the name of the file in the <code class="systemitem">named</code> working directory that contains the zone's configuration data.
+ </td></tr><tr><td class="">
+ <code class="option">masters</code>
+ </td><td class="">
+ Specifies from which IP addresses to request authoritative zone information. This option is used only if the zone is defined as <code class="option">type</code> <code class="option">slave</code>.
+ </td></tr><tr><td class="">
+ <code class="option">notify</code>
+ </td><td class="">
+ <div class="para">
+ ゾーンが更新されたときに、セカンダリーネームサーバーに通知するかどうかを指定します。以下のオプションを受け付けます:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — サーバーはすべてのセカンダリーネームサーバーに通知します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — サーバーはどのセカンダリーネームサーバーにも通知<span class="emphasis"><em>しません</em></span>。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — サーバーはゾーンのマスターサーバーのみに通知します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — zone 文の中の <code class="option">also-notify</code> 一覧に指定されているセカンダリーサーバーのみに通知します。
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">type</code>
+ </td><td class="">
+ <div class="para">
+ Specifies the zone type. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">delegation-only</code> — Enforces the delegation status of infrastructure zones such as COM, NET, or ORG. Any answer that is received without an explicit or implicit delegation is treated as <code class="literal">NXDOMAIN</code>. This option is only applicable in TLDs or root zone files used in recursive or caching implementations.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">forward</code> — Forwards all requests for information about this zone to other nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">hint</code> — A special type of zone used to point to the root nameservers which resolve queries when a zone is not otherwise known. No configuration beyond the default is necessary with a <code class="option">hint</code> zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master</code> — Designates the nameserver as authoritative for this zone. A zone should be set as the <code class="option">master</code> if the zone's configuration files reside on the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">slave</code> — Designates the nameserver as a slave server for this zone. Master server is specified in <code class="option">masters</code> directive.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Most changes to the <code class="filename">/etc/named.conf</code> file of a primary or secondary nameserver involve adding, modifying, or deleting <code class="option">zone</code> statements, and only a small subset of <code class="option">zone</code> statement options is usually needed for a nameserver to work efficiently.
+ </div><div class="para">
+ In <a class="xref" href="s1-BIND.html#example-bind-namedconf-common-zone-primary">例12.4「A zone statement for a primary nameserver」</a>, the zone is identified as <code class="literal">example.com</code>, the type is set to <code class="literal">master</code>, and the <code class="systemitem">named</code> service is instructed to read the <code class="filename">/var/named/example.com.zone</code> file. It also allows only a secondary nameserver (<code class="literal">192.168.0.2</code>) to transfer the zone.
+ </div><div class="example" id="example-bind-namedconf-common-zone-primary"><h6>例12.4 A zone statement for a primary nameserver</h6><div class="example-contents"><pre class="programlisting">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-transfer { 192.168.0.2; };
+};</pre></div></div><br class="example-break" /><div class="para">
+ A secondary server's <code class="option">zone</code> statement is slightly different. The type is set to <code class="literal">slave</code>, and the <code class="literal">masters</code> directive is telling <code class="systemitem">named</code> the IP address of the master server.
+ </div><div class="para">
+ In <a class="xref" href="s1-BIND.html#example-bind-namedconf-common-zone-secondary">例12.5「A zone statement for a secondary nameserver」</a>, the <code class="systemitem">named</code> service is configured to query the primary server at the <code class="literal">192.168.0.1</code> IP address for information about the <code class="literal">example.com</code> zone. The received information is then saved to the <code class="filename">/var/named/slaves/example.com.zone</code> file. Note that you have to put all slave zones to <code class="filename">/var/named/slaves</code> directory, otherwise the service will fail to transfer the zone.
+ </div><div class="example" id="example-bind-namedconf-common-zone-secondary"><h6>例12.5 A zone statement for a secondary nameserver</h6><div class="example-contents"><pre class="programlisting">zone "example.com" {
+ type slave;
+ file "slaves/example.com.zone";
+ masters { 192.168.0.1; };
+};</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s3-bind-namedconf-state-other"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.1.2. 他のステートメント形式</h4></div></div></div><div class="para">
+ The following types of statements are less commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm32491296" class="indexterm"></a>
+ <code class="option">controls</code></span></dt><dd><div class="para">
+ The <code class="option">controls</code> statement allows you to configure various security requirements necessary to use the <code class="command">rndc</code> command to administer the <code class="systemitem">named</code> service.
+ </div><div class="para">
+ <code class="command">rndc</code> ユーティリティとその使用法の詳細は<a class="xref" href="s2-bind-rndc.html">「rndc ユーティリティの使用法」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm32499248" class="indexterm"></a>
+ <code class="option">key</code></span></dt><dd><div class="para">
+ The <code class="option">key</code> statement allows you to define a particular key by name. Keys are used to authenticate various actions, such as secure updates or the use of the <code class="command">rndc</code> command. Two options are used with <code class="option">key</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">algorithm <em class="replaceable"><code>algorithm-name</code></em></code> — 使用されるアルゴリズムの種類 (たとえば、<code class="literal">hmac-md5</code>)。
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">secret "<em class="replaceable"><code>key-value</code></em>"</code> — 暗号化キー。
+ </div></li></ul></div><div class="para">
+ <code class="command">rndc</code> ユーティリティとその使用法の詳細は<a class="xref" href="s2-bind-rndc.html">「rndc ユーティリティの使用法」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm62394240" class="indexterm"></a>
+ <code class="option">logging</code></span></dt><dd><div class="para">
+ The <code class="option">logging</code> statement allows you to use multiple types of logs, so called <em class="firstterm">channels</em>. By using the <code class="option">channel</code> option within the statement, you can construct a customized type of log with its own file name (<code class="option">file</code>), size limit (<code class="option">size</code>), versioning (<code class="option">version</code>), and level of importance (<code class="option">severity</code>). Once a customized channel is defined, a <code class="option">category</code> option is used to categorize the channel and begin logging when the <code class="systemitem">named</code> service is restarted.
+ </div><div class="para">
+ By default, <code class="systemitem">named</code> sends standard messages to the <code class="systemitem">rsyslog</code> daemon, which places them in <code class="filename">/var/log/messages</code>. Several standard channels are built into BIND with various severity levels, such as <code class="literal">default_syslog</code> (which handles informational logging messages) and <code class="literal">default_debug</code> (which specifically handles debugging messages). A default category, called <code class="literal">default</code>, uses the built-in channels to do normal logging without any special configuration.
+ </div><div class="para">
+ Customizing the logging process can be a very detailed process and is beyond the scope of this chapter. For information on creating custom BIND logs, refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="s2-bind-additional-resources.html#s3-bind-installed-docs">「インストールされているドキュメント」</a>.
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm65962464" class="indexterm"></a>
+ <code class="option">server</code></span></dt><dd><div class="para">
+ The <code class="option">server</code> statement allows you to specify options that affect how the <code class="systemitem">named</code> service should respond to remote nameservers, especially with regard to notifications and zone transfers.
+ </div><div class="para">
+ The <code class="option">transfer-format</code> option controls the number of resource records that are sent with each message. It can be either <code class="literal">one-answer</code> (only one resource record), or <code class="literal">many-answers</code> (multiple resource records). Note that while the <code class="literal">many-answers</code> option is more efficient, it is not supported by older versions of BIND.
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm51167808" class="indexterm"></a>
+ <code class="option">trusted-keys</code></span></dt><dd><div class="para">
+ The <code class="option">trusted-keys</code> statement allows you to specify assorted public keys used for secure DNS (DNSSEC). Refer to <a class="xref" href="s2-bind-features.html#s3-bind-features-dnssec">「DNS Security Extensions (DNSSEC)」</a> for more information on this topic.
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm51173872" class="indexterm"></a>
+ <code class="option">view</code></span></dt><dd><div class="para">
+ The <code class="option">view</code> statement allows you to create special views depending upon which network the host querying the nameserver is on. This allows some hosts to receive one answer regarding a zone while other hosts receive totally different information. Alternatively, certain zones may only be made available to particular trusted hosts while non-trusted hosts can only make queries for other zones.
+ </div><div class="para">
+ Multiple views can be used as long as their names are unique. The <code class="option">match-clients</code> option allows you to specify the IP addresses that apply to a particular view. If the <code class="option">options</code> statement is used within a view, it overrides the already configured global options. Finally, most <code class="option">view</code> statements contain multiple <code class="option">zone</code> statements that apply to the <code class="option">match-clients</code> list.
+ </div><div class="para">
+ Note that the order in which the <code class="option">view</code> statements are listed is important, as the first statement that matches a particular client's IP address is used. For more information on this topic, refer to <a class="xref" href="s2-bind-features.html#s3-bind-features-views">「複数ビュー」</a>.
+ </div></dd></dl></div></div><div class="section" id="s3-bind-namedconf-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.1.3. コメントタグ</h4></div></div></div><a id="idm37385408" class="indexterm"></a><div class="para">
+ Additionally to statements, the <code class="filename">/etc/named.conf</code> file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to a user. The following are valid comment tags:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="literal">//</code></span></dt><dd><div class="para">
+ <code class="literal">//</code> 文字列の後ろにあるテキストは行末までがコメントとみなされます。たとえば:
+ </div><pre class="programlisting">notify yes; // notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">#</code></span></dt><dd><div class="para">
+ <code class="literal">#</code> 記号の後ろにあるテキストは行末までがコメントとみなされます。たとえば:
+ </div><pre class="programlisting">notify yes; # notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">/*</code> と <code class="literal">*/</code></span></dt><dd><div class="para">
+ <code class="literal">/*</code> と <code class="literal">*/</code> に囲まれたテキストのブロックはコメントとみなされます。たとえば:
+ </div><pre class="programlisting">notify yes; /* notify all secondary nameservers */</pre></dd></dl></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-DNS_Servers.html"><strong>戻る</strong>第12章 DNS サーバー</a></li><li class="up"><a accesskey="u" href="#"><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-bind-zone.html"><strong>次へ</strong>12.2.2. ゾーンファイルの編集</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-FTP.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-FTP.html
new file mode 100644
index 0000000..193a7aa
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-File_and_Print_Servers.html" title="第16章 ファイルサーバーおよびプリントサーバー" /><link rel="prev" href="ch-File_and_Print_Servers.html" title="第16章 ファイルサーバーおよびプリントサーバー" /><link rel="next" href="s2-ftp-servers.html" title="16.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">16.2. FTP</h2></div></div></div><a id="idm57975680" class="indexterm"></a><a id="idm48622496" 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">16.2.1. ファイル伝送プロトコル</h3></div></div></div><a id="idm36924992" 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">16.2.1.1. マルチポート、マルチモード</h4></div></div></div><a id="idm63161040" class="indexterm"></a><a id="idm40202928" class="indexterm"></a><a id="idm58582480" class="indexterm"></a><a id="idm70376736" 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. Refer to <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>第16章 ファイルサーバーおよびプリントサーバー</a></li><li class="up"><a accesskey="u" href="#"><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>16.2.2. FTP サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-autotasks-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-autotasks-additional-resources.html
new file mode 100644
index 0000000..c37f89c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-autotasks-additional-resources.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-service.html" title="19.2.6. サービスの起動と停止" /><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-service.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="idm83044240" class="indexterm"></a><a id="idm60776192" class="indexterm"></a><a id="idm60774448" class="indexterm"></a><div class="para">
+ 自動化タスクに関する詳細は、次のリソースを参照してください。
+ </div><div class="section" id="s2-autotasks-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.3.1. インストールされているドキュメント</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">cron</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 — The man page in section 1 contains an overview of the <code class="filename">crontab</code> file. The man page in section 5 contains the format for the file and some example entries.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">anacron</code> man page — contains an overview of anacron.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">anacrontab</code> man page — contains an overview of the <code class="filename">anacrontab</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/at-<em class="replaceable"><code>version</code></em>/timespec</code> contains more detailed information about the times that can be specified for cron jobs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">at</code> man page — description of <code class="command">at</code> and <code class="command">batch</code> and their command line options.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-service.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="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/17/html/System_Administrators_Guide/s1-autotasks-at-batch.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-autotasks-at-batch.html
new file mode 100644
index 0000000..d9d8b58
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-autotasks-at-batch.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="s2-autotasks-batch-configuring.html" title="19.2.2. 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="ch-Automating_Sy
stem_Tasks.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-batch-configuring.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="idm39363328" class="indexterm"></a><a id="idm60241312" class="indexterm"></a><div class="para">
+ While cron is used to schedule recurring tasks, the <code class="command">at</code> command is used to schedule a one-time task at a specific time and the <code class="command">batch</code> command is used to schedule a one-time task to be executed when the systems load average drops below 0.8.
+ </div><div class="para">
+ To use <code class="command">at</code> or <code class="command">batch</code>, the <code class="filename">at</code> RPM package must be installed, and the <code class="command">atd</code> service must be running. To determine if the package is installed, use the <code class="command">rpm -q at</code> command. To determine if the service is running, use the following command:
+ </div><pre class="screen"><code class="command">systemctl is-active atd.service</code></pre><div class="section" id="s2-autotasks-at-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.1. At ジョブの設定</h3></div></div></div><div class="para">
+ To schedule a one-time job at a specific time, 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 to execute the command.
+ </div><div class="para">
+ 引数 <em class="replaceable"><code>time</code></em> は次のいずれかを指定できます。
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ HH:MM format — For example, 04:00 specifies 4:00 a.m. If the time is already past, it is executed at the specified time the next day.
+ </div></li><li class="listitem"><div class="para">
+ midnight — 12:00 a.m. を指定します
+ </div></li><li class="listitem"><div class="para">
+ noon — 12:00 p.m. を指定します
+ </div></li><li class="listitem"><div class="para">
+ teatime — 4:00 p.m. を指定します
+ </div></li><li class="listitem"><div class="para">
+ month-name day year 形式 — たとえば、January 15 2002 は 2002 年 1 月 15 日を指定します。年はオプションです。
+ </div></li><li class="listitem"><div class="para">
+ MMDDYY, MM/DD/YY, または MM.DD.YY 形式 — たとえば、2002 年の 1 月 15 日は 011502 です。
+ </div></li><li class="listitem"><div class="para">
+ now + time — time is in minutes, hours, days, or weeks. For example, now + 5 days specifies that the command should be executed at the same time five days from now.
+ </div></li></ul></div><div class="para">
+ The time must be specified first, followed by the optional date. For more information about the time format, read the <code class="filename">/usr/share/doc/at-<em class="replaceable"><code>version</code></em>/timespec</code> text file.
+ </div><div class="para">
+ After typing the <code class="command">at</code> command with the time argument, the <code class="prompt">at></code> prompt is displayed. Type the command to execute, press <span class="keycap"><strong>Enter</strong></span>, and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Multiple commands can be specified by typing each command followed by the <span class="keycap"><strong>Enter</strong></span> key. After typing all the commands, press <span class="keycap"><strong>Enter</strong></span> to go to a blank line and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Alternatively, a shell script can be entered at the prompt, pressing <span class="keycap"><strong>Enter</strong></span> after each line in the script, and pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script i
s entered, the shell used is 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><div class="para">
+ If the set of commands or script tries to display information to standard output, the output is emailed to the user.
+ </div><div class="para">
+ Use the command <code class="command">atq</code> to view pending jobs. Refer to <a class="xref" href="s2-autotasks-at-batch-viewing.html">「保留ジョブの表示」</a> for more information.
+ </div><div class="para">
+ Usage of the <code class="command">at</code> command can be restricted. For more information, refer to <a class="xref" href="s2-autotasks-at-batch-controlling-access.html">「at と batch へのアクセスの制御」</a> for details.
+ </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="s2-autotasks-batch-configuring.html"><strong>次へ</strong>19.2.2. batch ジョブの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-check-rpm-sig.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-check-rpm-sig.html
new file mode 100644
index 0000000..0b4af55
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-check-rpm-sig.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>B.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-RPM.html" title="付録B RPM" /><link rel="prev" href="s2-rpm-verifying.html" title="B.2.7. 検証" /><link rel="next" href="s2-keys-checking.html" title="B.3.2. Verifying Signature of 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-verifying.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-keys-checking.ht
ml"><strong>次へ</strong></a></li></ul><div xml:lang="ja-JP" class="section" id="s1-check-rpm-sig" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.3. パッケージの署名を確認する</h2></div></div></div><a id="idm55563392" class="indexterm"></a><div class="para">
+ If you wish to verify that a package has not been corrupted or tampered with, you can examine just the md5sum by entering this command at the shell prompt: (where <em class="replaceable"><code><rpm_file></code></em> is the file name of the RPM package):
+ </div><pre class="screen">
+<code class="command">rpm -K --nosignature <em class="replaceable"><code><rpm_file></code></em> </code>
+</pre><div class="para">
+ The output <code class="computeroutput"><em class="replaceable"><code><rpm_file></code></em>: rsa sha1 (md5) pgp md5 OK</code> (specifically the <span class="emphasis"><em>OK</em></span> part of it) indicates that the file was not corrupted during download. To see a more verbose message, replace <code class="option">-K</code> with <code class="option">-Kvv</code> in the command.
+ </div><div class="para">
+ On the other hand, how trustworthy is the developer who created the package? If the package is <em class="firstterm">signed</em> with the developer's GnuPG <em class="firstterm">key</em>, you know that the developer really is who they say they are.
+ </div><a id="idm61566736" class="indexterm"></a><a id="idm61565104" class="indexterm"></a><a id="idm65254096" class="indexterm"></a><div class="para">
+ An RPM package can be signed using <em class="firstterm">Gnu Privacy Guard</em> (or GnuPG), to help you make certain your downloaded package is trustworthy.
+ </div><div class="para">
+ GnuPG is a tool for secure communication; it is a complete and free replacement for the encryption technology of PGP, an electronic privacy program. With GnuPG, you can authenticate the validity of documents and encrypt/decrypt data to and from other recipients. GnuPG is capable of decrypting and verifying PGP 5.<em class="replaceable"><code>x</code></em> files as well.
+ </div><div class="para">
+ During installation, GnuPG is installed by default, which enables you to immediately start using it to verify any packages that you download from the Fedora Project. Before doing so, you first need to import the correct Fedora key.
+ </div><div class="section" id="s2-keys-importing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.3.1. Importing Keys</h3></div></div></div><div class="para">
+ Fedora GnuPG keys are located in the <code class="filename">/etc/pki/rpm-gpg/</code> directory. To verify a Fedora Project package, first import the correct key based on your processor architecture:
+ </div><pre class="screen">
+<code class="command">rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-<em class="replaceable"><code>x86_64</code></em></code>
+</pre><div class="para">
+ To display a list of all keys installed for RPM verification, execute the command:
+ </div><pre class="screen">
+<code class="command">rpm -qa gpg-pubkey*</code>
+</pre><div class="para">
+ For the Fedora Project key, the output states:
+ </div><pre class="screen">gpg-pubkey-57bbccba-4a6f97af</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:
+ </div><pre class="screen">
+<code class="command">rpm -qi gpg-pubkey-57bbccba-4a6f97af</code>
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-verifying.html"><strong>戻る</strong>B.2.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="s2-keys-checking.html"><strong>次へ</strong>B.3.2. Verifying Signature of Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-additional-resources.html
new file mode 100644
index 0000000..d78bdf8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-additional-resources.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. その他のリソース</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-DHCP_Servers.html" title="第11章 DHCP サーバー" /><link rel="prev" href="s1-dhcp_for_ipv6_dhcpv6.html" title="11.5. IPv6 向け DHCP (DHCPv6)" /><link rel="next" href="ch-DNS_Servers.html" title="第12章 DNS サーバー" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-dhcp_for_ipv6_dhcpv6.html"><strong>戻る</strong></a></li><li class="next"><
a accesskey="n" href="ch-DNS_Servers.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-dhcp-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.6. その他のリソース</h2></div></div></div><a id="idm67048560" class="indexterm"></a><div class="para">
+ For additional information, refer to <em class="citetitle">The DHCP Handbook; Ralph Droms and Ted Lemon; 2003</em> or the following resources.
+ </div><div class="section" id="s2-dhcp-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.6.1. インストールされているドキュメント</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">dhcpd</code> マニュアルページ — DHCP デーモンがどうように動作するかを説明します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.conf</code> man page — Explains how to configure the DHCP configuration file; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.leases</code> マニュアルページ — リースの永続的なデータベースを説明しています。
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcp-options</code> man page — Explains the syntax for declaring DHCP options in <code class="filename">dhcpd.conf</code>; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcrelay</code> マニュアルページ — DHCP リレーエージェントおよびその設定オプションを説明しています。
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/dhcp-<em class="replaceable"><code>version</code></em>/</code> — 現在のバージョンの DHCP サービスに関するサンプルファイル、README ファイル、およびリリースノートがあります。
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>戻る</strong>11.5. IPv6 向け DHCP (DHCPv6)</a></li><li class="up"><a accesskey="u" href="#"><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-DNS_Servers.html"><strong>次へ</strong>第12章 DNS サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-configuring-client.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-configuring-client.html
new file mode 100644
index 0000000..af652dc
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-configuring-client.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>11.3. DHCP クライアントの設定</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-DHCP_Servers.html" title="第11章 DHCP サーバー" /><link rel="prev" href="dhcp-relay-agent.html" title="11.2.4. DHCP リレーエージェント" /><link rel="next" href="sect-Configuring_a_Multihomed_DHCP_Server.html" title="11.4. Configuring a Multihomed DHCP 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="dhcp-relay-agent.html"><strong>戻
る</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_a_Multihomed_DHCP_Server.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-dhcp-configuring-client"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.3. DHCP クライアントの設定</h2></div></div></div><a id="idm68026464" class="indexterm"></a><a id="idm68024864" class="indexterm"></a><div class="para">
+ DHCP クライアントを手動で設定するには、ネットワークを有効にするために <code class="filename">/etc/sysconfig/network</code> ファイルを、また <code class="filename">/etc/sysconfig/network-scripts</code> ディレクトリにある各ネットワークデバイス用の設定ファイルを変更します。このディレクトリにおいて、各デバイス <code class="filename">ifcfg-eth0</code> という名前の設定ファイルを持たなければいけません。ここで <code class="filename">eth0</code> はネットワークデバイス名です。
+ </div><div class="para">
+ <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code> ファイルは以下の行を含まなければいけません:
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ DHCP を使用するよう設定するデバイスごとに設定ファイルが必要です。
+ </div><div class="para">
+ ネットワークスクリプト用に含まれるその他のオプション:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">DHCP_HOSTNAME</code> — Only use this option if the DHCP server requires the client to specify a hostname before receiving an IP address. (The DHCP server daemon in Fedora does not support this feature.)
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">PEERDNS=<em class="replaceable"><code>answer</code></em> </code>、ここで<code class="literal"><em class="replaceable"><code>answer</code></em> </code> は以下のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — サーバーからの情報を用いて <code class="filename">/etc/resolv.conf</code> を変更します。DHCP を使用しているならば、<code class="command">yes</code> はデフォルトです。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — <code class="filename">/etc/resolv.conf</code> を変更しません。
+ </div></li></ul></div></li></ul></div><div class="note"><div class="admonition_header"><h2>高度な設定</h2></div><div class="admonition"><div class="para">
+ For advanced configurations of client DHCP options such as protocol timing, lease requirements and requests, dynamic DNS support, aliases, as well as a wide variety of values to override, prepend, or append to client-side configurations, refer to the <code class="command">dhclient</code> and <code class="command">dhclient.conf</code> man pages.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="dhcp-relay-agent.html"><strong>戻る</strong>11.2.4. DHCP リレーエージェント</a></li><li class="up"><a accesskey="u" href="#"><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_a_Multihomed_DHCP_Server.html"><strong>次へ</strong>11.4. Configuring a Multihomed DHCP Server</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-configuring-server.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-configuring-server.html
new file mode 100644
index 0000000..f615530
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp-configuring-server.html
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. DHCP サーバーの設定</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-DHCP_Servers.html" title="第11章 DHCP サーバー" /><link rel="prev" href="ch-DHCP_Servers.html" title="第11章 DHCP サーバー" /><link rel="next" href="lease-database.html" title="11.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-DHCP_Servers.html"><strong>戻る</strong></a></li><li class="next"><a accesskey
="n" href="lease-database.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-dhcp-configuring-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.2. DHCP サーバーの設定</h2></div></div></div><a id="idm55532144" class="indexterm"></a><div class="para">
+ <code class="filename">dhcp</code> パッケージは ISC DHCP サーバーを含みます。まず、<code class="systemitem">root</code> としてパッケージをインストールします:
+ </div><pre class="screen"><code class="command">yum install dhcp</code></pre><div class="para">
+ <code class="filename">dhcp</code> パッケージをインストールすることにより、単に空の設定ファイル <code class="filename">/etc/dhcp/dhcpd.conf</code> が作成されます:
+ </div><pre class="programlisting">#
+# DHCP Server Configuration file.
+# see /usr/share/doc/dhcp*/dhcpd.conf.sample
+# see dhcpd.conf(5) man page
+#</pre><div class="para">
+ サンプル設定ファイルが <code class="filename">/usr/share/doc/dhcp-<em class="replaceable"><code>version</code></em>/dhcpd.conf.sample</code> にあります。以下に説明されている <code class="filename">/etc/dhcp/dhcpd.conf</code> を設定する助けにするために、このファイルを使用すべきです。
+ </div><div class="para">
+ DHCP はクライアントの払い出しデータベースを保存するために <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> ファイルも使用します。詳細は<a class="xref" href="lease-database.html">「リースデータベース」</a>を参照してください。
+ </div><div class="section" id="config-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.2.1. 設定ファイル</h3></div></div></div><a id="idm42655520" class="indexterm"></a><a id="idm72574560" class="indexterm"></a><div class="para">
+ DHCP サーバーを設定する第一歩は、クライアントのネットワーク情報を保存する設定ファイルを作成することです。クライアントシステムのオプションや全体オプションを宣言するためにこのファイルを使用します。
+ </div><div class="para">
+ 設定ファイルはフォーマットがしやすいように余計なタブや空白行を含めることができます。キーワードは大文字小文字を区別しません。また、ハッシュ記号 (#) から始まる行はコメント行と見なされます。
+ </div><div class="para">
+ 設定ファイルのステートメントには、次の2タイプがあります：
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ パラメーター — タスクがどのように実行されるか、またはクライアントに送られるネットワーク設定オプションを述べます。
+ </div></li><li class="listitem"><div class="para">
+ 宣言 — ネットワークのトポロジーを記述します、クライアントを記述します、クライアントのアドレスを提供します、または宣言のグループにパラメーターのグループを適用します。
+ </div></li></ul></div><a id="idm66864080" class="indexterm"></a><div class="para">
+ キーワードオプションで始まるパラメーターは<em class="firstterm">オプション</em>として見なされます。これらのオプションは DHCP オプションを制御します。一方、パラメーターはオプションではない値を設定します、または、DHCP サーバーがどのように振る舞うかを制御します。
+ </div><a id="idm24357008" class="indexterm"></a><div class="para">
+ 中かっこ （{ }） で囲まれたセクションの前に宣言されたパラメータとオプションは、グローバルパラメータとみなされます。グローバルパラメータは、それ以降のすべてのセクションに適用されます。
+ </div><div class="important"><div class="admonition_header"><h2>変更を反映するには DHCP デーモンを再起動します</h2></div><div class="admonition"><div class="para">
+ 設定ファイルが変更されても、DHCP デーモンを再起動するまで、変更が有効になりません。そうするには、<code class="systemitem">root</code> としてシェルプロンプトにおいて以下を入力します:
+ </div><pre class="screen"><code class="command">systemctl restart dhcpd.service</code></pre></div></div><div class="note"><div class="admonition_header"><h2>omshell コマンドを使用する</h2></div><div class="admonition"><div class="para">
+ DHCP 設定ファイルを変更して、毎回サービスを再起動する代わりに、<code class="command">omshell</code> コマンドを使用することにより、DHCP サーバーに接続し、その設定を問い合わせ、変更する非対話式の方法が提供されます。<code class="command">omshell</code> を使用することにより、すべての変更はサーバーが実行中に反映されます。<code class="command">omshell</code> の詳細は <code class="command">omshell</code> マニュアルページを参照してください。
+ </div></div></div><div class="para">
+ <a class="xref" href="s1-dhcp-configuring-server.html#subnet">例11.1「サブネット宣言」</a>において、<code class="filename">routers</code>, <code class="filename">subnet-mask</code>, <code class="filename">domain-search</code>, <code class="filename">domain-name-servers</code>, および <code class="filename">time-offset</code> オプションはその下に宣言されたすべての <code class="filename">host</code> ステートメントに対して使用できます。
+ </div><a id="idm20181376" class="indexterm"></a><div class="para">
+ さらに、<code class="filename">subnet</code> が宣言され、<code class="filename">subnet</code> 宣言がネットワークにあるすべてのサブネットに対して含めなければいけません。もしなければ、DHCP サーバーが起動に失敗します。
+ </div><div class="para">
+ この例では、サブネットと宣言された <code class="filename">range</code> においてすべての DHCP クライアントに対する全体オプションがあります。クライアントは <code class="filename">range</code> の中にある IP アドレスが割り当てられます。
+ </div><div class="example" id="subnet"><h6>例11.1 サブネット宣言</h6><div class="example-contents"><pre class="programlisting">subnet 192.168.1.0 netmask 255.255.255.0 {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ range 192.168.1.10 192.168.1.100;
+}</pre></div></div><br class="example-break" /><div class="para">
+ 動的 IP アドレスをサブネットにあるシステムに払い出す DHCP サーバーを設定するには、値を持つ<a class="xref" href="s1-dhcp-configuring-server.html#dynamic-ip">例11.2「range パラメーター」</a>を変更します。デフォルトの払い出し期間、最大の払い出し期間、およびクライアントに対するネットワーク設定値を宣言します。この例はクライアントシステムに対して <code class="filename">range</code> 192.168.1.10 と 192.168.1.100 にある IP アドレスを割り当てます。
+ </div><div class="example" id="dynamic-ip"><h6>例11.2 range パラメーター</h6><div class="example-contents"><pre class="programlisting">default-lease-time 600;
+max-lease-time 7200;
+option subnet-mask 255.255.255.0;
+option broadcast-address 192.168.1.255;
+option routers 192.168.1.254;
+option domain-name-servers 192.168.1.1, 192.168.1.2;
+option domain-search "example.com";
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.10 192.168.1.100;
+}</pre></div></div><br class="example-break" /><div class="para">
+ To assign an IP address to a client based on the MAC address of the network interface card, use the <code class="filename">hardware ethernet</code> parameter within a <code class="filename">host</code> declaration. As demonstrated in <a class="xref" href="s1-dhcp-configuring-server.html#static-ip">例11.3「DHCP を用いた静的 IP アドレス」</a>, the <code class="filename">host apex</code> declaration specifies that the network interface card with the MAC address 00:A0:78:8E:9E:AA always receives the IP address 192.168.1.4.
+ </div><div class="para">
+ オプションのパラメーター <code class="filename">host-name</code> はホスト名をクライアントに割り当てるために使用されます。
+ </div><div class="example" id="static-ip"><h6>例11.3 DHCP を用いた静的 IP アドレス</h6><div class="example-contents"><pre class="programlisting">host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}</pre></div></div><br class="example-break" /><a id="idm46872336" class="indexterm"></a><div class="para">
+ All subnets that share the same physical network should be declared within a <code class="filename">shared-network</code> declaration as shown in <a class="xref" href="s1-dhcp-configuring-server.html#shared-network">例11.4「shared-network 宣言」</a>. Parameters within the <code class="filename">shared-network</code>, but outside the enclosed <code class="filename">subnet</code> declarations, are considered to be global parameters. The name of the <code class="filename">shared-network</code> must be a descriptive title for the network, such as using the title 'test-lab' to describe all the subnets in a test lab environment.
+ </div><div class="example" id="shared-network"><h6>例11.4 shared-network 宣言</h6><div class="example-contents"><pre class="programlisting">shared-network name {
+ option domain-search "test.redhat.com";
+ option domain-name-servers ns1.redhat.com, ns2.redhat.com;
+ option routers 192.168.0.254;
+ more parameters for EXAMPLE shared-network
+ subnet 192.168.1.0 netmask 255.255.252.0 {
+ parameters for subnet
+ range 192.168.1.1 192.168.1.254;
+ }
+ subnet 192.168.2.0 netmask 255.255.252.0 {
+ parameters for subnet
+ range 192.168.2.1 192.168.2.254;
+ }
+}</pre></div></div><br class="example-break" /><a id="idm67098064" class="indexterm"></a><div class="para">
+ As demonstrated in <a class="xref" href="s1-dhcp-configuring-server.html#group">例11.5「group 宣言」</a>, the <code class="filename">group</code> declaration is used to apply global parameters to a group of declarations. For example, shared networks, subnets, and hosts can be grouped.
+ </div><div class="example" id="group"><h6>例11.5 group 宣言</h6><div class="example-contents"><pre class="programlisting">group {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+ }
+ host raleigh {
+ option host-name "raleigh.example.com";
+ hardware ethernet 00:A1:DD:74:C3:F2;
+ fixed-address 192.168.1.6;
+ }
+}</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>サンプル設定ファイルの使用法</h2></div><div class="admonition"><div class="para">
+ The sample configuration file provided can be used as a starting point and custom configuration options can be added to it. To copy it to the proper location, use the following command:
+ </div><pre class="screen"><code class="command">cp /usr/share/doc/dhcp-<em class="replaceable"><code>version-number</code></em>/dhcpd.conf.sample /etc/dhcp/dhcpd.conf</code></pre><div class="para">
+ ... ここで <em class="replaceable"><code>version-number</code></em> は DHCP バージョン番号です。
+ </div></div></div><div class="para">
+ For a complete list of option statements and what they do, refer to the <code class="filename">dhcp-options</code> man page.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-DHCP_Servers.html"><strong>戻る</strong>第11章 DHCP サーバー</a></li><li class="up"><a accesskey="u" href="#"><strong>上に戻る</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>ホーム</strong></a></li><li class="next"><a accesskey="n" href="lease-database.html"><strong>次へ</strong>11.2.2. リースデータベース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp_for_ipv6_dhcpv6.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp_for_ipv6_dhcpv6.html
new file mode 100644
index 0000000..fcc3c07
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-dhcp_for_ipv6_dhcpv6.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.5. IPv6 向け DHCP (DHCPv6)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-DHCP_Servers.html" title="第11章 DHCP サーバー" /><link rel="prev" href="sect-Configuring_a_Multihomed_DHCP_Server.html" title="11.4. Configuring a Multihomed DHCP Server" /><link rel="next" href="s1-dhcp-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="sect-Configuring_a_Multihomed_DH
CP_Server.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-dhcp-additional-resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-dhcp_for_ipv6_dhcpv6"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.5. IPv6 向け DHCP (DHCPv6)</h2></div></div></div><a id="idm61218768" class="indexterm"></a><a id="idm61217328" class="indexterm"></a><div class="para">
+ The ISC DHCP includes support for IPv6 (DHCPv6) since the 4.x release with a DHCPv6 server, client and relay agent functionality. The server, client and relay agents support both IPv4 and IPv6. However, the client and the server can only manage one protocol at a time — for dual support they must be started separately for IPv4 and IPv6.
+ </div><div class="para">
+ DHCPv6 サーバーの設定ファイルは <code class="filename">/etc/dhcp/dhcpd6.conf</code> に見つけられます。
+ </div><div class="para">
+ The sample server configuration file can be found at <code class="filename">/usr/share/doc/dhcp-version/dhcpd6.conf.sample</code>.
+ </div><div class="para">
+ DHCPv6 サービスを開始するには、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl start dhcpd6.service</code></pre><div class="para">
+ DHCPv6 サーバーの簡単な設定ファイルはこのように見えます:
+ </div><pre class="programlisting">subnet6 2001:db8:0:1::/64 {
+ range6 2001:db8:0:1::129 2001:db8:0:1::254;
+ option dhcp6.name-servers fec0:0:0:1::1;
+ option dhcp6.domain-search "domain.example";
+}</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_a_Multihomed_DHCP_Server.html"><strong>戻る</strong>11.4. Configuring a Multihomed DHCP 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="s1-dhcp-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/17/html/System_Administrators_Guide/s1-email-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-additional-resources.html
new file mode 100644
index 0000000..df87f4c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Mail_Servers.html" title="第14章 メールサーバー" /><link rel="prev" href="s1-email-mua.html" title="14.5. メールユーザーエージェント" /><link rel="next" href="s2-email-useful-websites.html" title="14.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">14.6. その他のリソース</h2></div></div></div><a id="idm29898800" class="indexterm"></a><a id="idm50448704" class="indexterm"></a><a id="idm50446960" class="indexterm"></a><a id="idm50445216" 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">14.6.1. インストールされているドキュメント</h3></div></div></div><a id="idm20254128" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Information on configuring Sendmail is included with the <code class="filename">sendmail</code> and <code class="filename">sendmail-cf</code> 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-<em class="replaceable"><code>version-number</code></em> </code> — Contains a large amount of information about ways to configure Postfix. Replace <em class="replaceable"><code>version-number</code></em> with the version number of Postfix.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/fetchmail-<em class="replaceable"><code>version-number</code></em> </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. Replace <em class="replaceable"><code>version-number</code></em> with the version number of Fetchmail.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/procmail-<em class="replaceable"><code>version-number</code></em> </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. Replace <em class="replaceable"><code>version-number</code></em> with the version number of Procmail.
+ </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-<em class="replaceable"><code>version-number</code></em>/</code> — Contains a large amount of information pertaining to SpamAssassin. Replace <em class="replaceable"><code>version-number</code></em> with the version number of the <code class="filename">spamassassin</code> package.
+ </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>14.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>14.6.2. 役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-mda.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-mda.html
new file mode 100644
index 0000000..cf00b51
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-mda.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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Mail_Servers.html" title="第14章 メールサーバー" /><link rel="prev" href="s2-email-switchmail.html" title="14.3.4. Mail Transport Agent (MTA) の設定" /><link rel="next" href="s2-email-procmail-recipes.html" title="14.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">14.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="idm46275056" class="indexterm"></a><a id="idm58653536" 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">14.4.1. Procmail の設定</h3></div></div></div><a id="idm27331600" class="indexterm"></a><a id="idm27329856" 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">
+ たとえば、ユーザーの <code class="filename">.procmailrc</code> ファイルにある行は次のように見えるでしょう:
+ </div><pre class="programlisting">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="command">#</code>).
+ </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>, which is the login name; <code class="command">HOME</code>, which is the location of the home directory; and <code class="command">SHELL</code>, which is the default shell.
+ </div><div class="para">
+ A comprehensive explanation of all environments variables, as well as 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>14.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>14.4.2. Procmail レシピ</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-mta.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-mta.html
new file mode 100644
index 0000000..8b67f9b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-mta.html
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Mail_Servers.html" title="第14章 メールサーバー" /><link rel="prev" href="s2-email-types-mua.html" title="14.2.3. メール ユーザー エージェント" /><link rel="next" href="s2-email-mta-sendmail.html" title="14.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">14.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, although it is easy to switch the default MTA to Sendmail. To switch the default MTA to Sendmail, as <code class="systemitem">root</code>, you can either uninstall Postfix or use the following command 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/disable the desired service:
+ </div><pre class="screen"><code class="command">systemctl enable|disable <em class="replaceable"><code>service</code></em>.service</code></pre><div class="section" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">14.3.1. Postfix</h3></div></div></div><a id="idm24311888" class="indexterm"></a><a id="idm61959680" class="indexterm"></a><div class="para">
+ 元来、 IBM のセキュリティ専門家でありプログラマーの Wietse Venema によって開発された Postfix は、安全で迅速で設定が容易であるようにデザインされた Sendmail 対応の MTA です。
+ </div><div class="para">
+ セキュリティを改善する為に、 Postfix はモジュラーデザインを使用して、 <em class="firstterm">master</em> デーモンによって制限付の権限を持つ小規模のプロセスが起動できるようにします。より小規模で、権限の低いプロセスは、メール配送の各種段階における特定のタスクを実行し、外部攻撃からの影響を低減する為に変更したルート環境で動作します。
+ </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">14.3.1.1. Postfix のデフォルトインストール</h4></div></div></div><a id="idm41743312" class="indexterm"></a><div class="para">
+ The Postfix executable is <code class="filename">/usr/sbin/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, refer to <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.service</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">14.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="command">#</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 hostname 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">14.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">14.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> 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 created 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">
+ <code class="filename">/etc/postfix/ldap-aliases.cf</code> ファイルは、<code class="systemitem">LDAP</code> <code class="systemitem">SSL</code> および <code class="systemitem">STARTTLS</code> を有効化するパラメーターを含め、さまざまなパラメーターを指定できます。詳細は<code class="command">ldap_table(5)</code>マニュアルページを参照してください。
+ </div></div></div><div class="para">
+ <code class="systemitem">LDAP</code> の詳細は<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>14.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>14.3.2. Sendmail</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-mua.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-mua.html
new file mode 100644
index 0000000..1ad3cb2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Mail_Servers.html" title="第14章 メールサーバー" /><link rel="prev" href="s2-email-procmail-recipes.html" title="14.4.2. Procmail レシピ" /><link rel="next" href="s1-email-additional-resources.html" title="14.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">14.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">14.5.1. 通信のセキュリティ</h3></div></div></div><div class="para">
+ Popular MUAs included with Fedora, such as <span class="application"><strong>Evolution</strong></span> and <code class="command">mutt</code> offer SSL-encrypted email sessions.
+ </div><a id="idm50264800" class="indexterm"></a><div class="para">
+ Like any other service that flows over a network unencrypted, important email information, such as usernames, 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 usernames 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">14.5.1.1. 安全な電子メールクライアント</h4></div></div></div><a id="idm44003728" 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">14.5.1.2. 安全な電子クライアント通信</h4></div></div></div><a id="idm20150544" class="indexterm"></a><a id="idm61032448" 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">
+ 自己署名付き証明書は、テスト目的の為にのみ使用すべきものです。生産環境で使用するサーバーはすべて CA により認可された SSL 証明書を使用すべきです。
+ </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.conf</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">
+ Execute the <code class="command">systemctl restart dovecot.service</code> command to restart the <code class="command">dovecot</code> daemon.
+ </div><div class="para">
+ Alternatively, the <code class="command">stunnel</code> command can be used as an SSL 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">yum install stunnel</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</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">/usr/bin/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>, refer to the <code class="command">stunnel</code> man page or the documents in the <code class="filename">/usr/share/doc/stunnel-<em class="replaceable"><code>version-number</code></em> </code>/ directory, where <em class="replaceable"><code>version-number</code></em> is the version number of <code class="command">stunnel</code>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-procmail-recipes.html"><strong>戻る</strong>14.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>14.6. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-types.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-email-types.html
new file mode 100644
index 0000000..4fe2dd7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Mail_Servers.html" title="第14章 メールサーバー" /><link rel="prev" href="ch-Mail_Servers.html" title="第14章 メールサーバー" /><link rel="next" href="s2-email-types-mda.html" title="14.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">14.2. 電子メールプログラム分類</h2></div></div></div><a id="idm31950880" 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">14.2.1. メール転送エージェント (Mail Transport Agent)</h3></div></div></div><a id="idm31947008" class="indexterm"></a><a id="idm72922880" class="indexterm"></a><a id="idm72921168" 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, refer to <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>第14章 メールサーバー</a></li><li class="up"><a accesskey="u" href="#"><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>14.2.2. メール配送エージェント (Mail Delivery Agent)</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-configuration.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-configuration.html
new file mode 100644
index 0000000..a0a1e1b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-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>23.2. Configuring the kdump 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-kdump.html" title="第23章 The kdump Crash Recovery Service" /><link rel="prev" href="ch-kdump.html" title="第23章 The kdump Crash Recovery Service" /><link rel="next" href="s2-kdump-configuration-gui.html" title="23.2.2. Using the Kernel Dump Configuration Utility" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump.html"><strong>戻る</strong><
/a></li><li class="next"><a accesskey="n" href="s2-kdump-configuration-gui.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-kdump-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">23.2. Configuring the kdump Service</h2></div></div></div><div class="para">
+ There are three common means of configuring the <code class="systemitem">kdump</code> service: at the first boot, using the <span class="application"><strong>Kernel Dump Configuration</strong></span> graphical utility, and doing so manually on the command line.
+ </div><a id="idm20093312" class="indexterm"></a><div class="important"><div class="admonition_header"><h2>Disable IOMMU on Intel chipsets</h2></div><div class="admonition"><div class="para">
+ A limitation in the current implementation of the <code class="systemitem">Intel IOMMU</code> driver can occasionally prevent the <code class="systemitem">kdump</code> service from capturing the core dump image. To use <code class="systemitem">kdump</code> on Intel architectures reliably, it is advised that the IOMMU support is disabled.
+ </div></div></div><div class="section" id="s2-kdump-configuration-firstboot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.2.1. Configuring the kdump at First Boot</h3></div></div></div><div class="para">
+ When the system boots for the first time, the <span class="application"><strong>firstboot</strong></span> application is launched to guide the user through the initial configuration of the freshly installed system. To configure <code class="systemitem">kdump</code>, navigate to the <span class="guilabel"><strong>Kdump</strong></span> section and follow the instructions below.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure the system has enough memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_17.html#sect-Release_Notes-Hardware_Overview"><em class="citetitle">Hardware Overview</em></a> section of the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><em class="citetitle">Fedora 17 Release Notes</em></a>. When the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ </div></div></div><div class="section" id="s3-kdump-configuration-firstboot-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.1.1. サービスの有効化</h4></div></div></div><a id="idm31205488" class="indexterm"></a><div class="para">
+ To allow the <code class="systemitem">kdump</code> daemon to start at boot time, select the <span class="guilabel"><strong>Enable kdump?</strong></span> checkbox. This will enable the service and start it for the current session. Similarly, unselecting the checkbox will disable it for and stop the service immediately.
+ </div></div><div class="section" id="s3-kdump-configuration-firstboot-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.1.2. Configuring the Memory Usage</h4></div></div></div><a id="idm60500560" class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel, click the up and down arrow buttons next to the <span class="guilabel"><strong>Kdump Memory</strong></span> field to increase or decrease the value. Notice that the <span class="guilabel"><strong>Usable System Memory</strong></span> field changes accordingly showing you the remaining memory that will be available to the system.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-kdump.html"><strong>戻る</strong>第23章 The kdump Crash Recovery 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-kdump-configuration-gui.html"><strong>次へ</strong>23.2.2. Using the Kernel Dump Configuration Utili...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-crash.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-crash.html
new file mode 100644
index 0000000..f005342
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-crash.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>23.3. Analyzing the Core Dump</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-kdump.html" title="第23章 The kdump Crash Recovery Service" /><link rel="prev" href="s2-kdump-configuration-testing.html" title="23.2.4. Testing the Configuration" /><link rel="next" href="s2-kdump-crash-log.html" title="23.3.2. Displaying the Message Buffer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump-configuration-testing.html"><strong>æˆ
»ã‚‹</strong></a></li><li class="next"><a accesskey="n" href="s2-kdump-crash-log.html"><strong>次ã¸</strong></a></li></ul><div class="section" id="s1-kdump-crash"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">23.3. Analyzing the Core Dump</h2></div></div></div><a id="idm66578464" class="indexterm"></a><div class="para">
+ To determine the cause of the system crash, you can use the <span class="application"><strong>crash</strong></span> utility, which provides an interactive prompt very similar to the GNU Debugger (GDB). This utility allows you to interactively analyze a running Linux system as well as a core dump created by <code class="systemitem">netdump</code>, <code class="systemitem">diskdump</code>, <code class="systemitem">xendump</code>, or <code class="systemitem">kdump</code>.
+ </div><a id="idm43938896" class="indexterm"></a><div class="note"><div class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div class="admonition"><div class="para">
+ To analyze the <code class="filename">vmcore</code> dump file, you must have the <span class="package">crash</span> and <span class="package">kernel-debuginfo</span> packages installed. To install these packages, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install crash</code>
+<code class="command">debuginfo-install kernel</code></pre><div class="para">
+ For more information on how to install new packages in Fedora, refer to <a class="xref" href="sec-Installing.html">「パッケージのインストール」</a>.
+ </div></div></div><div class="section" id="s2-kdump-crash-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.1. Running the crash Utility</h3></div></div></div><a id="idm33455632" class="indexterm"></a><div class="para">
+ To start the utility, type the command in the following form at a shell prompt:
+ </div><pre class="synopsis"><code class="command">crash</code> <code class="filename">/var/crash/<em class="replaceable"><code>timestamp</code></em>/vmcore</code> <code class="filename">/usr/lib/debug/lib/modules/<em class="replaceable"><code>kernel</code></em>/vmlinux</code></pre><div class="para">
+ Note that the <em class="replaceable"><code>kernel</code></em> version should be the same that was captured by <code class="systemitem">kdump</code>. To find out which kernel you are currently running, use the <code class="command">uname -r</code> command.
+ </div><div class="example" id="ex-kdump-crash-running"><h6>例23.1 Running the crash utility</h6><div class="example-contents"><pre class="screen">~]# <code class="command">crash /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux \</code>
+<code class="command">/var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore</code>
+
+crash 5.0.0-23.el6
+Copyright (C) 2002-2010 Red Hat, Inc.
+Copyright (C) 2004, 2005, 2006 IBM Corporation
+Copyright (C) 1999-2006 Hewlett-Packard Co
+Copyright (C) 2005, 2006 Fujitsu Limited
+Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
+Copyright (C) 2005 NEC Corporation
+Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
+Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
+This program is free software, covered by the GNU General Public License,
+and you are welcome to change it and/or distribute copies of it under
+certain conditions. Enter "help copying" to see the conditions.
+This program has absolutely no warranty. Enter "help warranty" for details.
+
+GNU gdb (GDB) 7.0
+Copyright (C) 2009 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law. Type "show copying"
+and "show warranty" for details.
+This GDB was configured as "i686-pc-linux-gnu"...
+
+ KERNEL: /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux
+ DUMPFILE: /var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore [PARTIAL DUMP]
+ CPUS: 4
+ DATE: Wed Aug 25 08:44:47 2010
+ UPTIME: 00:09:02
+LOAD AVERAGE: 0.00, 0.01, 0.00
+ TASKS: 140
+ NODENAME: hp-dl320g5-02.lab.bos.redhat.com
+ RELEASE: 2.6.32-69.el6.i686
+ VERSION: #1 SMP Tue Aug 24 10:31:45 EDT 2010
+ MACHINE: i686 (2394 Mhz)
+ MEMORY: 8 GB
+ PANIC: "Oops: 0002 [#1] SMP " (check log for details)
+ PID: 5591
+ COMMAND: "bash"
+ TASK: f196d560 [THREAD_INFO: ef4da000]
+ CPU: 2
+ STATE: TASK_RUNNING (PANIC)
+
+crash></pre></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-configuration-testing.html"><strong>戻る</strong>23.2.4. Testing the 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-kdump-crash-log.html"><strong>次へ</strong>23.3.2. Displaying the Message Buffer</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-resources.html
new file mode 100644
index 0000000..b610816
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kdump-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>23.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-kdump.html" title="第23章 The kdump Crash Recovery Service" /><link rel="prev" href="s2-kdump-crash-exit.html" title="23.3.7. Exiting the Utility" /><link rel="next" href="s2-kdump-resources-online.html" title="23.4.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="s2-kdump-crash-exit.html"><strong>戻る</strong></a></li><l
i class="next"><a accesskey="n" href="s2-kdump-resources-online.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-kdump-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">23.4. その他のリソース</h2></div></div></div><div class="section" id="s2-kdump-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.4.1. インストールされているドキュメント</h3></div></div></div><a id="idm68138816" class="indexterm"></a><a id="idm18120912" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>kdump.conf</strong></span>(5) — a manual page for the <code class="filename">/etc/kdump.conf</code> configuration file containing the full documentation of available options.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>makedumpfile</strong></span>(8) — a manual page for the <code class="command">makedumpfile</code> core collector.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>kexec</strong></span>(8) — a manual page for <span class="application"><strong>kexec</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>crash</strong></span>(8) — a manual page for the <span class="application"><strong>crash</strong></span> utility.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kexec-tools-<em class="replaceable"><code>version</code></em>/kexec-kdump-howto.txt</code> — an overview of the <code class="systemitem">kdump</code> and <span class="application"><strong>kexec</strong></span> installation and usage.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-exit.html"><strong>戻る</strong>23.3.7. Exiting the Utility</a></li><li class="up"><a accesskey="u" href="#"><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-kdump-resources-online.html"><strong>次へ</strong>23.4.2. 役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-boot-loader.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-boot-loader.html
new file mode 100644
index 0000000..0652928
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-boot-loader.html
@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. ブートローダの確認</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="第21章 カーネルをアップグレードする" /><link rel="prev" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="21.5. 初期RAMディスクイメージの確認" /><link rel="next" href="s2-kernel-boot-loader-iseries.html" title="21.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">21.6. ブートローダの確認</h2></div></div></div><a id="idm52419664" 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 may 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 "Refer to" link to jump to the correct instructions for your system.
+ </div><div class="table" id="tb-grub-arch-loaders"><h6>表21.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="">
+ Refer to
+ </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">21.6.1. Configuring the GRUB 2 Boot Loader</h3></div></div></div><a id="idm69720592" class="indexterm"></a><a id="idm69719152" class="indexterm"></a><div class="para">
+ Fedora 17 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 17 with Linux kernel 3.4.0-1.fc17.x86_64:
+ </div><pre class="programlisting">menuentry 'Fedora (3.4.0-1.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-77ba9149-751a-48e0-974f-ad94911734b9' {
+ 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' 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ else
+ search --no-floppy --fs-uuid --set=root 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ fi
+ echo 'Loading Fedora (3.4.0-1.fc17.x86_64)'
+ linux /vmlinuz-3.4.0-1.fc17.x86_64 root=/dev/mapper/vg_fedora-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_fedora/lv_swap KEYTABLE=us rd.lvm.lv=vg_fedora/lv_root rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
+ echo 'Loading initial ramdisk ...'
+ initrd /initramfs-3.4.0-1.fc17.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">initrd /initramfs-3.4.0-1.fc17.x86_64.img</code> line means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-3.4.0-1.fc17.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">手順21.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>21.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>21.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/17/html/System_Administrators_Guide/s1-kernel-download.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-download.html
new file mode 100644
index 0000000..c8c1e21
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>21.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="第21章 カーネルをアップグレードする" /><link rel="prev" href="s1-kernel-preparing.html" title="21.2. アップグレードの準備" /><link rel="next" href="s1-kernel-perform-upgrade.html" title="21.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">21.3. アップグレードされたカーネルをダウンロードする</h2></div></div></div><a id="idm57117888" class="indexterm"></a><a id="idm57116448" class="indexterm"></a><a id="idm57115040" class="indexterm"></a><a id="idm48652720" class="indexterm"></a><div class="para">
+ システムに対して更新されたカーネルがあるかどうかを確認するには、いくつかの方法があります。
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Security Advisories — Refer to <a href="http://fedoraproject.org/wiki/FSA">http://fedoraproject.org/wiki/FSA</a> 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.fedoraproject.org/updates/</a>.
+ </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>21.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>21.4. アップグレードの実行</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html
new file mode 100644
index 0000000..bc7d000
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-modules-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>22.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="第22章 Working with Kernel Modules" /><link rel="prev" href="sec-Using_Channel_Bonding.html" title="22.7.2. Using Channel Bonding" /><link rel="next" href="s2-kernel-modules-additional-resources-websites.html" title="22.8.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="sec-Using_Cha
nnel_Bonding.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-kernel-modules-additional-resources-websites.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">22.8. その他のリソース</h2></div></div></div><div class="para">
+ For more information on kernel modules and their utilities, refer to the following resources.
+ </div><div class="section" id="s2-kernel-modules-additional-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.8.1. インストールされているドキュメント</h3></div></div></div><div class="para">
+ There is a number of manual pages for various utilities related to the kernel modules:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">man lsmod</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">lsmod</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man modinfo</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">modinfo</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man modprobe</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">modprobe</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man rmmod</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">rmmod</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ethtool</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">ethtool</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man mii-tool</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">mii-tool</code> command.
+ </div></dd></dl></div><div class="para">
+ Additionally, you can refer to the documentation provided by the <span class="package">kernel-doc</span> package:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/</code></span></dt><dd><div class="para">
+ This directory contains information on the kernel, kernel modules, and their respective parameters. Note that before accessing the kernel documentation, you must run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install kernel-doc</code></pre></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Channel_Bonding.html"><strong>戻る</strong>22.7.2. Using Channel Bonding</a></li><li class="up"><a accesskey="u" href="#"><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-modules-additional-resources-websites.html"><strong>次へ</strong>22.8.2. 役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html
new file mode 100644
index 0000000..eab00e7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>21.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="第21章 カーネルをアップグレードする" /><link rel="prev" href="s1-kernel-download.html" title="21.3. アップグレードされたカーネルをダウンロードする" /><link rel="next" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="21.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">21.4. アップグレードの実行</h2></div></div></div><a id="idm21955232" 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. Refer to <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>21.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>21.5. 初期RAMディスクイメージの確認</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-preparing.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-preparing.html
new file mode 100644
index 0000000..710188d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-kernel-preparing.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>21.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="第21章 カーネルをアップグレードする" /><link rel="prev" href="ch-Manually_Upgrading_the_Kernel.html" title="第21章 カーネルをアップグレードする" /><link rel="next" href="s1-kernel-download.html" title="21.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">21.2. アップグレードの準備</h2></div></div></div><a id="idm31058560" class="indexterm"></a><a id="idm31057600" class="indexterm"></a><a id="idm31055680" class="indexterm"></a><a id="idm31054240" 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, the system cannot be booted into Fedora without working boot media.
+ </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>. Refer to <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">yum 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 may differ:
+ </div><pre class="screen">~]# <code class="command">yum list installed "kernel-*"</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+kernel.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
+kernel.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing
+kernel-doc.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
+kernel-doc.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing
+kernel-headers.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
+kernel-headers.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing</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. Refer to <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>第21章 カーネルをアップグレードする</a></li><li class="up"><a accesskey="u" href="#"><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>21.3. アップグレードされたカーネルをダウンロードする</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-log-files-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-log-files-additional-resources.html
new file mode 100644
index 0000000..6e5c6f3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-log-files-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>18.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-logfiles-examining.html" title="18.5. ログファイルを監視する" /><link rel="next" href="s2-log-files-useful-websites.html" title="18.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-logfi
les-examining.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-log-files-useful-websites.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.6. その他のリソース</h2></div></div></div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span>, <span class="application"><strong>logrotate</strong></span> および一般的なログファイルに関する詳細を知るには、以下のリソースを参照してください。
+ </div><div class="section" id="s2-log-files-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.6.1. インストールされているドキュメント</h3></div></div></div><a id="idm47509584" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rsyslogd</code> manual page — <code class="command">rsyslogd</code> およびその多くのオプションに関する詳細を知るには <code class="command">man rsyslogd</code> を入力してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">rsyslog.conf</code> manual page — <code class="command">/etc/rsyslog.conf</code> 設定ファイルおよびその多くのオプションに関する詳細を知るには <code class="command">man rsyslog.conf</code> と入力してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em>/ </code> — <span class="package">rsyslog</span> パッケージのインストール後、このディレクトリーに <code class="systemitem">html</code> 形式の広範囲なドキュメントがあります。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">logrotate</code> マニュアルページ — <code class="command">logrotate</code> および多くのオプションに関する詳細を知るには <code class="command">man logrotate</code> と入力してください。
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-examining.html"><strong>戻る</strong>18.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-log-files-useful-websites.html"><strong>次へ</strong>18.6.2. 役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-adding.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-adding.html
new file mode 100644
index 0000000..6cdf16f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-logfiles-viewing.html" title="18.3. ログファイルの表示" /><link rel="next" href="s1-logfiles-examining.html" title="18.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-logfiles-viewin
g.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-examining.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-logfiles-adding"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.4. ログファイルの追加</h2></div></div></div><div class="para">
+ To add a log file you wish 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 wish to view.<a class="xref" href="s1-logfiles-adding.html#fig-redhat-logviewer-add">図18.5「Log File Viewer — 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/system-log-viewer-add.png" alt="Log File Viewer — adding a log file" /><div class="longdesc"><div class="para">
+ Log File Viewer — adding a log file
+ </div></div></div></div><h6>図18.5 Log File Viewer — 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>Log File Viewer</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-logfiles-viewing.html"><strong>戻る</strong>18.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-logfiles-examining.html"><strong>次へ</strong>18.5. ログファイルを監視する</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-examining.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-examining.html
new file mode 100644
index 0000000..a639cdd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-logfiles-adding.html" title="18.4. ログファイルの追加" /><link rel="next" href="s1-log-files-additional-resources.html" title="18.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-logfiles-addi
ng.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="s1-logfiles-examining"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.5. ログファイルを監視する</h2></div></div></div><a id="idm65223936" class="indexterm"></a><a id="idm24681168" class="indexterm"></a><div class="para">
+ <span class="application"><strong>Log File Viewer</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="s1-logfiles-examining.html#fig-redhat-logviewer-monitoring">図18.6「Log File Viewer — new log alert」</a> illustrates a new alert in the <span class="guilabel"><strong>yum.log</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/system-log-viewer-alerts.png" alt="Log File Viewer — new log alert" /><div class="longdesc"><div class="para">
+ Log File Viewer — new log alert
+ </div></div></div></div><h6>図18.6 Log File Viewer — new log alert</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-adding.html"><strong>戻る</strong>18.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-log-files-additional-resources.html"><strong>次へ</strong>18.6. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-locating.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-locating.html
new file mode 100644
index 0000000..957edfe
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-locating.html
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. ログファイルを探す</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="s1-logfiles-viewing.html" title="18.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-Viewing_and_Managing_Log_Files.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-viewing.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-logfiles-locating"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.2. ログファイルを探す</h2></div></div></div><a id="idm17905760" 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="idm17901744" class="indexterm"></a><a id="idm59611312" 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 timestamp 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 class="section" id="configuring-logrotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.2.1. logrotate の設定法</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 the duration of 4 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 on a weekly basis. 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 just-rotated log files are to be mailed, instead of the about-to-expire 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, refer to the <code class="command">logrotate</code> man page (<code class="command">man logrotate</code>).
+ </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="s1-logfiles-viewing.html"><strong>次へ</strong>18.3. ログファイルの表示</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-viewing.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-viewing.html
new file mode 100644
index 0000000..f9a30e9
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-logfiles-viewing.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. ログファイルの表示</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-logfiles-locating.html" title="18.2. ログファイルを探す" /><link rel="next" href="s1-logfiles-adding.html" title="18.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-logfiles-locating.html"
><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-adding.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-logfiles-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.3. ログファイルの表示</h2></div></div></div><a id="idm50315344" class="indexterm"></a><div class="para">
+ Most log files are 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, <code class="systemitem">root</code> privileges are required to read most log files.
+ </div><a id="idm50311360" class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span class="application"><strong>Log File Viewer</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>Log File Viewer</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">yum install gnome-system-log</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は <a class="xref" href="sec-Installing.html">「パッケージのインストール」</a> を参照してください。
+ </div></div></div><div class="para">
+ After you have installed the <span class="package">gnome-system-log</span> package, you can open the <span class="application"><strong>Log File Viewer</strong></span> by selecting <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Log File Viewer</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, 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-logfiles-viewing.html#fig-redhat-logviewer">図18.1「ログファイルビューアー」</a>.
+ </div><a id="idm37728800" class="indexterm"></a><a id="idm36600864" class="indexterm"></a><div class="figure" id="fig-redhat-logviewer"><div class="figure-contents"><div class="mediaobject"><img src="images/system-log-viewer.png" alt="ログファイルビューアー" /><div class="longdesc"><div class="para">
+ ログファイルビューアー
+ </div></div></div></div><h6>図18.1 ログファイルビューアー</h6></div><br class="figure-break" /><a id="idm67200704" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Log File Viewer</strong></span> application lets you filter any existing log file. Click on <span class="guimenuitem"><strong>Filters</strong></span> from the menu and select <span class="guimenuitem"><strong>Manage Filters</strong></span> to define or edit your desired filter.
+ </div><div class="figure" id="fig-redhat-filters"><div class="figure-contents"><div class="mediaobject"><img src="images/system-log-viewer-filters-manage.png" alt="ログファイルビューアー — フィルター" /><div class="longdesc"><div class="para">
+ ログファイルビューアー — フィルター
+ </div></div></div></div><h6>図18.2 ログファイルビューアー — フィルター</h6></div><br class="figure-break" /><div class="para">
+ フィルターを追加または編集することにより、<a class="xref" href="s1-logfiles-viewing.html#fig-redhat-filter-sample">図18.3「ログファイルビューアー — フィルターの定義」</a>に示されたとおり、そのパラメーターを定義できます。
+ </div><div class="figure" id="fig-redhat-filter-sample"><div class="figure-contents"><div class="mediaobject"><img src="images/system-log-viewer-filters-define.png" alt="ログファイルビューアー — フィルターの定義" /><div class="longdesc"><div class="para">
+ ログファイルビューアー — フィルターの定義
+ </div></div></div></div><h6>図18.3 ログファイルビューアー — フィルターの定義</h6></div><br class="figure-break" /><div class="para">
+ フィルターを定義するとき、以下のパラメーターを編集できます:
+ </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, you may select it 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/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/system-log-viewer-filters-enable.png" alt="Log File Viewer — enabling a filter" /><div class="longdesc"><div class="para">
+ Log File Viewer — enabling a filter
+ </div></div></div></div><h6>図18.4 Log File Viewer — enabling a filter </h6></div><br class="figure-break" /><div class="para">
+ When you check 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-locating.html"><strong>戻る</strong>18.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-logfiles-adding.html"><strong>次へ</strong>18.4. ログファイルの追加</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-control.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-control.html
new file mode 100644
index 0000000..b7eec11
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-control.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Network_Interfaces.html" title="第7章 ネットワーク・インターフェース" /><link rel="prev" href="s2-networkscripts-interfaces-other.html" title="7.2.7. 他のインターフェース" /><link rel="next" href="s1-networkscripts-static-routes.html" title="7.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" hr
ef="s2-networkscripts-interfaces-other.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-static-routes.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-networkscripts-control"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. インターフェース制御スクリプト</h2></div></div></div><a id="idm33392672" class="indexterm"></a><a id="idm33389968" class="indexterm"></a><a id="idm39095952" class="indexterm"></a><a id="idm39094208" class="indexterm"></a><div class="para">
+ インターフェース制御スクリプトはシステムインターフェースを活性化および非活性化します。<code class="filename">/etc/sysconfig/network-scripts/</code> ディレクトリーに置かれている制御スクリプトにおいて呼び出す 2 つの主なインターフェース制御スクリプトがあります: <code class="command">/sbin/ifdown</code> および <code class="command">/sbin/ifup</code>。
+ </div><div class="para">
+ <code class="filename">ifup</code> および <code class="filename">ifdown</code> インターフェーススクリプトは、<code class="filename">/sbin/</code> ディレクトリにあるスクリプトへのシンボリックリンクです。これらのスクリプトのいずれかが呼び出されるとき、次のように、インターフェースの値が指定される必要があります:
+ </div><pre class="screen"><code class="command">ifup eth0</code></pre><div class="warning"><div class="admonition_header"><h2>インターフェースのスクリプト ifup と ifdown を使う</h2></div><div class="admonition"><div class="para">
+ <code class="filename">ifup</code> および <code class="filename">ifdown</code> インターフェーススクリプトは、ユーザーがネットワークインターフェースを起動または停止するために使用する唯一のスクリプトです。
+ </div><div class="para">
+ 参考のために以下にスクリプトの例をあげておきます。
+ </div></div></div><div class="para">
+ ネットワークインターフェースが起動するプロセス中にさまざまなネットワーク初期化作業を実行するために使用される2つのファイルが、<code class="filename">/etc/rc.d/init.d/functions</code> および <code class="filename">/etc/sysconfig/network-scripts/network-functions</code> です。詳細は<a class="xref" href="s1-networkscripts-functions.html">「ネットワーク機能ファイル」</a>を参照してください。
+ </div><div class="para">
+ インターフェースが指定され、要求を実行しているユーザーがインターフェースを制御することが許可された後、適切なスクリプトがインターフェースを起動または停止します。以下は、<code class="filename">/etc/sysconfig/network-scripts/</code> ディレクトリーの中にある一般的なインターフェース制御スクリプトです:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">ifup-aliases</code></span></dt><dd><div class="para">
+ 複数の IP アドレスが 1 つのインターフェイスに関連付けられている場合、インターフェース設定ファイルから IP エイリアスを設定します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-ippp</code> と <code class="filename">ifdown-ippp</code></span></dt><dd><div class="para">
+ ISDN インターフェースをアップとダウンする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-ipv6</code> と <code class="filename">ifdown-ipv6</code></span></dt><dd><div class="para">
+ IPv6 インターフェースをアップとダウンする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-plip</code></span></dt><dd><div class="para">
+ PLIP インターフェースをアップする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-plusb</code></span></dt><dd><div class="para">
+ ネットワーク接続用の USB インターフェースをアップする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-post</code> と <code class="filename">ifdown-post</code></span></dt><dd><div class="para">
+ これらには、インターフェイスを立ち上げた後、及び停止した後に実行されるコマンドが含まれています。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-ppp</code> と <code class="filename">ifdown-ppp</code></span></dt><dd><div class="para">
+ PPP インターフェースをアップとダウンする為に使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-routes</code></span></dt><dd><div class="para">
+ デバイスの静的ルートを、そのインターフェイスがアップするときに追加します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifdown-sit</code> と <code class="filename">ifup-sit</code></span></dt><dd><div class="para">
+ IPv4 接続内にある IPv6 トンネルのアップ/ダウンに関連した機能呼び出しを含みます。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifup-wireless</code></span></dt><dd><div class="para">
+ ワイヤレスインターフェースをアップする為に使用します。
+ </div></dd></dl></div><div class="warning"><div class="admonition_header"><h2>ネットワーク スクリプトの修正と削除をする際は注意をしてください!</h2></div><div class="admonition"><div class="para">
+ Removing or modifying any scripts in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory can cause interface connections to act irregularly or fail. Only advanced users should modify scripts related to a network interface.
+ </div></div></div><div class="para">
+ The easiest way to manipulate all network scripts simultaneously is to use the <code class="command">systemctl</code> command on the network service (<code class="filename">/etc/rc.d/init.d/network</code>), as illustrated by the following command:
+ </div><pre class="screen"><code class="command">systemctl <em class="replaceable"><code>action</code></em> network.service</code></pre><div class="para">
+ ここで、<em class="replaceable"><code>action</code></em> は <code class="command">start</code>, <code class="command">stop</code>, または <code class="command">restart</code> のどれかです。
+ </div><div class="para">
+ 設定したデバイスと現在アクティブになっているネットワーク インターフェースの一覧を表示するには、次のコマンドを使用します：
+ </div><pre class="screen"><code class="command"> systemctl status network.service</code></pre><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ The older SysV service commands, such as <span class="quote">「<span class="quote">service network status</span>」</span> are considered deprecated but will still work. The SysV services can define their status in an arbitrary fashion so the output of the status command is not considered predictable over time. The SysV commands are retained for compatibility purposes. The <span class="application"><strong>/sbin/service</strong></span> utility will call <span class="application"><strong>systemctl</strong></span> when necessary.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-other.html"><strong>戻る</strong>7.2.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-networkscripts-static-routes.html"><strong>次へ</strong>7.4. スタティック ルートの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-functions.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-functions.html
new file mode 100644
index 0000000..581af6d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-functions.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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Network_Interfaces.html" title="第7章 ネットワーク・インターフェース" /><link rel="prev" href="s1-networkscripts-static-routes.html" title="7.4. スタティック ルートの設定" /><link rel="next" href="s1-networkscripts-resources.html" title="7.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-networks
cripts-static-routes.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-networkscripts-functions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.5. ネットワーク機能ファイル</h2></div></div></div><a id="idm66641008" class="indexterm"></a><div class="para">
+ Fedora は、インターフェースを起動および停止するために使用される、重要な一般的な機能を含むいくつかのファイルを使用します。それぞれのインターフェース制御ファイルにこれらの機能を強制的に含めるよりは、必要なときに呼び出されるいくつかのファイルに一緒にグループ化します。
+ </div><div class="para">
+ <code class="filename">/etc/sysconfig/network-scripts/network-functions</code> ファイルは最も一般的に使用される IPv4 機能が含まれます。これは多くのインターフェース制御スクリプトにとって有用です。これらの機能には、インターフェースの状態の変更、ホスト名の設定、ゲートウェイデバイスの検索、特定のデバイスがダウンしているかどうかの検証、およびデフォルトルートの追加に関して、必要とされる情報を持つ実行中のプログラムにアクセスすることを含みます。
+ </div><div class="para">
+ IPv6 インターフェースに対して要求される関数は IPv4 インターフェースとは異なるので、<code class="filename">/etc/sysconfig/network-scripts/network-functions-ipv6</code> ファイルはこの情報を保持するために特別に存在します。このファイルにある関数は、静的 IPv6 ルートを設定および削除、トンネルを作成および削除、インターフェースに IPv6 アドレスを追加および削除、およびインターフェースに IPv6 アドレスの存在を確認します。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-static-routes.html"><strong>戻る</strong>7.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-networkscripts-resources.html"><strong>次へ</strong>7.6. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-interfaces.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-interfaces.html
new file mode 100644
index 0000000..4695201
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-interfaces.html
@@ -0,0 +1,126 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Network_Interfaces.html" title="第7章 ネットワーク・インターフェース" /><link rel="prev" href="ch-Network_Interfaces.html" title="第7章 ネットワーク・インターフェース" /><link rel="next" href="s2-networkscripts-interfaces-chan.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 cla
ss="previous"><a accesskey="p" href="ch-Network_Interfaces.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-chan.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-networkscripts-interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.2. インターフェース設定ファイル</h2></div></div></div><a id="idm40162528" class="indexterm"></a><a id="idm40160928" class="indexterm"></a><div class="para">
+ インターフェース設定ファイルは、それぞれのネットワークデバイスに対するソフトウェアインターフェースを制御します。システムが起動するとき、どのインターフェースを起動して、それらをどのように設定するのかを決めるために、これらのファイルを使用します。これらのファイルは通常 <code class="filename">ifcfg-<em class="replaceable"><code>name</code></em></code> という名前です、ここで <em class="replaceable"><code>name</code></em> は設定ファイルが制御するデバイスの名前を参照します。
+ </div><div class="section" id="s2-networkscripts-interfaces-eth0"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. イーサネット インターフェース</h3></div></div></div><a id="idm74907872" class="indexterm"></a><a id="idm74905792" class="indexterm"></a><div class="para">
+ One of the most common interface files is <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code>, which controls the first Ethernet <em class="firstterm">network interface card</em> or <acronym class="acronym">NIC</acronym> in the system. In a system with multiple NICs, there are multiple <code class="filename">ifcfg-eth<em class="replaceable"><code>X</code></em></code> files (where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface). Because each device has its own configuration file, an administrator can control how each interface functions individually.
+ </div><div class="para">
+ 下記は固定 IP アドレスを用いたシステム向けの <code class="filename">ifcfg-eth0</code> のサンプルです。
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=none
+ONBOOT=yes
+NETMASK=255.255.255.0
+IPADDR=10.0.1.27
+USERCTL=no</pre><div class="para">
+ インターフェース設定ファイルにおいて必要とされる値は他の値に基づいて変更できます。たとえば、DHCP を使用しているインターフェースの <code class="filename">ifcfg-eth0</code> ファイルは、IP 情報が DHCP サーバーにより提供されるので、異なって見えます:
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> is graphical configuration tool which provides an easy way to make changes to the various network interface configuration files (refer to <a class="xref" href="ch-NetworkManager.html">6章<em>NetworkManager</em></a> for detailed instructions on using this tool).
+ </div><div class="para">
+ 但し、任意のネットワーク インターフェースの設定ファイルは、手動で編集することもできます。
+ </div><div class="para">
+ 以下にイーサネット インターフェースの設定ファイル内の設定パラメーターを一覧で示します。
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">BONDING_OPTS</code>=<em class="replaceable"><code>parameters</code></em></span></dt><dd><div class="para">
+ sets the configuration parameters for the bonding device, and is used in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code>N</code></em></code> (see <a class="xref" href="s2-networkscripts-interfaces-chan.html">「チャンネル・ボンディング・インターフェース」</a>). These parameters are identical to those used for bonding devices in <code class="filename">/sys/class/net/<em class="replaceable"><code>bonding_device</code></em>/bonding</code>, and the module parameters for the bonding driver as described in <span class="emphasis"><em><code class="filename">bonding</code> Module Directives</em></span>.
+ </div><div class="para">
+ This configuration method is used so that multiple bonding devices can have different configurations. It is highly recommended to place all of your bonding options after the <code class="option">BONDING_OPTS</code> directive in <code class="filename">ifcfg-<em class="replaceable"><code>name</code></em></code>. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">BOOTPROTO</code>=<em class="replaceable"><code>protocol</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>protocol</code></em> は次のどれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">none</code> — ブートプロトコルを使用しません。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">bootp</code> — BOOTP プロトコルが使用されます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">dhcp</code> — DHCP プロトコルが使用されます。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">BROADCAST</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> はブロードキャストアドレスです。この値は <code class="command">ipcalc</code> を用いて自動的に計算されるので、このディレクティブは推奨されません。
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">DEVICE</code>=<em class="replaceable"><code>name</code></em> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code>name</code></em> is the name of the physical device (except for dynamically-allocated PPP devices where it is the <span class="emphasis"><em>logical name</em></span>).
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">DHCP_HOSTNAME</code>=<em class="replaceable"><code>name</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>name</code></em> は DHCP サーバーに送信される短縮ホスト名です。DHCP サーバーがクライアントに IP アドレスを受信する前にホスト名を指定するよう要求するときのみ、このオプションを使用してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">DNS<em class="replaceable"><code>{1,2}</code></em></code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>address</code></em> is a name server address to be placed in <code class="filename">/etc/resolv.conf</code> if the <code class="option">PEERDNS</code> directive is set to <code class="literal">yes</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">ETHTOOL_OPTS</code>=<em class="replaceable"><code>options</code></em> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code>options</code></em> are any device-specific options supported by <code class="command">ethtool</code>. For example, if you wanted to force 100Mb, full duplex:
+ </div><pre class="programlisting">ETHTOOL_OPTS="autoneg off speed 100 duplex full"</pre><div class="para">
+ Instead of a custom initscript, use <code class="option">ETHTOOL_OPTS</code> to set the interface speed and duplex settings. Custom initscripts run outside of the network init script lead to unpredictable results during a post-boot network service restart.
+ </div><div class="important"><div class="admonition_header"><h2>Set <span class="quote">「<span class="quote">autoneg off</span>」</span> before changing speed or duplex settings</h2></div><div class="admonition"><div class="para">
+ Changing speed or duplex settings almost always requires disabling autonegotiation with the <code class="option">autoneg off</code> option. This option needs to be stated first, as the option entries are order-dependent.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"><code class="option">GATEWAY</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> はネットワークのルーターまたはゲートウェイデバイスの IP アドレスです（あれば）。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">HOTPLUG</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このデバイスはホットプラグされたときに有効化されます (これが初期状態です)。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — このデバイスがホットプラグされたときに有効化<span class="emphasis"><em>されません</em></span>。
+ </div></li></ul></div><div class="para">
+ <code class="option">HOTPLUG=no</code> オプションは、bonding カーネルモジュールが読み込まれているときに、チャネルボンディングインターフェースが有効化するのを防げます。
+ </div><div class="para">
+ ボンディング・インターフェースの詳細は<a class="xref" href="s2-networkscripts-interfaces-chan.html">「チャンネル・ボンディング・インターフェース」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">HWADDR</code>=<em class="replaceable"><code>MAC-address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>MAC-address</code></em> は <em class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em> の形式であるイーサネットデバイスのハードウェアアドレスです。このディレクティブは、インターフェースが各 NIC モジュールに対して設定された読み込み順序にかかわりなく正しいデバイス名を確実に割り当てるために、複数の NIC を持つマシンにおいて使用する必要があります。このディレクティブは <code class="option">MACADDR</code> と同時に使用<span class="strong strong"><strong>できません</strong></span>。
+ </div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ 永続的なデバイス名は <code class="filename">/etc/udev/rules.d/70-persistent-net.rules</code> により処理されています。
+ </div></div></div></dd><dt class="varlistentry"><span class="term"><code class="option">IPADDR</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> は IP アドレスです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">LINKDELAY</code>=<em class="replaceable"><code>time</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>time</code></em> は、デバイスを設定する前にリンクネゴシエーションを待つ秒数です。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">MACADDR</code>=<em class="replaceable"><code>MAC-address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>MAC-address</code></em> は <em class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em> の形式であるイーサネットデバイスのハードウェアアドレスです。
+ </div><div class="para">
+ このディレクティブは、物理 NIC に割り当てられた MAC アドレスを上書きして、インターフェースに MAC アドレスを割り当てるために使用されます。このディレクティブは <code class="option">HWADDR</code> ディレクティブと一緒に使用<span class="strong strong"><strong>できません</strong></span>。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">MASTER</code>=<em class="replaceable"><code>bond-interface</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>bond-interface</code></em> は、イーサネットインターフェースが連結されたチャネルボンディングインターフェースです。
+ </div><div class="para">
+ このディレクティブは <code class="option">SLAVE</code> ディレクティブと一緒に使用されます。
+ </div><div class="para">
+ ボンディング・インターフェースの詳細は<a class="xref" href="s2-networkscripts-interfaces-chan.html">「チャンネル・ボンディング・インターフェース」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">NETMASK</code>=<em class="replaceable"><code>mask</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>mask</code></em> はネットマスクの値です。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">NETWORK</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> はネットワークアドレスです。この値は <code class="command">ipcalc</code> を用いて自動的に計算されるので、このディレクティブは推奨されません。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">NM_CONTROLLED</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — NetworkManager がこのデバイスを設定することを許可します。これは初期状態の動作のため、省略できます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — NetworkManager がこのデバイスを設定することを許可しません。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">ONBOOT</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このデバイスが起動時に有効化されます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — このデバイスが起動時に有効化されません。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">PEERDNS</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — DNS ディレクティブが設定されていると、<code class="filename">/etc/resolv.conf</code> を変更します。DHCP を使用していると、<code class="literal">yes</code> が初期値です。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — <code class="filename">/etc/resolv.conf</code> を変更しません。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">SLAVE</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このデバイスは <code class="option">MASTER</code> ディレクティブにおいて指定されたチャネルボンディングインターフェースにより制御されます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — このデバイスは <code class="option">MASTER</code> ディレクティブにおいて指定されたチャネルボンディングインターフェースにより制御<span class="emphasis"><em>されません</em></span>。
+ </div></li></ul></div><div class="para">
+ このディレクティブは <code class="option">MASTER</code> ディレクティブと同時に使用されません。
+ </div><div class="para">
+ チャネル・ボンディング・インターフェースの詳細は<a class="xref" href="s2-networkscripts-interfaces-chan.html">「チャンネル・ボンディング・インターフェース」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">SRCADDR</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>address</code></em> は出力パケットに対して指定されるソース IP アドレスです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">USERCTL</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — 非 <code class="systemitem">root</code> ユーザーがこのデバイスを制御できます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — 非 <code class="systemitem">root</code> ユーザーがこのデバイスを制御できません。
+ </div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Network_Interfaces.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="s2-networkscripts-interfaces-chan.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/17/html/System_Administrators_Guide/s1-networkscripts-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-resources.html
new file mode 100644
index 0000000..f7bb2fd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-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>7.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Network_Interfaces.html" title="第7章 ネットワーク・インターフェース" /><link rel="prev" href="s1-networkscripts-functions.html" title="7.5. ネットワーク機能ファイル" /><link rel="next" href="part-Infrastructure_Services.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 acc
esskey="p" href="s1-networkscripts-functions.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="s1-networkscripts-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.6. その他のリソース</h2></div></div></div><a id="idm69434768" class="indexterm"></a><div class="para">
+ ネットワークインターフェースに関して詳細に説明しているリソースを以下に示します。
+ </div><div class="section" id="s2-networkscripts-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.6.1. インストールされているドキュメント</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code>version</code></em>/sysconfig.txt</code></span></dt><dd><div class="para">
+ この章では触れていない IPv6 オプションなど、ネットワーク設定ファイル用に利用可能なオプションへの手引きです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/iproute-<em class="replaceable"><code>version</code></em>/ip-cref.ps</code></span></dt><dd><div class="para">
+ このファイルは <code class="command">ip</code> コマンドに関する豊富な情報を含みます。ここで、他のことがらの間で、ルーティングテーブルを操作するために使用できます。このファイルを表示するには <span class="application"><strong>ggv</strong></span> または <span class="application"><strong>kghostview</strong></span> アプリケーションを使用します。
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-functions.html"><strong>戻る</strong>7.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="part-Infrastructure_Services.html"><strong>次へ</strong>パート IV. インフラストラクチャーサービス</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-static-routes.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-static-routes.html
new file mode 100644
index 0000000..c81e8a5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-networkscripts-static-routes.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>7.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Network_Interfaces.html" title="第7章 ネットワーク・インターフェース" /><link rel="prev" href="s1-networkscripts-control.html" title="7.3. インターフェース制御スクリプト" /><link rel="next" href="s1-networkscripts-functions.html" title="7.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" hre
f="s1-networkscripts-control.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-functions.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-networkscripts-static-routes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.4. スタティック ルートの設定</h2></div></div></div><div class="para">
+ Static routes are for traffic that must not, or should not, go through the default route. Use the <code class="command">route</code> command to display the IP routing table. If static routes are required, they can be specified by means of the GATEWAY directive, either globally or in interface-specific configuration files. There is also the GATEWAYDEV directive, which is a global option. If multiple devices specify GATEWAY, and one interface is specified using the GATEWAYDEV directive, that directive will take precedence. This option is not recommend. Specifying an exit interface is optional. It can be useful if you want to force traffic out of a specific interface. For example, in the case of a VPN, you can force traffic to a remote network to pass through a tun0 interface even when the interface is in a different sub-net to the destination network.
+ </div><div class="para">
+ Global static route configuration is stored in the <code class="filename">/etc/sysconfig/network</code> file. This file specifies routing and host information for all network interfaces. For more information about this file and the directives it accepts, refer to <a class="xref" href="ch-The_sysconfig_Directory.html#s2-sysconfig-network">「/etc/sysconfig/network」</a>.
+ </div><div class="para">
+ Per-interface static route configuration is stored in a <code class="filename">/etc/sysconfig/network-scripts/route-<em class="replaceable"><code>interface</code></em></code> file. For example, static routes for the <code class="systemitem">eth0</code> interface would be stored in the <code class="filename">/etc/sysconfig/network-scripts/route-eth0</code> file. The <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> file has two formats: IP command arguments and network/netmask directives.
+ </div><h3 id="bh-networkscripts-static-routes-ip-command">IP コマンドの引数形式</h3><div class="para">
+ 最初の行にデフォルトゲートウェイを定義します。デフォルトゲートウェイが DHCP 経由で設定されていないときのみ、これが必要になります:
+ </div><pre class="synopsis">default via <em class="replaceable"><code>X.X.X.X</code></em><code class="option"> dev </code><em class="replaceable"><code>interface</code></em></pre><div class="para">
+ <em class="replaceable"><code>X.X.X.X</code></em> is the IP address of the default gateway. The <em class="replaceable"><code>interface</code></em> is the interface that is connected to, or can reach, the default gateway. The <code class="option"> dev </code> option can be omitted.
+ </div><div class="para">
+ 静的ルーティングを定義します。各行はそれぞれルーティングとして構文解析されます:
+ </div><pre class="synopsis"><em class="replaceable"><code>X.X.X.X/X</code></em> via <em class="replaceable"><code>X.X.X.X</code></em> dev <em class="replaceable"><code>interface</code></em></pre><div class="para">
+ <em class="replaceable"><code>X.X.X.X/X</code></em> は静的ルートに対するネットワークの番号とネットマスクです。<em class="replaceable"><code>X.X.X.X</code></em> および <em class="replaceable"><code>interface</code></em> はそれぞれデフォルトゲートウェイに対する IP アドレスとインターフェースです。<em class="replaceable"><code>X.X.X.X</code></em> のアドレスはデフォルトゲートウェイの IP アドレスである必要がありません。多くの場合、<em class="replaceable"><code>X.X.X.X</code></em> は異なるサブネットにおける IP アドレスです。また、<em class="replaceable"><code>interface</code></em> は、そのサブネットに接続されている、または到達できるインターフェースです。
+ </div><div class="para">
+ 以下は IP コマンド引数形式を使用するサンプル <code class="filename">route-eth0</code> ファイルです。デフォルトゲートウェイは 192.168.0.1、インターフェース eth0 です。2 つの静的ルートは 10.10.10.0/24 および 172.16.1.0/24 のネットワークに対するものです:
+ </div><pre class="screen">default via 192.168.0.1 dev eth0
+10.10.10.0/24 via 192.168.0.1 dev eth0
+172.16.1.0/24 via 192.168.0.1 dev eth0</pre><div class="para">
+ Static routes should only be configured for other subnets. The above example is not necessary, since packets going to the 10.10.10.0/24 and 172.16.1.0/24 networks will use the default gateway anyway. Below is an example of setting static routes to a different subnet, on a machine in a 192.168.0.0/24 subnet. The example machine has an <code class="systemitem">eth0</code> interface in the 192.168.0.0/24 subnet, and an <code class="systemitem">eth1</code> interface (10.10.10.1) in the 10.10.10.0/24 subnet:
+ </div><pre class="screen">10.10.10.0/24 via 10.10.10.1 dev eth1</pre><div class="important"><div class="admonition_header"><h2>デフォルト ゲートウェイの複製</h2></div><div class="admonition"><div class="para">
+ デフォルトゲートウェイがすでに DHCP から割り当てられていると、IP コマンド引数のフォーマットは、起動中、または <code class="command">ifup</code> コマンドを使用してインターフェースを停止状態から起動するとき、次のエラーのうちどちらかが発生します: "RTNETLINK answers: File exists" または 'Error: either "to" is a duplicate, or "<em class="replaceable"><code>X.X.X.X</code></em>" is a garbage.'、ここで <em class="replaceable"><code>X.X.X.X</code></em> はゲートウェイまたは他の IP アドレスです。デフォルトゲートウェイを使用して他のネットワークへの他のルートがあると、これらのエラーが発生する可能性があります。これらのエラーはどちらも無視しても安全です。
+ </div></div></div><h3 id="bh-networkscripts-static-routes-network-netmask-directives">ネットワーク/ネットマスク ディレクティブの形式</h3><div class="para">
+ You can also use the network/netmask directives format for <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> files. The following is a template for the network/netmask format, with instructions following afterwards:
+ </div><pre class="synopsis"> ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em> NETMASK0=<em class="replaceable"><code>X.X.X.X</code></em> GATEWAY0=<em class="replaceable"><code>X.X.X.X</code></em> </pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em></code> is the network number for the static route.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NETMASK0=<em class="replaceable"><code>X.X.X.X</code></em></code> is the netmask for the network number defined with <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">GATEWAY0=<em class="replaceable"><code>X.X.X.X</code></em></code> is the default gateway, or an IP address that can be used to reach <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em></code>
+ </div></li></ul></div><div class="para">
+ The following is a sample <code class="filename">route-eth0</code> file using the network/netmask directives format. The default gateway is 192.168.0.1, interface <code class="systemitem">eth0</code>. The two static routes are for the 10.10.10.0/24 and 172.16.1.0/24 networks. However, as mentioned before, this example is not necessary as the 10.10.10.0/24 and 172.16.1.0/24 networks would use the default gateway anyway:
+ </div><pre class="programlisting">ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=192.168.0.1
+ADDRESS1=172.16.1.0
+NETMASK1=255.255.255.0
+GATEWAY1=192.168.0.1</pre><div class="para">
+ 後続の静的ルートが順番に番号がつけられる必要があります。また、すべての値を飛ばすことはできません。たとえば、<code class="computeroutput">ADDRESS0</code>, <code class="computeroutput">ADDRESS1</code>, <code class="computeroutput">ADDRESS2</code>, などです。
+ </div><div class="para">
+ Below is an example of setting static routes to a different subnet, on a machine in the 192.168.0.0/24 subnet. The example machine has an <code class="systemitem">eth0</code> interface in the 192.168.0.0/24 subnet, and an <code class="systemitem">eth1</code> interface (10.10.10.1) in the 10.10.10.0/24 subnet:
+ </div><pre class="programlisting">ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=10.10.10.1</pre><div class="para">
+ DHCP が使用されていると、これらの設定が自動的に割り当てられることに注意してください。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-control.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="s1-networkscripts-functions.html"><strong>次へ</strong>7.5. ネットワーク機能ファイル</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-openssh-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-openssh-additional-resources.html
new file mode 100644
index 0000000..e40caa6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-openssh-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>10.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-OpenSSH.html" title="第10章 OpenSSH" /><link rel="prev" href="s2-ssh-beyondshell-tcpip.html" title="10.4.2. ポート転送" /><link rel="next" href="s2-openssh-useful-websites.html" title="10.5.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="s2-ssh-beyondshell-tcpip.html"><strong>戻る</strong></a></li><li class="next"><
a accesskey="n" href="s2-openssh-useful-websites.html"><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">10.5. 追加のリソース</h2></div></div></div><a id="idm72625408" class="indexterm"></a><a id="idm49303344" class="indexterm"></a><div class="para">
+ OpenSSH と OpenSSL プロジェクトの開発は常に進められているため、これらに関する最新情報は該当する Web サイトを参照してください。 OpenSSH と OpenSSL ツールの man ページでも詳細情報を参照することができます。
+ </div><div class="section" id="s2-openssh-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.5.1. インストールされているドキュメント</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">man ssh</code></span></dt><dd><div class="para">
+ <span class="application"><strong>ssh</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man scp</code></span></dt><dd><div class="para">
+ <span class="application"><strong>scp</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sftp</code></span></dt><dd><div class="para">
+ <span class="application"><strong>sftp</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sshd</code></span></dt><dd><div class="para">
+ <span class="application"><strong>sshd</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ssh-keygen</code></span></dt><dd><div class="para">
+ <span class="application"><strong>ssh-keygen</strong></span> の使用法に関する完全なドキュメントを含むマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ssh_config</code></span></dt><dd><div class="para">
+ SSH クライアントの利用可能な設定オプションの完全な説明を持つマニュアルページです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sshd_config</code></span></dt><dd><div class="para">
+ SSH デーモンの利用可能な設定オプションの完全な説明を持つマニュアルページです。
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-beyondshell-tcpip.html"><strong>戻る</strong>10.4.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-openssh-useful-websites.html"><strong>次へ</strong>10.5.2. 役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-additional-resources.html
new file mode 100644
index 0000000..819d86c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-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>20.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.10. OProfile and SystemTap" /><link rel="next" href="s2-oprofile-useful-websites.html" title="20.11.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-oprofile-and-systemtap.html"><strong>戻る</strong></a></li><li cl
ass="next"><a accesskey="n" href="s2-oprofile-useful-websites.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.11. 追加のリソース</h2></div></div></div><a id="idm68214128" class="indexterm"></a><div class="para">
+ This chapter only highlights OProfile and how to configure and use it. To learn more, refer to the following resources.
+ </div><div class="section" id="s1-oprofile-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.11.1. Installed Docs</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/oprofile-<em class="replaceable"><code>version</code></em>/oprofile.html</code> — <em class="citetitle">OProfile Manual</em>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">oprofile</code> man 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></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-and-systemtap.html"><strong>戻る</strong>20.10. 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="s2-oprofile-useful-websites.html"><strong>次へ</strong>20.11.2. 役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html
new file mode 100644
index 0000000..7901c9e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.4. Saving Data" /><link rel="next" href="s2-oprofile-reading-opreport-single.html" title="20.5.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>戻る</strong></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.5. Analyzing the Data</h2></div></div></div><a id="idm39400880" class="indexterm"></a><div class="para">
+ Periodically, the OProfile daemon, <code class="command">oprofiled</code>, 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. Please note that the sample file and the binary have to agree. Making a backup is not going to work if they do not match. <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. Refer to <a class="xref" href="s1-oprofile-saving-data.html">「Saving Data」</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.5.1. Using <code class="command">opreport</code> </h3></div></div></div><a id="idm52427120" class="indexterm"></a><a id="idm52424896" class="indexterm"></a><div class="para">
+ The <code class="command">opreport</code> tool provides an overview of all the executables being profiled.
+ </div><div class="para">
+ The following is part of a sample output:
+ </div><pre class="screen">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">
+ Refer to the <code class="command">opreport</code> man 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.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-saving-data.html"><strong>戻る</strong>20.4. Saving 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-reading-opreport-single.html"><strong>次へ</strong>20.5.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/17/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html
new file mode 100644
index 0000000..5e8eb51
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.10. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.9. Graphical Interface" /><link rel="next" href="s1-oprofile-additional-resources.html" title="20.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-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.10. OProfile and SystemTap</h2></div></div></div><a id="idm21844016" 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 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 instrumentation, it is particularly useful for instrumenting the kernel and daemons.
+ </div><div class="para">
+ For more information on SystemTap, refer to <a class="xref" href="s2-oprofile-useful-websites.html">「役に立つ Web サイト」</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.9. 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.11. 追加のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-configuring.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-configuring.html
new file mode 100644
index 0000000..b472e47
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.2. Configuring 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-oprofile-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-oprofile-event
s.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.2. Configuring OProfile</h2></div></div></div><a id="idm48137824" class="indexterm"></a><a id="idm48136192" class="indexterm"></a><a id="idm69734016" class="indexterm"></a><div class="para">
+ Before OProfile can be run, 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.2.1. Specifying the Kernel</h3></div></div></div><a id="idm34497984" 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 root:
+ </div><a id="idm34495264" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux</code></pre><div class="note"><div class="admonition_header"><h2>Install the debuginfo package</h2></div><div class="admonition"><div class="para">
+ The <span class="package">debuginfo</span> package for the kernel must be installed (which contains the uncompressed kernel) in order to monitor the kernel.
+ </div></div></div><div class="para">
+ To configure OProfile not to monitor the kernel, execute the following command as root:
+ </div><a id="idm57025056" 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. Refer to <a class="xref" href="s1-oprofile-dev-oprofile.html">「Understanding <code class="filename">/dev/oprofile/</code> 」</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, refer to <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="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-oprofile-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/17/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html
new file mode 100644
index 0000000..761648d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.6. Understanding /dev/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.5.4. Using opannotate" /><link rel="next" href="s1-oprofile-example-usage.html" title="20.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="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.6. Understanding <code class="filename">/dev/oprofile/</code> </h2></div></div></div><a id="idm49205168" class="indexterm"></a><a id="idm49202944" class="indexterm"></a><div class="para">
+ The <code class="filename">/dev/oprofile/</code> directory contains the file system for OProfile. 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.5.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.7. 使用法の例</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-example-usage.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-example-usage.html
new file mode 100644
index 0000000..2490077
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.6. Understanding /dev/oprofile/" /><link rel="next" href="s1-oprofile-java-support.html" title="20.8. 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.7. 使用法の例</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 under performing, 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.6. Understanding /dev/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="s1-oprofile-java-support.html"><strong>次へ</strong>20.8. OProfile Support for Java</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-gui.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-gui.html
new file mode 100644
index 0000000..db05417
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.9. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.8. OProfile Support for Java" /><link rel="next" href="s1-oprofile-and-systemtap.html" title="20.10. 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.9. Graphical Interface</h2></div></div></div><a id="idm48859600" class="indexterm"></a><div class="para">
+ Some OProfile preferences can be set with a graphical interface. To start it, execute the <code class="command">oprof_start</code> command as root at a shell prompt. To use the graphical interface, you will need to have the <code class="filename">oprofile-gui</code> package installed.
+ </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 unselected, 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 unselected, 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 checkbox 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 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.8. 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.10. OProfile and SystemTap</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-java-support.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-java-support.html
new file mode 100644
index 0000000..1e35a00
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-java-support.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.8. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.7. 使用法の例" /><link rel="next" href="s1-oprofile-gui.html" title="20.9. 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" hr
ef="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.8. OProfile Support for Java</h2></div></div></div><a id="idm42670016" 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 17 includes build-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.8.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:jvmti_oprofile</code></pre><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.
+ </div></div></div><div class="para">
+ To learn more about Java support in OProfile, refer to 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.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-oprofile-gui.html"><strong>次へ</strong>20.9. Graphical Interface</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-saving-data.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-saving-data.html
new file mode 100644
index 0000000..5c4dc1b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-saving-data.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.4. Saving 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.3. Starting and Stopping OProfile" /><link rel="next" href="s1-oprofile-analyzing-data.html" title="20.5. 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 a
ccesskey="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.4. Saving Data</h2></div></div></div><a id="idm49408192" 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 directory <code class="filename">/var/lib/oprofile/samples/<em class="replaceable"><code>name</code></em>/</code> is created and the current sample files are copied to it.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-starting.html"><strong>戻る</strong>20.3. Starting and Stopping 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="s1-oprofile-analyzing-data.html"><strong>次へ</strong>20.5. Analyzing the Data</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-starting.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-oprofile-starting.html
new file mode 100644
index 0000000..39c2571
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.3. Starting and Stopping 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.2.3. Separating Kernel and User-space Profiles" /><link rel="next" href="s1-oprofile-saving-data.html" title="20.4. Saving 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="s2-oprofile-starting-separate.html"><strong>戻る</strong></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.3. Starting and Stopping OProfile</h2></div></div></div><a id="idm61199520" class="indexterm"></a><div class="para">
+ To start monitoring the system with OProfile, execute the following command as root:
+ </div><a id="idm24937296" 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="idm44877632" class="indexterm"></a><a id="idm44875408" class="indexterm"></a><a id="idm46890352" 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 17 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 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:
+ </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.2.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.4. Saving Data</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-additional-resources.html
new file mode 100644
index 0000000..43e1384
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="s1-printing-edit.html" title="16.3.10. 既存プリンタの変更" /><link rel="next" href="part-Monitoring_and_Automation.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-printing-edit.html"><strong>戻る</s
trong></a></li><li class="next"><a accesskey="n" href="part-Monitoring_and_Automation.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">16.3.11. その他のリソース</h3></div></div></div><div class="para">
+ To learn more about printing on Fedora, refer to 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">16.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">16.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.linuxprinting.org/</a></span></dt><dd><div 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></span></dt><dd><div 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>16.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="part-Monitoring_and_Automation.html"><strong>次へ</strong>パート VI. 監視および自動化</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-edit.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-edit.html
new file mode 100644
index 0000000..d08f3c3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-edit.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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="s1-printing-test-page.html" title="16.3.9. Printing a test page" /><link rel="next" href="s1-printing-additional-resources.html" title="16.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">16.3.10. 既存プリンタの変更</h3></div></div></div><div class="para">
+ To delete an existing printer, in the <span class="guilabel"><strong>Printer Configuration</strong></span> 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="idm42798032"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm42798032">16.3.10.1. The Settings Page</h4></div></div></div><a id="idm54813168" 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>図16.11 Settings page</h6></div><br class="figure-break" /></div><div class="section" id="idm22004752"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm22004752">16.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 username 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-menu and choose the option that best describes the nature of the print jobs (such as <span class="guilabel"><strong>topsecret</strong></span>, <span class="guilabel"><strong>classified</strong></span>, or <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">16.3.10.2.1. Sharing Printers</h5></div></div></div><a id="idm57915856" 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="para">
+ Finally, ensure that the firewall allows incoming TCP connections to port 631, which is Network Printing Server (IPP) in system-config-firewall.
+ </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>図16.12 Policies page</h6></div><br class="figure-break" /></div><div class="section" id="sec-The_Access_Control_Page"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">16.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>図16.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">16.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>図16.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">16.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>図16.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">16.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>図16.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">16.3.10.3. 印刷ジョブの管理</h4></div></div></div><a id="idm60698048" 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>図16.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>例16.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">例16.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 root 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>16.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>16.3.11. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-ipp-printer.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-ipp-printer.html
new file mode 100644
index 0000000..9c310d3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="s1-printing-jetdirect-printer.html" title="16.3.4. Adding an AppSocket/HP JetDirect printer" /><link rel="next" href="sec-printing-LPDLPR-printer.html" title="16.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">16.3.5. IPP プリンタの追加</h3></div></div></div><a id="idm45827280" class="indexterm"></a><div class="para">
+ IPP プリンタは同じ TCP/IP ネットワーク上にある別のシステムに接続されたプリンタです。このプリンタが接続されるシステムは CUPS を実行しているか単純に IPP を使用するよう設定されているかのどちらかです。
+ </div><div class="para">
+ If a firewall is enabled on the printer server, then the firewall must be configured to allow incoming TCP connections on port 631. 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 UDP packets on port 631.
+ </div><div class="procedure" id="proc-Adding_IPP_Printer"><div class="para">
+ Follow this procedure to add an IPP 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> 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 hostname for the system that controls the 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 IPP Printer
+ </div></div></div></div><h6>図16.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. Refer to <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>16.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>16.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/17/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html
new file mode 100644
index 0000000..cdbb1df
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="sec-Adding_Other_Printer.html" title="16.3.3. ローカルプリンタの追加" /><link rel="next" href="s1-printing-ipp-printer.html" title="16.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">16.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">New Printer</code> dialog (refer to <a class="xref" href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">「Starting the Printer 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 hostname or IP 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>図16.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. Refer to <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>16.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>16.3.5. IPP プリンタの追加</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-select-model.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-select-model.html
new file mode 100644
index 0000000..6092209
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="s1-printing-smb-printer.html" title="16.3.7. Adding a Samba (SMB) printer" /><link rel="next" href="s1-printing-test-page.html" title="16.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">16.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 PostScript Printer Description (PPD) 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>図16.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">図16.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 printed 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>図16.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>図16.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 also later, refer to <a class="xref" href="s1-printing-test-page.html">「Printing a test page」</a> for details.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-smb-printer.html"><strong>戻る</strong>16.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>16.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/17/html/System_Administrators_Guide/s1-printing-smb-printer.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-smb-printer.html
new file mode 100644
index 0000000..21d413e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="sec-printing-LPDLPR-printer.html" title="16.3.6. Adding an LPD/LPR Host or Printer" /><link rel="next" href="s1-printing-select-model.html" title="16.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">16.3.7. Adding a Samba (SMB) printer</h3></div></div></div><a id="idm70202688" class="indexterm"></a><a id="idm70201248" 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">yum install samba-client</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は <a class="xref" href="sec-Installing.html">「パッケージのインストール」</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">図16.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>図16.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>: username 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 username 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 プリンタのユーザー名とパスワードは root 及び lpd によって読み取り可能な暗号化されていないファイルとしてプリンタサーバーに格納されます。したがって、プリンタサーバーに root アクセスを有するユーザーであれば他のユーザーが Samba プリンタへのアクセスに使用するユーザー名とパスワードを閲覧することができます。
+ </div><div class="para">
+ As such, when you choose a username 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. Refer to <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>16.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>16.3.8. プリンタモデルの選択と終了</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-test-page.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-printing-test-page.html
new file mode 100644
index 0000000..332b5ad
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="s1-printing-select-model.html" title="16.3.8. プリンタモデルの選択と終了" /><link rel="next" href="s1-printing-edit.html" title="16.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">16.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>16.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>16.3.10. 既存プリンタの変更</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-additional-resources.html
new file mode 100644
index 0000000..6c3317e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-additional-resources.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>E.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-proc.html" title="付録E The proc File System" /><link rel="prev" href="s1-proc-sysctl.html" title="E.4. Using the sysctl Command" /><link rel="next" href="app-Revision_History.html" title="付録F 改訂履歴" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-sysctl.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-proc-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.5. 参考文献</h2></div></div></div><a id="idm25960624" class="indexterm"></a><div class="para">
+ Below are additional sources of information about <code class="filename">proc</code> file system.
+ </div><div class="simplesect" id="s2-proc-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h1 class="title">インストールされているドキュメント</h1></div></div></div><a id="idm25956432" class="indexterm"></a><div class="para">
+ Some of the best documentation about the <code class="filename">proc</code> file system is installed on the system by default.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt</code> — Contains assorted, but limited, information about all aspects of the <code class="filename">/proc/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysrq.txt</code> — An overview of System Request Key options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysctl/</code> — A directory containing a variety of <code class="command">sysctl</code> tips, including modifying values that concern the kernel (<code class="filename">kernel.txt</code>), accessing file systems (<code class="filename">fs.txt</code>), and virtual memory use (<code class="filename">vm.txt</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/ip-sysctl.txt</code> — A detailed overview of IP networking options.
+ </div></li></ul></div></div><div class="simplesect" id="s2-proc-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h1 class="title">役に立つ Web サイト</h1></div></div></div><a id="idm41612192" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.linuxhq.com/">http://www.linuxhq.com/</a> — This website maintains a complete database of source, patches, and documentation for various versions of the Linux kernel.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-sysctl.html"><strong>戻る</strong>E.4. Using the sysctl 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="app-Revision_History.html"><strong>次へ</strong>付録F 改訂履歴</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-directories.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-directories.html
new file mode 100644
index 0000000..3855a79
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-directories.html
@@ -0,0 +1,118 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.3. Directories within /proc/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-proc.html" title="付録E The proc File System" /><link rel="prev" href="s2-proc-version.html" title="E.2.29. /proc/version" /><link rel="next" href="s2-proc-dir-bus.html" title="E.3.2. /proc/bus/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-version.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-bus.h
tml"><strong>次へ</strong></a></li></ul><div class="section" id="s1-proc-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.3. Directories within /proc/</h2></div></div></div><a id="idm24341600" class="indexterm"></a><div class="para">
+ Common groups of information concerning the kernel are grouped into directories and subdirectories within the <code class="filename">/proc/</code> directory.
+ </div><div class="section" id="s2-proc-processdirs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.1. Process Directories</h3></div></div></div><a id="idm24337152" class="indexterm"></a><div class="para">
+ Every <code class="filename">/proc/</code> directory contains a number of directories with numerical names. A listing of them may be similar to the following:
+ </div><pre class="screen">
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 1
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 1010
+dr-xr-xr-x 3 xfs xfs 0 Feb 13 01:28 1087
+dr-xr-xr-x 3 daemon daemon 0 Feb 13 01:28 1123
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 11307
+dr-xr-xr-x 3 apache apache 0 Feb 13 01:28 13660
+dr-xr-xr-x 3 rpc rpc 0 Feb 13 01:28 637
+dr-xr-xr-x 3 rpcuser rpcuser 0 Feb 13 01:28 666
+</pre><div class="para">
+ These directories are called <em class="firstterm">process directories</em>, as they are named after a program's process ID and contain information specific to that process. The owner and group of each process directory is set to the user running the process. When the process is terminated, its <code class="filename">/proc/</code> process directory vanishes.
+ </div><div class="para">
+ Each process directory contains the following files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">cmdline</code> — Contains the command issued when starting the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cwd</code> — A symbolic link to the current working directory for the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">environ</code> — A list of the environment variables for the process. The environment variable is given in all upper-case characters, and the value is in lower-case characters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">exe</code> — A symbolic link to the executable of this process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">fd</code> — A directory containing all of the file descriptors for a particular process. These are given in numbered links:
+ </div><pre class="screen">
+total 0
+lrwx------ 1 root root 64 May 8 11:31 0 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 1 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 2 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 3 -> /dev/ptmx
+lrwx------ 1 root root 64 May 8 11:31 4 -> socket:[7774817]
+lrwx------ 1 root root 64 May 8 11:31 5 -> /dev/ptmx
+lrwx------ 1 root root 64 May 8 11:31 6 -> socket:[7774829]
+lrwx------ 1 root root 64 May 8 11:31 7 -> /dev/ptmx
+</pre></li><li class="listitem"><div class="para">
+ <code class="computeroutput">maps</code> — A list of memory maps to the various executables and library files associated with this process. This file can be rather long, depending upon the complexity of the process, but sample output from the <code class="command">sshd</code> process begins like the following:
+ </div><pre class="screen">
+08048000-08086000 r-xp 00000000 03:03 391479 /usr/sbin/sshd
+08086000-08088000 rw-p 0003e000 03:03 391479 /usr/sbin/sshd
+08088000-08095000 rwxp 00000000 00:00 0
+40000000-40013000 r-xp 0000000 03:03 293205 /lib/ld-2.2.5.so
+40013000-40014000 rw-p 00013000 03:03 293205 /lib/ld-2.2.5.so
+40031000-40038000 r-xp 00000000 03:03 293282 /lib/libpam.so.0.75
+40038000-40039000 rw-p 00006000 03:03 293282 /lib/libpam.so.0.75
+40039000-4003a000 rw-p 00000000 00:00 0
+4003a000-4003c000 r-xp 00000000 03:03 293218 /lib/libdl-2.2.5.so
+4003c000-4003d000 rw-p 00001000 03:03 293218 /lib/libdl-2.2.5.so
+</pre></li><li class="listitem"><div class="para">
+ <code class="computeroutput">mem</code> — The memory held by the process. This file cannot be read by the user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">root</code> — A link to the root directory of the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">stat</code> — The status of the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">statm</code> — The status of the memory in use by the process. Below is a sample <code class="filename">/proc/statm</code> file:
+ </div><pre class="screen">
+263 210 210 5 0 205 0
+</pre><div class="para">
+ The seven columns relate to different memory statistics for the process. From left to right, they report the following aspects of the memory used:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Total program size, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ Size of memory portions, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages that are shared.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages that are code.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages of data/stack.
+ </div></li><li class="listitem"><div class="para">
+ Number of library pages.
+ </div></li><li class="listitem"><div class="para">
+ Number of dirty pages.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">status</code> — The status of the process in a more readable form than <code class="filename">stat</code> or <code class="filename">statm</code>. Sample output for <code class="command">sshd</code> looks similar to the following:
+ </div><pre class="screen">
+Name: sshd
+State: S (sleeping)
+Tgid: 797
+Pid: 797
+PPid: 1
+TracerPid: 0
+Uid: 0 0 0 0
+Gid: 0 0 0 0
+FDSize: 32
+Groups:
+VmSize: 3072 kB
+VmLck: 0 kB
+VmRSS: 840 kB
+VmData: 104 kB
+VmStk: 12 kB
+VmExe: 300 kB
+VmLib: 2528 kB
+SigPnd: 0000000000000000
+SigBlk: 0000000000000000
+SigIgn: 8000000000001000
+SigCgt: 0000000000014005
+CapInh: 0000000000000000
+CapPrm: 00000000fffffeff
+CapEff: 00000000fffffeff
+</pre><div class="para">
+ The information in this output includes the process name and ID, the state (such as <code class="computeroutput">S (sleeping)</code> or <code class="computeroutput">R (running)</code>), user/group ID running the process, and detailed data regarding memory usage.
+ </div></li></ul></div><div class="section" id="s3-proc-self"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.1.1. /proc/self/ </h4></div></div></div><a id="idm59002160" class="indexterm"></a><div class="para">
+ The <code class="filename">/proc/self/</code> directory is a link to the currently running process. This allows a process to look at itself without having to know its process ID.
+ </div><div class="para">
+ Within a shell environment, a listing of the <code class="filename">/proc/self/</code> directory produces the same contents as listing the process directory for that process.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-version.html"><strong>戻る</strong>E.2.29. /proc/version </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dir-bus.html"><strong>次へ</strong>E.3.2. /proc/bus/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-sysctl.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-sysctl.html
new file mode 100644
index 0000000..566380b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-sysctl.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>E.4. Using the sysctl 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-proc.html" title="付録E The proc File System" /><link rel="prev" href="s2-proc-pid.html" title="E.3.12. /proc/PID/" /><link rel="next" href="s1-proc-additional-resources.html" title="E.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-proc-pid.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-proc-additio
nal-resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-proc-sysctl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.4. Using the sysctl Command</h2></div></div></div><a id="idm41512480" class="indexterm"></a><a id="idm41510736" class="indexterm"></a><a id="idm41508992" class="indexterm"></a><a id="idm49472688" class="indexterm"></a><a id="idm49469136" class="indexterm"></a><a id="idm49466912" class="indexterm"></a><div class="para">
+ The <code class="command">/sbin/sysctl</code> command is used to view, set, and automate kernel settings in the <code class="filename">/proc/sys/</code> directory.
+ </div><div class="para">
+ For a quick overview of all settings configurable in the <code class="filename">/proc/sys/</code> directory, type the <code class="command">/sbin/sysctl -a</code> command as root. This creates a large, comprehensive list, a small portion of which looks something like the following:
+ </div><pre class="screen">
+net.ipv4.route.min_delay = 2 kernel.sysrq = 0 kernel.sem = 250 32000 32 128
+</pre><div class="para">
+ This is the same information seen if each of the files were viewed individually. The only difference is the file location. For example, the <code class="filename">/proc/sys/net/ipv4/route/min_delay</code> file is listed as <code class="computeroutput">net.ipv4.route.min_delay</code>, with the directory slashes replaced by dots and the <code class="computeroutput">proc.sys</code> portion assumed.
+ </div><div class="para">
+ The <code class="command">sysctl</code> command can be used in place of <code class="command">echo</code> to assign values to writable files in the <code class="filename">/proc/sys/</code> directory. For example, instead of using the command
+ </div><pre class="screen">
+echo 1 > /proc/sys/kernel/sysrq
+</pre><div class="para">
+ use the equivalent <code class="command">sysctl</code> command as follows:
+ </div><pre class="screen">
+sysctl -w kernel.sysrq="1"
+kernel.sysrq = 1
+</pre><div class="para">
+ While quickly setting single values like this in <code class="filename">/proc/sys/</code> is helpful during testing, this method does not work as well on a production system as special settings within <code class="filename">/proc/sys/</code> are lost when the machine is rebooted. To preserve custom settings, add them to the <code class="filename">/etc/sysctl.conf</code> file.
+ </div><div class="para">
+ Each time the system boots, <code class="systemitem">systemd</code> executes <code class="command">sysctl</code> using the <code class="filename">/etc/sysctl.conf</code> configuration file to determine the values passed to the kernel. Any values added to <code class="filename">/etc/sysctl.conf</code> therefore take effect each time the system boots.
+ </div><div class="para">
+ Additionally, <code class="systemitem">systemd</code> determines the contents of several directories including <code class="filename">/etc/sysctl.d/</code> and reads values from any file with the <code class="filename">.conf</code> extension. The <code class="filename">/etc/sysctl.d/</code> directory can be used to organize values into different files, and also permits them to be disabled by changing the extension of the file. For a complete list of directories read by <code class="systemitem">systemd</code>, refer to the <span class="bold bold"><strong>sysctl.d</strong></span>(5) manual page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-pid.html"><strong>戻る</strong>E.3.12. /proc/PID/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-additional-resources.html"><strong>次へ</strong>E.5. 参考文献</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-topfiles.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-topfiles.html
new file mode 100644
index 0000000..3ab5903
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-proc-topfiles.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>E.2. Top-level Files within the proc File 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-proc.html" title="付録E The proc File System" /><link rel="prev" href="ch-proc.html" title="付録E The proc File System" /><link rel="next" href="s2-proc-cmdline.html" title="E.2.2. /proc/cmdline" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-cmdline.html"><
strong>次へ</strong></a></li></ul><div class="section" id="s1-proc-topfiles"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.2. Top-level Files within the <code class="filename">proc</code> File System</h2></div></div></div><a id="idm57580640" class="indexterm"></a><div class="para">
+ Below is a list of some of the more useful virtual files in the top-level of the <code class="filename">/proc/</code> directory.
+ </div><div class="note"><div class="admonition_header"><h2>The content of your files may differ</h2></div><div class="admonition"><div class="para">
+ In most cases, the content of the files listed in this section are not the same as those installed on your machine. This is because much of the information is specific to the hardware on which Fedora is running for this documentation effort.
+ </div></div></div><div class="section" id="s2-proc-buddyinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.1. /proc/buddyinfo </h3></div></div></div><a id="idm73364448" class="indexterm"></a><div class="para">
+ This file is used primarily for diagnosing memory fragmentation issues. Using the buddy algorithm, each column represents the number of pages of a certain order (a certain size) that are available at any given time. For example, for zone <em class="firstterm">direct memory access</em> (DMA), there are 90 of 2<sup>(0*PAGE_SIZE)</sup> chunks of memory. Similarly, there are 6 of 2<sup>(1*PAGE_SIZE)</sup> chunks, and 2 of 2<sup>(2*PAGE_SIZE)</sup> chunks of memory available.
+ </div><div class="para">
+ The <code class="computeroutput">DMA</code> row references the first 16 MB on a system, the <code class="computeroutput">HighMem</code> row references all memory greater than 4 GB on a system, and the <code class="computeroutput">Normal</code> row references all memory in between.
+ </div><div class="para">
+ The following is an example of the output typical of <code class="filename">/proc/buddyinfo</code>:
+ </div><pre class="screen">
+Node 0, zone DMA 90 6 2 1 1 ...
+Node 0, zone Normal 1650 310 5 0 0 ...
+Node 0, zone HighMem 2 0 0 1 1 ...
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-proc.html"><strong>戻る</strong>付録E The proc File 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="s2-proc-cmdline.html"><strong>次へ</strong>E.2.2. /proc/cmdline </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-additional-resources.html
new file mode 100644
index 0000000..c404f45
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-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>B.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-RPM.html" title="付録B RPM" /><link rel="prev" href="s1-rpm-impressing.html" title="B.4. Practical and Common Examples of RPM Usage" /><link rel="next" href="s2-rpm-useful-websites.html" title="B.5.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-rpm-impressing.html"><strong>戻る</strong></a></li><li class="next"><a ac
cesskey="n" href="s2-rpm-useful-websites.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">B.5. その他のリソース</h2></div></div></div><a id="idm67180688" class="indexterm"></a><div class="para">
+ RPM は、パッケージの問い合わせ、インストール、アップグレード、 削除を実行するためのたくさんのオプションや方法がある 非常に複雑なユーティリティです。RPM の詳細については、 以下のリソースを参照してください。
+ </div><div class="section" id="s2-rpm-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.5.1. インストールされているドキュメント</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rpm --help</code> — This command displays a quick reference of RPM parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man rpm</code> — The RPM man page gives more detail about RPM parameters than the <code class="command">rpm --help</code> command.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-impressing.html"><strong>戻る</strong>B.4. Practical and 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="s2-rpm-useful-websites.html"><strong>次へ</strong>B.5.2. 役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-impressing.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-impressing.html
new file mode 100644
index 0000000..1883c7c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-impressing.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>B.4. Practical and 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-RPM.html" title="付録B RPM" /><link rel="prev" href="s2-keys-checking.html" title="B.3.2. Verifying Signature of Packages" /><link rel="next" href="s1-rpm-additional-resources.html" title="B.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-keys-checking.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n
" href="s1-rpm-additional-resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-rpm-impressing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.4. Practical and Common Examples of RPM Usage</h2></div></div></div><a id="idm49701312" class="indexterm"></a><a id="idm49699872" class="indexterm"></a><div class="para">
+ RPM is a useful tool for both managing your system and diagnosing and fixing problems. The best way to make sense of all its options is to look at some examples.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 誤って何らかのファイルを削除してしまったものの、 何を削除したかわからないとします。 システム全体を検証して足りないものを調べるには、以下のコマンドを試すことができます。
+ </div><a id="idm20215600" class="indexterm"></a><a id="idm20214192" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre><div class="para">
+ 足りないファイルがあるか、壊れているファイルが あるように見える場合は、おそらくパッケージを再インストールするか、いったんアンインストールして 再インストールする必要があります。
+ </div></li><li class="listitem"><div class="para">
+ 所属先のわからないファイルを見つけたとします。そのファイルが含まれるパッケージを検索するには、以下のように入力します。
+ </div><a id="idm60527696" class="indexterm"></a><a id="idm60526288" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qf /usr/bin/ghostscript</code>
+</pre><div class="para">
+ 出力は以下のようになります。
+ </div><pre class="screen">ghostscript-8.70-1.fc17.x86_64</pre></li><li class="listitem"><div class="para">
+ We can combine the above two examples in the following scenario. Say you are having problems with <code class="filename">/usr/bin/paste</code>. You would like to verify the package that owns that program, but you do not know which package owns <code class="command">paste</code>. Enter the following command,
+ </div><pre class="screen">
+<code class="command">rpm -Vf /usr/bin/paste</code>
+</pre><div class="para">
+ 該当するパッケージが検証されます。
+ </div></li><li class="listitem"><div class="para">
+ 特定のプログラムに関して詳細な情報が必要 なら、次のコマンドを入力して、そのプログラムの入った パッケージに付随するドキュメントを検索することが できます。
+ </div><a id="idm62303296" class="indexterm"></a><a id="idm53261328" class="indexterm"></a><a id="idm53259920" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qdf /usr/bin/free</code>
+</pre><div class="para">
+ 出力は以下のようになります。
+ </div><pre class="screen">/usr/share/doc/procps-3.2.8/BUGS
+/usr/share/doc/procps-3.2.8/FAQ
+/usr/share/doc/procps-3.2.8/NEWS
+/usr/share/doc/procps-3.2.8/TODO
+/usr/share/man/man1/free.1.gz
+/usr/share/man/man1/pgrep.1.gz
+/usr/share/man/man1/pkill.1.gz
+/usr/share/man/man1/pmap.1.gz
+/usr/share/man/man1/ps.1.gz
+/usr/share/man/man1/pwdx.1.gz
+/usr/share/man/man1/skill.1.gz
+/usr/share/man/man1/slabtop.1.gz
+/usr/share/man/man1/snice.1.gz
+/usr/share/man/man1/tload.1.gz
+/usr/share/man/man1/top.1.gz
+/usr/share/man/man1/uptime.1.gz
+/usr/share/man/man1/w.1.gz
+/usr/share/man/man1/watch.1.gz
+/usr/share/man/man5/sysctl.conf.5.gz
+/usr/share/man/man8/sysctl.8.gz
+/usr/share/man/man8/vmstat.8.gz</pre></li><li class="listitem"><div class="para">
+ 新しい<span class="application"><strong>RPM</strong></span>パッケージ が見つかったものの、それが何であるかがわからないと します。それに関する情報を検索するには、以下のコマンド を使用します。
+ </div><a id="idm41604224" class="indexterm"></a><a id="idm41602816" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qip crontabs-1.10-31.fc17.noarch.rpm</code>
+</pre><div class="para">
+ 出力は以下のようになります。
+ </div><pre class="screen">Name : crontabs Relocations: (not relocatable)
+Size : 2486 License: Public Domain and GPLv2
+Signature : RSA/SHA1, Tue 11 Aug 2009 01:11:19 PM CEST, Key ID 9d1cc34857bbccba
+Packager : Fedora Project
+Summary : Root crontab files used to schedule the execution of programs
+Description :
+The crontabs package contains root crontab files and directories.
+You will need to install cron daemon to run the jobs from the crontabs.
+The cron daemon such as cronie or fcron checks the crontab files to
+see when particular commands are scheduled to be executed. If commands
+are scheduled, it executes them.
+Crontabs handles a basic system function, so it should be installed on
+your system.</pre></li><li class="listitem"><div class="para">
+ Perhaps you now want to see what files the <code class="filename">crontabs</code> RPM package installs. You would enter the following:
+ </div><a id="idm29564864" class="indexterm"></a><a id="idm29563456" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qlp crontabs-1.10-31.fc17.noarch.rpm</code>
+</pre><div class="para">
+ 出力は以下のようになります。
+ </div><pre class="screen">/etc/cron.daily
+/etc/cron.hourly
+/etc/cron.monthly
+/etc/cron.weekly
+/etc/crontab
+/usr/bin/run-parts
+/usr/share/man/man4/crontabs.4.gz</pre></li></ul></div><div class="para">
+ These are just a few examples. As you use RPM, you may find more uses for it.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-keys-checking.html"><strong>戻る</strong>B.3.2. Verifying Signature of 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-additional-resources.html"><strong>次へ</strong>B.5. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-using.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-using.html
new file mode 100644
index 0000000..319c7e2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-rpm-using.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>B.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-RPM.html" title="付録B RPM" /><link rel="prev" href="ch-RPM.html" title="付録B RPM" /><link rel="next" href="sec-Installing_and_Upgrading.html" title="B.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-RPM.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and
_Upgrading.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">B.2. RPMの使用法</h2></div></div></div><div class="para">
+ RPM has five basic modes of operation
+ <a id="idm62945952" 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 <code class="command">man rpm</code>. You can also refer to <a class="xref" href="s1-rpm-additional-resources.html">「その他のリソース」</a> for more information on RPM.
+ </div><div class="section" id="s2-rpm-finding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.1. RPM パッケージの検索</h3></div></div></div><a id="idm67721536" class="indexterm"></a><a id="idm49559056" class="indexterm"></a><div class="para">
+ Before using any RPM packages, you must know where to find them. An Internet search returns many RPM repositories, but if you are looking for Red Hat RPM packages, they can be found at the following locations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The Fedora installation media
+ <a id="idm52753680" class="indexterm"></a>
+ <a id="idm61129840" class="indexterm"></a>
+ contain many installable RPMs.
+ </div></li><li class="listitem"><div class="para">
+ The initial RPM repositories provided with the YUM package manager
+ <a id="idm46739392" class="indexterm"></a>
+ <a id="idm67386592" class="indexterm"></a>
+ . Refer to <a class="xref" href="ch-yum.html">4章<em>Yum</em></a> for details on how to use the official Fedora package repositories.
+ </div></li><li class="listitem"><div class="para">
+ The active Fedora mirrors contains many installable RPMs: <a href="http://mirrors.fedoraproject.org/publiclist/">http://mirrors.fedoraproject.org/publiclist/</a>.
+ </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>Third-party repositories and package compatibility</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="ch-RPM.html"><strong>戻る</strong>付録B 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="sec-Installing_and_Upgrading.html"><strong>次へ</strong>B.2.2. インストールとアップグレード</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-services-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-services-additional-resources.html
new file mode 100644
index 0000000..dce745d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>8.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Services_and_Daemons.html" title="第8章 サービスおよびデーモン" /><link rel="prev" href="s3-services-running-restarting.html" title="8.2.4. サービスの再起動" /><link rel="next" href="s2-services-additional-resources-books.html" title="8.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">8.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">8.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>8.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>8.3.2. 関連書籍</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-services-running.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-services-running.html
new file mode 100644
index 0000000..19139b5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>8.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Services_and_Daemons.html" title="第8章 サービスおよびデーモン" /><link rel="prev" href="ch-Services_and_Daemons.html" title="第8章 サービスおよびデーモン" /><link rel="next" href="s3-services-running-running.html" title="8.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">8.2. サービスの実行</h2></div></div></div><a id="idm69609264" class="indexterm"></a><a id="idm69607152" 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">8.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>例8.3 httpd サービスの状態の確認</h6><div class="example-contents"><div class="para">
+ <a class="xref" href="ch-Services_and_Daemons.html#exam-services-configuration-enabling">例8.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>例8.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>第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="s3-services-running-running.html"><strong>次へ</strong>8.2.2. サービスの実行</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-ssh-beyondshell.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-ssh-beyondshell.html
new file mode 100644
index 0000000..2e8e326
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>10.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-OpenSSH.html" title="第10章 OpenSSH" /><link rel="prev" href="s2-ssh-clients-sftp.html" title="10.3.3. sftp ユーティリティの使用方法" /><link rel="next" href="s2-ssh-beyondshell-tcpip.html" title="10.4.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">10.4. 安全なシェル以上のもの</h2></div></div></div><div class="para">
+ 安全なコマンドラインインターフェイスは、 SSH が使用できる多くの方法の単なる一部分です。充分なバンド幅があれば、 X11 セッションは １ つの 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">10.4.1. X11 転送</h3></div></div></div><a id="idm54680800" 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">
+ たとえば、ユーザー名に <code class="systemitem">john</code> を用いて、<code class="systemitem">penguin.example.com</code> という名前のリモートマシンにログインするには、次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">ssh -Y john at penguin.example.com</code>
+john at penguin.example.com's password:</pre><div class="para">
+ 安全なシェルプロンプトから X プログラムが実行されると、 SSH クライアントとサーバーは新しい安全なチャンネルを作成し、 X プログラムデータはそのチャンネルを通じて透過的にクライアントマシンに送信されます。
+ </div><div class="para">
+ X11 転送は非常に有用です。<span class="application"><strong>プリンター設定</strong></span>ユーティリティのセキュアな対話式セッションを作成するために使用できます。これをするために、<span class="application"><strong>ssh</strong></span> を使用してサーバーに接続して、次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">system-config-printer &</code></pre><div class="para">
+ <span class="application"><strong>プリンター設定ツール</strong></span>が表示され、リモートユーザーがリモートシステムにある印刷環境を安全に設定できるようになります。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-clients-sftp.html"><strong>戻る</strong>10.3.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>10.4.2. ポート転送</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-ssh-clients.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-ssh-clients.html
new file mode 100644
index 0000000..4dc6c9a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-ssh-clients.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>10.3. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-OpenSSH.html" title="第10章 OpenSSH" /><link rel="prev" href="s2-ssh-configuration-keypairs.html" title="10.2.4. キー認証の使用" /><link rel="next" href="s2-ssh-clients-scp.html" title="10.3.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="s2-ssh-configuration-keypairs.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">10.3. OpenSSH クライアント</h2></div></div></div><a id="idm37788576" class="indexterm"></a><div class="note"><div class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div class="admonition"><div class="para">
+ クライアントマシンから OpenSSH サーバーに接続するには、<span class="package">openssh-clients</span> および <span class="package">openssh</span> パッケージをインストールしなければいけません。Fedora に新しいパッケージをインストールする方法は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</a>を参照してください。
+ </div></div></div><div class="section" id="s2-ssh-clients-ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.1. ssh ユーティリティの使用方法</h3></div></div></div><a id="idm45314032" class="indexterm"></a><a id="idm45312112" class="indexterm"></a><div class="para">
+ <code class="command">ssh</code> はリモートマシンにログインしたり、そこでコマンドを実行したりできます。<code class="command">rlogin</code>, <code class="command">rsh</code>, および <code class="command">telnet</code> プログラムのセキュアな代替品です。
+ </div><div class="para">
+ <code class="command">telnet</code> と同じように、<code class="systemitem">penguin.example.com</code> というリモートマシンにログインするには、シェルプロンプトにおいて以下のコマンドを入力します:
+ </div><pre class="screen">~]$ <code class="command">ssh penguin.example.com</code></pre><div class="para">
+ これはローカルマシンにおいて使用しているものと同じユーザー名を用いてログインします。異なるものを指定したい場合、<code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code> 形式でコマンドを使用します。たとえば、<code class="systemitem">john</code> としてログインするには、このように入力します:
+ </div><pre class="screen">~]$ <code class="command">ssh john at penguin.example.com</code></pre><div class="para">
+ はじめて接続するとき、このようなメッセージが表示されます:
+ </div><pre class="screen">The authenticity of host 'penguin.example.com' can't be established.
+RSA key fingerprint is 94:68:3a:3a:bc:f3:9a:9b:01:5d:b3:07:38:e2:11:0c.
+Are you sure you want to continue connecting (yes/no)?</pre><div class="para">
+ 確認するために <strong class="userinput"><code>yes</code></strong> と入力します。サーバーが既知のホストのリストに追加されることに注意してください。そして、パスワードを問い合わせるプロンプトが出ます:
+ </div><pre class="screen">Warning: Permanently added 'penguin.example.com' (RSA) to the list of known hosts.
+john at penguin.example.com's password:</pre><div class="important"><div class="admonition_header"><h2>SSH サーバーのホストキーの更新方法</h2></div><div class="admonition"><div class="para">
+ SSH サーバーのホストキーが変更されると、サーバーのホストキーが <code class="filename">~/.ssh/known_hosts</code> ファイルから削除されるまで接続を進めることができないことを、クライアントがユーザーに通知します。そうするには、テキストエディターでファイルを開いて、先頭にリモートマシン名を含む行を削除します。しかし、これを実行する前に、サーバーが侵入されていないことを確認するために、SSH サーバーのシステム管理者に問い合わせてください。
+ </div></div></div><div class="para">
+ パスワードを入力した後、リモートマシンのシェルプロンプトを提供されます。
+ </div><div class="para">
+ 代わりに、<code class="command">ssh</code> プログラムがシェルプロンプトにログインすることなく、リモートマシンにおいてコマンドを実行するためにも使うことができます。そのための構文は <code class="command">ssh [<em class="replaceable"><code>username</code></em>@]<em class="replaceable"><code>hostname</code></em> <em class="replaceable"><code>command</code></em></code> です。たとえば、<code class="systemitem">penguin.example.com</code>において <code class="command">whoami</code> コマンドを実行したいならば、次のように入力します:
+ </div><pre class="screen">~]$ <code class="command">ssh john at penguin.example.com whoami</code>
+john at penguin.example.com's password:
+john</pre><div class="para">
+ 正しいパスワードが入力された後、ユーザー名が表示され、ローカルのシェルプロンプトに戻ってきます。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-keypairs.html"><strong>戻る</strong>10.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-ssh-clients-scp.html"><strong>次へ</strong>10.3.2. scp ユーティリティの使用方法</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-ssh-configuration.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-ssh-configuration.html
new file mode 100644
index 0000000..0be1b82
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-ssh-configuration.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>10.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-OpenSSH.html" title="第10章 OpenSSH" /><link rel="prev" href="ch-OpenSSH.html" title="第10章 OpenSSH" /><link rel="next" href="s2-ssh-configuration-sshd.html" title="10.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-conf
iguration-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">10.2. 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">10.2.1. 設定ファイル</h3></div></div></div><a id="idm54263408" 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="idm42060336" class="indexterm"></a><div class="para">
+ システム全体の SSH 設定ファイルは <code class="filename">/etc/ssh/</code> ディレクトリに保存されてます。詳細は<a class="xref" href="s1-ssh-configuration.html#table-ssh-configuration-configs-system">表10.1「システム全体の設定ファイル」</a>を参照してください。
+ </div><div class="table" id="table-ssh-configuration-configs-system"><h6>表10.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="">
+ 設定ファイル
+ </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_dsa_key</code>
+ </td><td class="">
+ <code class="command">sshd</code> デーモンにより使用される DSA 秘密鍵です。
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/ssh/ssh_host_dsa_key.pub</code>
+ </td><td class="">
+ <code class="command">sshd</code> デーモンにより使用される DSA 公開鍵です。
+ </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="">
+ SSH プロトコルのバージョン2用の <code class="command">sshd</code> デーモンにより使用される RSA 公開鍵です。
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="idm98824288" class="indexterm"></a><div class="para">
+ ユーザー固有の SSH 設定ファイルは、ユーザーのホームディレクトリにある <code class="filename">~/.ssh/</code> ディレクトリに保存されます。詳細は<a class="xref" href="s1-ssh-configuration.html#table-ssh-configuration-configs-user">表10.2「ユーザー固有の設定ファイル」</a>を参照してください。
+ </div><div class="table" id="table-ssh-configuration-configs-user"><h6>表10.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="">
+ 設定ファイル
+ </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_dsa</code>
+ </td><td class="">
+ ユーザーの DSA 秘密鍵を含みます。
+ </td></tr><tr><td class="">
+ <code class="filename">~/.ssh/id_dsa.pub</code>
+ </td><td class="">
+ ユーザーの DSA 公開鍵です。
+ </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="">
+ SSH プロトコルのバージョン2用の <code class="command">ssh</code> により使用される RSA 鍵です。
+ </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="">
+ ユーザーによりアクセスされた SSH サーバーの DSA ホスト・キーを含みます。このファイルは SSH クライアントが正しい SSH サーバーに接続していることを確実にするために非常に重要です。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ SSH の設定ファイルにおいて利用可能なさまざまなディレクティブに関する詳細は、<code class="command">ssh_config</code> および <code class="command">sshd_config</code> のマニュアルページを参照してください。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-OpenSSH.html"><strong>戻る</strong>第10章 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>10.2.2. OpenSSH サーバーの起動</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysconfig-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysconfig-additional-resources.html
new file mode 100644
index 0000000..41b232c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysconfig-additional-resources.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>D.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-The_sysconfig_Directory.html" title="付録D sysconfig ディレクトリー" /><link rel="prev" href="s1-sysconfig-etcsysconf-dir.html" title="D.2. Directories in the /etc/sysconfig/ Directory" /><link rel="next" href="ch-proc.html" title="付録E The proc File 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="previous"><a accesskey="p" href="s1-sysconfig-etcsysconf-dir.html"><str
ong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ch-proc.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-sysconfig-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">D.3. その他のリソース</h2></div></div></div><a id="idm57934032" class="indexterm"></a><div class="para">
+ This chapter is only intended as an introduction to the files in the <code class="filename">/etc/sysconfig/</code> directory. The following source contains more comprehensive information.
+ </div><div class="section" id="s2-sysconfig-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">D.3.1. インストールされているドキュメント</h3></div></div></div><a id="idm57929568" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code>version</code></em>/sysconfig.txt</code></span></dt><dd><div class="para">
+ A more authoritative listing of the files found in the <code class="filename">/etc/sysconfig/</code> directory and the configuration options available for them.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysconfig-etcsysconf-dir.html"><strong>戻る</strong>D.2. Directories in the /etc/sysconfig/ 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="ch-proc.html"><strong>次へ</strong>付録E The proc File System</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysconfig-etcsysconf-dir.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysconfig-etcsysconf-dir.html
new file mode 100644
index 0000000..ca29c8c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysconfig-etcsysconf-dir.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>D.2. Directories in the /etc/sysconfig/ 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-The_sysconfig_Directory.html" title="付録D sysconfig ディレクトリー" /><link rel="prev" href="ch-The_sysconfig_Directory.html" title="付録D sysconfig ディレクトリー" /><link rel="next" href="s1-sysconfig-additional-resources.html" title="D.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-The_sysconfig_Direc
tory.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-sysconfig-additional-resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-sysconfig-etcsysconf-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">D.2. Directories in the /etc/sysconfig/ Directory</h2></div></div></div><a id="idm34074608" class="indexterm"></a><div class="para">
+ The following directories are normally found in <code class="filename">/etc/sysconfig/</code>.
+ </div><a id="idm34071456" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/cbq/</code> </span></dt><dd><div class="para">
+ <a id="idm34066240" class="indexterm"></a>
+ This directory contains the configuration files needed to do <em class="firstterm">Class Based Queuing</em> for bandwidth management on network interfaces. CBQ divides user traffic into a hierarchy of classes based on any combination of IP addresses, protocols, and application types.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/networking/</code> </span></dt><dd><div class="para">
+ <a id="idm51987040" class="indexterm"></a>
+ This directory is used by the <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>), and its contents should not be edited manually.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/network-scripts/</code> </span></dt><dd><div class="para">
+ <a id="idm44846112" class="indexterm"></a>
+ This directory contains the following network-related configuration files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Network configuration files for each configured network interface, such as <code class="filename">ifcfg-eth0</code> for the <code class="systemitem">eth0</code> Ethernet interface.
+ </div></li><li class="listitem"><div class="para">
+ Scripts used to bring network interfaces up and down, such as <code class="command">ifup</code> and <code class="command">ifdown</code>.
+ </div></li><li class="listitem"><div class="para">
+ Scripts used to bring ISDN interfaces up and down, such as <code class="command">ifup-isdn</code> and <code class="command">ifdown-isdn</code>.
+ </div></li><li class="listitem"><div class="para">
+ 直接編集すべきではない各種共有のネットワーク機能スクリプト。
+ </div></li></ul></div><div class="para">
+ For more information on the <code class="filename">/etc/sysconfig/network-scripts/</code> directory, refer to <a class="xref" href="ch-Network_Interfaces.html">7章<em>ネットワーク・インターフェース</em></a>.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_sysconfig_Directory.html"><strong>戻る</strong>付録D sysconfig ディレクトリー</a></li><li class="up"><a accesskey="u" href="#"><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-sysconfig-additional-resources.html"><strong>次へ</strong>D.3. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysinfo-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysinfo-additional-resources.html
new file mode 100644
index 0000000..6b18bd6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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/17/html/System_Administrators_Guide/s1-sysinfo-cpu.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysinfo-cpu.html
new file mode 100644
index 0000000..65df9bc
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm19986336" class="indexterm"></a><a id="idm19984896" 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="idm73094912" class="indexterm"></a><a id="idm73093792" 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/17/html/System_Administrators_Guide/s1-sysinfo-filesystems.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysinfo-filesystems.html
new file mode 100644
index 0000000..5b07331
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm52491504" class="indexterm"></a><a id="idm52490096" 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="idm32545280" 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/17/html/System_Administrators_Guide/s1-sysinfo-hardware.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysinfo-hardware.html
new file mode 100644
index 0000000..b746546
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm19214080" class="indexterm"></a><a id="idm19212640" 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="idm55678016" 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/17/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html
new file mode 100644
index 0000000..5440b8c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm43621968" class="indexterm"></a><a id="idm66703136" class="indexterm"></a><a id="idm66702176" 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="idm66700256" 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/17/html/System_Administrators_Guide/s1-users-configui.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-users-configui.html
new file mode 100644
index 0000000..473df3c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="第3章 ユーザーとグループの管理" /><link rel="prev" href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html" title="3.2.3. ユーザーの削除" /><link rel="next" href="s2-redhat-config-users-user-new.html" title="3.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 acc
esskey="p" href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-redhat-config-users-user-new.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">3.3. ユーザー管理のツールを使う</h2></div></div></div><a id="idm61302768" class="indexterm"></a><a id="idm61301328" class="indexterm"></a><a id="idm61299888" class="indexterm"></a><a id="idm56510736" class="indexterm"></a><a id="idm56509328" class="indexterm"></a><a id="idm56507920" class="indexterm"></a><div class="para">
+ <span class="application"><strong>ユーザー管理</strong></span>アプリケーションにより、グラフィカルユーザーインターフェースにおいてローカルユーザーとグループを表示、編集、追加および削除できます。アプリケーションを起動するには、<span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>その他</strong></span> → <span class="guimenuitem"><strong>ユーザーとグループ</strong></span>を選択するか、シェルプロンプトにおいて <code class="command">system-config-users</code> と入力します。スーパーユーザー権限がなければ、アプリケーションが <code class="systemitem">root</code> として認証するプロンプトを表示することに注意してください。
+ </div><div class="section" id="s2-redhat-config-users-list"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.1. ユーザーとグループを閲覧する</h3></div></div></div><a id="idm57157712" class="indexterm"></a><a id="idm57156304" class="indexterm"></a><div class="para">
+ <span class="application"><strong>ユーザー管理</strong></span>のメインウィンドウは2つのタブに分けられています: <span class="guilabel"><strong>ユーザー</strong></span>タブは、ローカルユーザーの一覧とそのユーザー ID、プライマリグループ、ホームディレクトリ、ログインシェル、およびフルネームに関する追加情報を提供します。<span class="guilabel"><strong>グループ</strong></span>タブは、ローカルグループの一覧とそのグループ ID およびグループのメンバーに関する追加情報を提供します。
+ </div><div class="figure" id="fig-Users_Groups-User_Manager"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager.png" alt="ユーザーとグループを閲覧する" /><div class="longdesc"><div class="para">
+ ユーザーとグループを閲覧する
+ </div></div></div></div><h6>図3.5 ユーザーとグループを閲覧する</h6></div><br class="figure-break" /><div class="para">
+ 特定のユーザーまたはグループを検索するには、<span class="guilabel"><strong>検索フィルター</strong></span>フィールドに最初の数文字を入力して、<span class="keycap"><strong>Enter</strong></span> を押すか、<span class="guibutton"><strong>フィルターの適用</strong></span>ボタンをクリックします。列のヘッダーをクリックすると、利用可能な列は何でも項目を並べ替えることができます。
+ </div><div class="para">
+ Fedora は、1000未満のユーザー ID とグループ ID をシステムユーザーとグループのために予約しています。デフォルトで、<span class="application"><strong>ユーザー管理</strong></span>はシステムユーザーを表示しません。すべてのユーザーとグループを表示するには、<span class="guilabel"><strong>設定</strong></span>ダイアログを開くために<span class="guimenu"><strong>編集</strong></span> → <span class="guimenuitem"><strong>設定</strong></span>を選択して、<span class="guilabel"><strong>システムユーザーとグループを非表示</strong></span>チェックボックスを外します。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html"><strong>戻る</strong>3.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-redhat-config-users-user-new.html"><strong>次へ</strong>3.3.2. 新規ユーザーを追加する</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-users-groups-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-users-groups-additional-resources.html
new file mode 100644
index 0000000..7b9c04d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-users-groups-additional-resources.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="第3章 ユーザーとグループの管理" /><link rel="prev" href="s2-users-tools-groups-directories.html" title="3.4.5. グループ用ディレクトリーの作成" /><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" hre
f="s2-users-tools-groups-directories.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="part-Package_Management.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-users-groups-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.5. その他のリソース</h2></div></div></div><a id="idm83459824" class="indexterm"></a><a id="idm83458384" class="indexterm"></a><div class="para">
+ ユーザーとグループの管理に関する詳細は以下のリソースを参照してください。
+ </div><div class="section" id="s2-users-groups-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.5.1. インストールされているドキュメント</h3></div></div></div><a id="idm35772752" class="indexterm"></a><a id="idm35770864" class="indexterm"></a><div class="para">
+ ユーザーとグループを管理するためのさまざまなユーティリティに関する詳細は、以下のマニュアルページを参照してください:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>chage</strong></span>(1) — パスワードのエージングポリシーとアカウントの期限切れ日を変更するためのコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>gpasswd</strong></span>(1) — <code class="filename">/etc/group</code> ファイルを管理するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>groupadd</strong></span>(8) — グループを追加するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>grpck</strong></span>(8) — <code class="filename">/etc/group</code> ファイルを検証するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>groupdel</strong></span>(8) — グループを削除するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>groupmod</strong></span>(8) — グループのメンバーを修正するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>pwck</strong></span>(8) — <code class="filename">/etc/passwd</code> と <code class="filename">/etc/shadow</code> ファイルを検証するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>pwconv</strong></span>(8) — 標準的なパスワードから shadow 形式のパスワードに変換するツールです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>pwunconv</strong></span>(8) — shadow 形式のパスワードから標準的なパスワードに変換するツールです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>useradd</strong></span>(8) — ユーザーを追加するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>userdel</strong></span>(8) — ユーザーを削除するコマンドです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>usermod</strong></span>(8) — ユーザーを修正するコマンドです。
+ </div></li></ul></div><div class="para">
+ 関連する設定ファイルに関する詳細は、以下を参照してください:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>group</strong></span>(5) — システムのグループ情報を含むファイルです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>passwd</strong></span>(5) — システムのユーザー情報を含むファイルです。
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>shadow</strong></span>(5) — パスワードおよびシステムに対するアカウント期限切れ情報を含むファイルです。
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-users-tools-groups-directories.html"><strong>戻る</strong>3.4.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="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/17/html/System_Administrators_Guide/s1-users-tools.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-users-tools.html
new file mode 100644
index 0000000..a6c4227
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-users-tools.html
@@ -0,0 +1,171 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="第3章 ユーザーとグループの管理" /><link rel="prev" href="s2-redhat-config-users-group-properties.html" title="3.3.5. グループのプロパティを変更する" /><link rel="next" href="s2-users-tools-groups-add.html" title="3.4.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 access
key="p" href="s2-redhat-config-users-group-properties.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">3.4. コマンドラインのツールを使う</h2></div></div></div><a id="idm69753152" class="indexterm"></a><a id="idm69751072" class="indexterm"></a><a id="idm69748992" class="indexterm"></a><a id="idm44098368" class="indexterm"></a><div class="para">
+ Fedora においてユーザーとグループを管理する最も簡単な方法は、<a class="xref" href="s1-users-configui.html">「ユーザー管理のツールを使う」</a>に説明されているように、<span class="application"><strong>ユーザー管理</strong></span>アプリケーションを使用することです。しかしながら、コマンドラインツールを好むか、X Window System をインストールしていなければ、<a class="xref" href="s1-users-tools.html#table-users-tools">表3.1「ユーザーとグループの管理のためのコマンドライン」</a>に一覧化されているコマンドラインユーティリティを使用できます。
+ </div><div class="table" id="table-users-tools"><h6>表3.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">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></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">3.4.1. 新規ユーザーを追加する</h3></div></div></div><a id="idm50902304" class="indexterm"></a><a id="idm50900576" class="indexterm"></a><a id="idm50899136" class="indexterm"></a><div class="para">
+ 新規ユーザーをシステムに追加するには、シェルプロンプトにおいて <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">
+ …ここで <em class="replaceable"><code>options</code></em> は<a class="xref" href="s1-users-tools.html#table-useradd-options">表3.2「useradd のコマンドライン オプション」</a>において説明されているコマンドラインオプションです。
+ </div><a id="idm59974176" 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">
+ オプションとして、パスワードエージングポリシーを設定することができます。パスワードエージングを有効にする方法は<a class="xref" href="s2-users-tools-password-aging.html">「パスワードエージングの有効化」</a>を参照してください。
+ </div><div class="table" id="table-useradd-options"><h6>表3.2 useradd のコマンドライン オプション</h6><div class="table-contents"><table summary="useradd のコマンドライン オプション" 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="">
+ パスワード期限切れ後にアカウントが無効化されるまでの日数です。<code class="literal">0</code> が指定されると、アカウントはパスワード期限切れ後すぐに無効化されます。<code class="literal">-1</code> が指定されると、アカウントはパスワード期限切れ後に無効化されません。
+ </td></tr><tr><td class="">
+ <code class="option">-g</code> <em class="replaceable"><code>group_name</code></em>
+ </td><td class="">
+ ユーザーのデフォルトグループのグループ名とグループ番号です。グループはここに指定される以前から存在していなければなりません。
+ </td></tr><tr><td class="">
+ <code class="option">-G</code> <em class="replaceable"><code>group_list</code></em>
+ </td><td class="">
+ ユーザーがメンバーとなる追加グループ (デフォルト以外) のグループ名とグループ番号をコンマで区切って入れます。グループはここに指定される以前から存在していなければなりません。
+ </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" /><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:501:501::/home/juan:/bin/bash</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">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">
+ オプションの <em class="firstterm">GECOS</em> 情報は空白のままです。
+ </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:501:</pre><div class="para">
+ ユーザーと同じ名前を持つグループは<em class="firstterm">ユーザープライベートグループ</em>と呼ばれます。ユーザープライベートグループの詳細は<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">
+ GID は <code class="filename">/etc/passwd</code> においてユーザー <code class="systemitem">juan</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 -l /home</code>
+total 4
+drwx------. 4 juan juan 4096 Mar 3 18:23 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">
+ <code class="filename">/etc/skel/</code> ディレクトリ（デフォルトのユーザー設定を含みます）の中にあるファイルが新規 <code class="filename">/home/juan/</code> ディレクトリの中にコピーされます:
+ </div><pre class="screen">~]# <code class="command">ls -la /home/juan</code>
+total 28
+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 Jun 22 2010 .bash_logout
+-rw-r--r--. 1 juan juan 176 Jun 22 2010 .bash_profile
+-rw-r--r--. 1 juan juan 124 Jun 22 2010 .bashrc
+drwxr-xr-x. 2 juan juan 4096 Jul 14 2010 .gnome2
+drwxr-xr-x. 4 juan juan 4096 Nov 23 15:09 .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="s2-redhat-config-users-group-properties.html"><strong>戻る</strong>3.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="s2-users-tools-groups-add.html"><strong>次へ</strong>3.4.2. 新規グループを追加する</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-additional-resources.html
new file mode 100644
index 0000000..885112a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-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>C.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-The_X_Window_System.html" title="付録C X Window System" /><link rel="prev" href="s1-x-fonts.html" title="C.4. フォント" /><link rel="next" href="s2-x-useful-websites.html" title="C.5.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-x-fonts.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="
s2-x-useful-websites.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-x-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.5. その他のリソース</h2></div></div></div><a id="idm49394736" class="indexterm"></a><div class="para">
+ X サーバー、このサーバーに接続されているクライアント、及びさまざまなデスクトップ環境とウィンドウマネージャについては他にも多量の詳細情報があります。
+ </div><div class="section" id="s2-x-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.5.1. インストールされているドキュメント</h3></div></div></div><a id="idm24469088" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/X11/doc/</code> — contains detailed documentation on the X Window System architecture, as well as how to get additional information about the Xorg project as a new user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/gdm-<em class="replaceable"><code><version-number></code></em>/README</code> — contains information on how display managers control user authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man xorg.conf</code> — Contains information about the <code class="filename">xorg.conf</code> configuration files, including the meaning and syntax for the different sections within the files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man Xorg</code> — Describes the <code class="command">Xorg</code> display server.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-fonts.html"><strong>戻る</strong>C.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-x-useful-websites.html"><strong>次へ</strong>C.5.2. 役に立つ Web サイト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-clients.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-clients.html
new file mode 100644
index 0000000..3e6c9ad
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-clients.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>C.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-The_X_Window_System.html" title="付録C X Window System" /><link rel="prev" href="ch-The_X_Window_System.html" title="付録C X Window System" /><link rel="next" href="s2-x-clients-winmanagers.html" title="C.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-The_X_Window_System.html"><strong>戻る</strong></a></li><l
i class="next"><a accesskey="n" href="s2-x-clients-winmanagers.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-x-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.2. デスクトップ環境とウィンドウマネージャ</h2></div></div></div><a id="idm56092016" class="indexterm"></a><div class="para">
+ Once an X server is running, X client applications can connect to it and create a GUI for the user. A range of GUIs are available with Fedora, from the rudimentary <em class="firstterm">Tab Window Manager</em> (twm) to the highly developed and interactive desktop environment (such as <em class="firstterm">GNOME</em> or <em class="firstterm">KDE</em>) that most Fedora users are familiar with.
+ </div><div class="para">
+ To create the latter, more comprehensive GUI, two main classes of X client application must connect to the X server: a <em class="firstterm">window manager</em> and a <em class="firstterm">desktop environment</em>.
+ </div><div class="section" id="s2-x-clients-desktop"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.2.1. デスクトップ環境</h3></div></div></div><a id="idm26453696" class="indexterm"></a><a id="idm26451584" class="indexterm"></a><a id="idm26449952" class="indexterm"></a><a id="idm49329232" class="indexterm"></a><a id="idm49327600" class="indexterm"></a><a id="idm49325488" class="indexterm"></a><div class="para">
+ A desktop environment integrates various X clients to create a common graphical user environment and a development platform.
+ </div><div class="para">
+ Desktop environments have advanced features allowing X clients and other running processes to communicate with one another, while also allowing all applications written to work in that environment to perform advanced tasks, such as drag-and-drop operations.
+ </div><div class="para">
+ Fedora provides two desktop environments:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>GNOME</em></span> — The default desktop environment for Fedora based on the GTK+ 2 graphical toolkit.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>KDE</em></span> — An alternative desktop environment based on the Qt 4 graphical toolkit.
+ </div></li></ul></div><div class="para">
+ Both GNOME and KDE have advanced-productivity applications, such as word processors, spreadsheets, and Web browsers; both also provide tools to customize the look and feel of the GUI. Additionally, if both the GTK+ 2 and the Qt libraries are present, KDE applications can run in GNOME and vice versa.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_X_Window_System.html"><strong>戻る</strong>付録C X Window 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="s2-x-clients-winmanagers.html"><strong>次へ</strong>C.2.2. ウィンドウマネージャ</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-fonts.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-fonts.html
new file mode 100644
index 0000000..5c4a22e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-fonts.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>C.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-The_X_Window_System.html" title="付録C X Window System" /><link rel="prev" href="s2-x-server-config-xorg.conf.html" title="C.3.3. The xorg.conf File" /><link rel="next" href="s1-x-additional-resources.html" title="C.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-x-server-config-xorg.conf.html"><strong>戻る</strong></a>
</li><li class="next"><a accesskey="n" href="s1-x-additional-resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-x-fonts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.4. フォント</h2></div></div></div><a id="idm61431472" class="indexterm"></a><a id="idm61429248" class="indexterm"></a><a id="idm61427024" class="indexterm"></a><a id="idm61424800" class="indexterm"></a><div class="para">
+ Fedora uses <em class="firstterm">Fontconfig</em> subsystem to manage and display fonts under the X Window System. It simplifies font management and provides advanced display features, such as anti-aliasing. This system is used automatically for applications programmed using the <code class="literal">Qt 3</code> or <code class="literal">GTK+ 2</code> graphical toolkits, or their newer versions.
+ </div><div class="para">
+ The Fontconfig font subsystem allows applications to directly access fonts on the system and use the <em class="firstterm">X FreeType interface library</em> (<em class="firstterm">Xft</em>) or other rendering mechanisms to render Fontconfig fonts with advanced features such as anti-aliasing. Graphical applications can use the Xft library with Fontconfig to draw text to the screen.
+ </div><div class="note"><div class="admonition_header"><h2>Font configuration</h2></div><div class="admonition"><div class="para">
+ Fontconfig uses the <code class="filename">/etc/fonts/fonts.conf</code> configuration file, which should not be edited by hand.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Fonts group</h2></div><div class="admonition"><div class="para">
+ Any system where the user expects to run remote X applications needs to have the <code class="systemitem">fonts</code> group installed. This can be done by selecting the group in the installer, and also by running the <code class="command">yum groupinstall fonts</code> command after installation.
+ </div></div></div><div class="section" id="s3-x-fonts-fontconfig-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.4.1. Fontconfig へのフォントの追加</h3></div></div></div><a id="idm30798752" class="indexterm"></a><div class="para">
+ Adding new fonts to the Fontconfig subsystem is a straightforward process:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To add fonts for an individual user, copy the new fonts into the <code class="filename">.fonts/</code> directory in the user's home directory.
+ </div><div class="para">
+ To add fonts system-wide, copy the new fonts into the <code class="filename">/usr/share/fonts/</code> directory. It is a good idea to create a new subdirectory, such as <code class="filename">local/</code> or similar, to help distinguish between user-installed and default fonts.
+ </div></li><li class="listitem"><div class="para">
+ Run the <code class="command">fc-cache</code> command as root to update the font information cache:
+ </div><pre class="screen"><code class="command">fc-cache <em class="replaceable"><code><path-to-font-directory></code></em></code></pre><div class="para">
+ In this command, replace <em class="replaceable"><code><path-to-font-directory></code></em> with the directory containing the new fonts (either <code class="filename">/usr/share/fonts/local/</code> or <code class="filename">/home/<em class="replaceable"><code><user></code></em>/.fonts/</code>).
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Interactive font installation</h2></div><div class="admonition"><div class="para">
+ Individual users may also install fonts interactively, by typing <code class="filename">fonts:///</code> into the <span class="application"><strong>Nautilus</strong></span> address bar, and dragging the new font files there.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x-server-config-xorg.conf.html"><strong>戻る</strong>C.3.3. The xorg.conf 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-x-additional-resources.html"><strong>次へ</strong>C.5. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-server-configuration.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-server-configuration.html
new file mode 100644
index 0000000..107256a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s1-x-server-configuration.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>C.3. X サーバー設定ファイル</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-The_X_Window_System.html" title="付録C X Window System" /><link rel="prev" href="s2-x-clients-winmanagers.html" title="C.2.2. ウィンドウマネージャ" /><link rel="next" href="s2-x-server-config-xorg.conf.d.html" title="C.3.2. The xorg.conf.d 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-x-clients-winmanagers.html"><strong>戻る<
/strong></a></li><li class="next"><a accesskey="n" href="s2-x-server-config-xorg.conf.d.html"><strong>次へ</strong></a></li></ul><div class="section" id="s1-x-server-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">C.3. X サーバー設定ファイル</h2></div></div></div><a id="idm56050640" class="indexterm"></a><a id="idm56048048" class="indexterm"></a><div class="para">
+ The X server is a single binary executable <code class="filename">/usr/bin/Xorg</code>; a symbolic link <code class="filename">X</code> pointing to this file is also provided. Associated configuration files are stored in the <code class="filename">/etc/X11/</code> and <code class="filename">/usr/share/X11/</code> directories.
+ </div><div class="para">
+ The X Window System supports two different configuration schemes. Configuration files in the <code class="filename">xorg.conf.d</code> directory contain preconfigured settings from vendors and from distribution, and these files should not be edited by hand. Configuration in the <code class="filename">xorg.conf</code> file, on the other hand, is done completely by hand but is not necessary in most scenarios.
+ </div><div class="note"><div class="admonition_header"><h2>When do you need the xorg.conf file?</h2></div><div class="admonition"><div class="para">
+ All necessary parameters for a display and peripherals are auto-detected and configured during installation. The configuration file for the X server, <code class="filename">/etc/X11/xorg.conf</code>, that was necessary in previous releases, is not supplied with the current release of the X Window System. It can still be useful to create the file manually to configure new hardware, to set up an environment with multiple video cards, or for debugging purposes.
+ </div></div></div><div class="para">
+ The <code class="filename">/usr/lib/xorg/modules/</code> (or <code class="filename">/usr/lib64/xorg/modules/</code>) directory contains X server modules that can be loaded dynamically at runtime. By default, only some modules in <code class="filename">/usr/lib/xorg/modules/</code> are automatically loaded by the X server.
+ </div><div class="para">
+ When Fedora 17 is installed, the configuration files for X are created using information gathered about the system hardware during the installation process by the HAL (Hardware Abstraction Layer) configuration back end. Whenever the X server is started, it asks HAL for the list of input devices and adds each of them with their respective driver. Whenever a new input device is plugged in, or an existing input device is removed, HAL notifies the X server about the change. Because of this notification system, devices using the <code class="systemitem">mouse</code>, <code class="systemitem">kbd</code>, or <code class="systemitem">vmmouse</code> driver configured in the <code class="filename">xorg.conf</code> file are, by default, ignored by the X server. Refer to <a class="xref" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-serverf">「The <code class="option">ServerFlags</code> section」</a> for further details. Additional configuration is provided in
the <code class="filename">/etc/X11/xorg.conf.d/</code> directory and it can override or augment any configuration that has been obtained through HAL.
+ </div><div class="section" id="s2-x-server-config-xorg.conf-struct"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.3.1. The Structure of the Configuration</h3></div></div></div><a id="idm56656560" class="indexterm"></a><a id="idm56653968" class="indexterm"></a><a id="idm68159824" class="indexterm"></a><div class="para">
+ The format of the X configuration files is comprised of many different sections which address specific aspects of the system hardware. Each section begins with a <code class="option">Section "<em class="replaceable"><code>section-name</code></em>"</code> line, where "<em class="replaceable"><code>section-name</code></em>" is the title for the section, and ends with an <code class="option">EndSection</code> line. Each section contains lines that include option names and one or more option values. Some of these are sometimes enclosed in double quotes (<code class="literal">"</code>).
+ </div><div class="para">
+ Some options within the <code class="filename">/etc/X11/xorg.conf</code> file accept a boolean switch which turns the feature on or off. The acceptable values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">1</code>, <code class="literal">on</code>, <code class="literal">true</code>, or <code class="literal">yes</code> — Turns the option on.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">0</code>, <code class="literal">off</code>, <code class="literal">false</code>, or <code class="literal">no</code> — Turns the option off.
+ </div></li></ul></div><div class="para">
+ The following shows a typical configuration file for the keyboard. Lines beginning with a hash sign (<code class="literal">#</code>) are not read by the X server and are used for human-readable comments.
+ </div><pre class="screen"># This file is autogenerated by system-setup-keyboard. Any
+# modifications will be lost.
+
+Section "InputClass"
+ Identifier "system-setup-keyboard"
+ MatchIsKeyboard "on"
+ Option "XkbModel" "pc105"
+ Option "XkbLayout" "cz,us"
+# Option "XkbVariant" "(null)"
+ Option "XkbOptions" "terminate:ctrl_alt_bksp,grp:shifts_toggle,grp_led:scroll"
+EndSection</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x-clients-winmanagers.html"><strong>戻る</strong>C.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-x-server-config-xorg.conf.d.html"><strong>次へ</strong>C.3.2. The xorg.conf.d Directory</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-at-batch-controlling-access.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-at-batch-controlling-access.html
new file mode 100644
index 0000000..2c55006
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-at-batch-controlling-access.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>19.2.5. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.4. その他のコマンドラインオプション" /><link rel="next" href="s2-autotasks-at-batch-service.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" h
ref="s2-autotasks-commandline-options.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-at-batch-service.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.5. at と batch へのアクセスの制御</h3></div></div></div><div class="para">
+ The <code class="filename">/etc/at.allow</code> and <code class="filename">/etc/at.deny</code> files can be used to restrict access to the <code class="command">at</code> and <code class="command">batch</code> commands. The format of both access control files is one username on each line. Whitespace is not permitted in either file. 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 access control files.
+ </div><div class="para">
+ If the file <code class="filename">at.allow</code> exists, only users listed in it 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-commandline-options.html"><strong>戻る</strong>19.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-autotasks-at-batch-service.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/17/html/System_Administrators_Guide/s2-autotasks-at-batch-service.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-at-batch-service.html
new file mode 100644
index 0000000..3ee2c8c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-at-batch-service.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-controlling-access.html" title="19.2.5. at と batch へのアクセスの制御" /><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-at-batch-controlling-access.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-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.6. サービスの起動と停止</h3></div></div></div><div class="para">
+ To start the <code class="command">at</code> service, use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl start atd.service</code></pre><div class="para">
+ To stop the service, as <code class="systemitem">root</code>, type the following at a shell prompt:
+ </div><pre class="screen"><code class="command">systemctl stop atd.service</code></pre><div class="para">
+ It is recommended that you start the service at boot time. To do so, run the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">systemctl enable atd.service</code></pre><div class="para">
+ Fedora においてサービスを設定する方法に関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-controlling-access.html"><strong>戻る</strong>19.2.5. 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="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/17/html/System_Administrators_Guide/s2-autotasks-at-batch-viewing.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-at-batch-viewing.html
new file mode 100644
index 0000000..361ca83
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.2. batch ジョブの設定" /><link rel="next" href="s2-autotasks-commandline-options.html" title="19.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-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.3. 保留ジョブの表示</h3></div></div></div><div class="para">
+ To view pending <code class="command">at</code> and <code class="command">batch</code> jobs, use 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 line. Each line follows the job number, date, hour, job class, and username 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.2. 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-commandline-options.html"><strong>次へ</strong>19.2.4. その他のコマンドラインオプション</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-batch-configuring.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-batch-configuring.html
new file mode 100644
index 0000000..2d5cdc3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-batch-configuring.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.2. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-batch-viewing.html" title="19.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-autotasks-at-batch.htm
l"><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.2. batch ジョブの設定</h3></div></div></div><div class="para">
+ To execute a one-time task when the load average is below 0.8, use the <code class="command">batch</code> command.
+ </div><div class="para">
+ After typing the <code class="command">batch</code> command, the <code class="prompt">at></code> prompt is displayed. Type the command to execute, press <span class="keycap"><strong>Enter</strong></span>, and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Multiple commands can be specified by typing each command followed by the <span class="keycap"><strong>Enter</strong></span> key. After typing all the commands, press <span class="keycap"><strong>Enter</strong></span> to go to a blank line and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Alternatively, a shell script can be entered at the prompt, pressing <span class="keycap"><strong>Enter</strong></span> after each line in the script, and pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script is entered, the shell
used is 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). As soon as the load average is below 0.8, the set of commands or script is executed.
+ </div><div class="para">
+ 標準出力に情報を表示するコマンドやスクリプトを入力した場合、この出力はユーザーに電子メールで送信されます。
+ </div><div class="para">
+ Use the command <code class="command">atq</code> to view pending jobs. Refer to <a class="xref" href="s2-autotasks-at-batch-viewing.html">「保留ジョブの表示」</a> for more information.
+ </div><div class="para">
+ Usage of the <code class="command">batch</code> command can be restricted. For more information, refer to <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="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-batch-viewing.html"><strong>次へ</strong>19.2.3. 保留ジョブの表示</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-commandline-options.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-autotasks-commandline-options.html
new file mode 100644
index 0000000..e4a548b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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.3. 保留ジョブの表示" /><link rel="next" href="s2-autotasks-at-batch-controlling-access.html" title="19.2.5. 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.4. その他のコマンドラインオプション</h3></div></div></div><div class="para">
+ Additional command line options for <code class="command">at</code> and <code class="command">batch</code> include:
+ </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.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-autotasks-at-batch-controlling-access.html"><strong>次へ</strong>19.2.5. at と batch へのアクセスの制御</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-additional-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-additional-resources.html
new file mode 100644
index 0000000..194359e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-additional-resources.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>12.2.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-BIND.html" title="12.2. BIND" /><link rel="prev" href="s2-bind-mistakes.html" title="12.2.6. よくある間違いを避けるために" /><link rel="next" href="ch-Web_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-bind-mistakes.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="
n" href="ch-Web_Servers.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-bind-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.7. その他のリソース</h3></div></div></div><div class="para">
+ 以下の情報源は、 BIND に関する追加情報を提供します。
+ </div><div class="section" id="s3-bind-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.7.1. インストールされているドキュメント</h4></div></div></div><a id="idm74678624" class="indexterm"></a><div class="para">
+ BIND features a full range of installed documentation covering many different topics, each placed in its own subject directory. For each item below, replace <em class="replaceable"><code>version</code></em> with the version of the <span class="package">bind</span> package installed on the system:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/</code></span></dt><dd><div class="para">
+ メインディレクトリに最新のドキュメントがあります。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/arm/</code></span></dt><dd><div class="para">
+ The directory containing the <em class="citetitle">BIND 9 Administrator Reference Manual</em> in HTML and SGML formats, which details BIND resource requirements, how to configure different types of nameservers, how to perform load balancing, and other advanced topics. For most new users of BIND, this is the best place to start.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/draft/</code></span></dt><dd><div class="para">
+ The directory containing assorted technical documents that review issues related to the DNS service, and propose some methods to address them.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/misc/</code></span></dt><dd><div class="para">
+ The directory designed to address specific advanced issues. Users of BIND version 8 should consult the <code class="filename">migration</code> document for specific changes they must make when moving to BIND 9. The <code class="filename">options</code> file lists all of the options implemented in BIND 9 that are used in <code class="filename">/etc/named.conf</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/rfc/</code></span></dt><dd><div class="para">
+ BIND に関連するすべての RFC ドキュメントを提供しているディレクトリーです。
+ </div></dd></dl></div><div class="para">
+ There is also a number of man pages for the various applications and configuration files involved with BIND:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">man rndc</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">rndc</code> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man named</code></span></dt><dd><div class="para">
+ The manual page for <code class="systemitem">named</code> containing the documentation on assorted arguments that can be used to control the BIND nameserver daemon.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man lwresd</code></span></dt><dd><div class="para">
+ The manual page for <code class="systemitem">lwresd</code> containing the full documentation on the lightweight resolver daemon and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man named.conf</code></span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="systemitem">named</code> configuration file.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man rndc.conf</code></span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="command">rndc</code> configuration file.
+ </div></dd></dl></div></div><div class="section" id="s3-bind-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.7.2. 役に立つ Web サイト</h4></div></div></div><a id="idm47838608" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.isc.org/software/bind">http://www.isc.org/software/bind</a></span></dt><dd><div class="para">
+ <em class="citetitle">BIND 9 Administrator Reference Manual</em> の PDF バージョンなど現在のリリースに関する情報が含まれている、BIND プロジェクトのホームページです。
+ </div></dd></dl></div></div><div class="section" id="s3-bind-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.7.3. 関連書籍</h4></div></div></div><a id="idm69999424" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="citetitle">DNS and BIND</em>、Paul Albitz and Cricket Liu; O'Reilly & Associates</span></dt><dd><div class="para">
+ 一般的な設定オプションと難解なもの両方を説明している人気のあるリファレンスです。また、DNS サーバーをセキュア化するための手法を提供しています。
+ </div></dd><dt class="varlistentry"><span class="term"><em class="citetitle">The Concise Guide to DNS and BIND</em>、Nicolai Langfeldt; Que</span></dt><dd><div class="para">
+ Looks at the connection between multiple network services and BIND, with an emphasis on task-oriented, technical topics.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-mistakes.html"><strong>戻る</strong>12.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="ch-Web_Servers.html"><strong>次へ</strong>第13章 ウェブ サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-dig.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-dig.html
new file mode 100644
index 0000000..30da799
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-dig.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.2.4. dig ユーティリティの使用</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-BIND.html" title="12.2. BIND" /><link rel="prev" href="s2-bind-rndc.html" title="12.2.3. rndc ユーティリティの使用法" /><link rel="next" href="s2-bind-features.html" title="12.2.5. BIND の高度な機能" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-bind-rndc.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s
2-bind-features.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-bind-dig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.4. dig ユーティリティの使用</h3></div></div></div><a id="idm56087392" class="indexterm"></a><div class="para">
+ <code class="command">dig</code> ユーティリティは、DNS 検索の実行およびネームサーバーの設定のデバッグを実行できるようにするコマンドラインツールです。その典型的な使用方法は以下のとおりです:
+ </div><pre class="screen"><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>type</code></em></pre><div class="para">
+ 一般的な <em class="replaceable"><code>type</code></em> の一覧は<a class="xref" href="s2-bind-zone.html#s4-bind-zone-rr">「Common Resource Records」</a>を参照してください。
+ </div><div class="section" id="s3-bind-dig-ns"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.4.1. ネームサーバーの検索</h4></div></div></div><div class="para">
+ 特定のドメインに対するネームサーバーを検索するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> NS</pre><div class="para">
+ <a class="xref" href="s2-bind-dig.html#example-bind-dig-ns">例12.16「ネームサーバーの検索例」</a>において、<code class="command">dig</code> ユーティリティが <code class="systemitem">example.com</code> のネームサーバーを表示するために使用されます。
+ </div><div class="example" id="example-bind-dig-ns"><h6>例12.16 ネームサーバーの検索例</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com NS</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com NS
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57883
+;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN NS
+
+;; ANSWER SECTION:
+example.com. 99374 IN NS a.iana-servers.net.
+example.com. 99374 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:04:06 2010
+;; MSG SIZE rcvd: 77</pre></div></div><br class="example-break" /></div><div class="section" id="s3-bind-dig-a"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.4.2. IP アドレスの検索</h4></div></div></div><div class="para">
+ 特定のドメインに割り当てられた IP アドレスを検索するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> A</pre><div class="para">
+ <a class="xref" href="s2-bind-dig.html#example-bind-dig-a">例12.17「IP アドレスの検索例」</a>において、<code class="command">dig</code> ユーティリティが <code class="systemitem">example.com</code> の IP アドレスを表示するために使用されます。
+ </div><div class="example" id="example-bind-dig-a"><h6>例12.17 IP アドレスの検索例</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com A</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com A
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4849
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN A
+
+;; ANSWER SECTION:
+example.com. 155606 IN A 192.0.32.10
+
+;; AUTHORITY SECTION:
+example.com. 99175 IN NS a.iana-servers.net.
+example.com. 99175 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:07:25 2010
+;; MSG SIZE rcvd: 93</pre></div></div><br class="example-break" /></div><div class="section" id="s3-bind-dig-x"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.4.3. ホスト名の検索</h4></div></div></div><div class="para">
+ 特定の IP アドレスに対するホスト名を検索するには、以下の形式でコマンドを使用します:
+ </div><pre class="screen"><code class="command">dig</code> <code class="option">-x</code> <em class="replaceable"><code>address</code></em></pre><div class="para">
+ <a class="xref" href="s2-bind-dig.html#example-bind-dig-x">例12.18「ホスト名の検索例」</a>において、<code class="command">dig</code> ユーティリティが <code class="systemitem">192.0.32.10</code> に割り当てられたホスト名を表示するために使用されます。
+ </div><div class="example" id="example-bind-dig-x"><h6>例12.18 ホスト名の検索例</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig -x 192.0.32.10</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> -x 192.0.32.10
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29683
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6
+
+;; QUESTION SECTION:
+;10.32.0.192.in-addr.arpa. IN PTR
+
+;; ANSWER SECTION:
+10.32.0.192.in-addr.arpa. 21600 IN PTR www.example.com.
+
+;; AUTHORITY SECTION:
+32.0.192.in-addr.arpa. 21600 IN NS b.iana-servers.org.
+32.0.192.in-addr.arpa. 21600 IN NS c.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS d.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS ns.icann.org.
+32.0.192.in-addr.arpa. 21600 IN NS a.iana-servers.net.
+
+;; ADDITIONAL SECTION:
+a.iana-servers.net. 13688 IN A 192.0.34.43
+b.iana-servers.org. 5844 IN A 193.0.0.236
+b.iana-servers.org. 5844 IN AAAA 2001:610:240:2::c100:ec
+c.iana-servers.net. 12173 IN A 139.91.1.10
+c.iana-servers.net. 12173 IN AAAA 2001:648:2c30::1:10
+ns.icann.org. 12884 IN A 192.0.34.126
+
+;; Query time: 156 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:25:15 2010
+;; MSG SIZE rcvd: 310</pre></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc.html"><strong>戻る</strong>12.2.3. rndc ユーティリティの使用法</a></li><li class="up"><a accesskey="u" href="#"><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-bind-features.html"><strong>次へ</strong>12.2.5. BIND の高度な機能</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-features.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-features.html
new file mode 100644
index 0000000..6f01fd5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-features.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>12.2.5. BIND の高度な機能</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-BIND.html" title="12.2. BIND" /><link rel="prev" href="s2-bind-dig.html" title="12.2.4. dig ユーティリティの使用" /><link rel="next" href="s2-bind-mistakes.html" title="12.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-bind-dig.html"><strong>戻る</strong></a></li><li class="next"><a accesske
y="n" href="s2-bind-mistakes.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-bind-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.5. BIND の高度な機能</h3></div></div></div><div class="para">
+ Most BIND implementations only use the <code class="systemitem">named</code> service to provide name resolution services or to act as an authority for a particular domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient DNS service.
+ </div><div class="important"><div class="admonition_header"><h2>機能がサポートされていることを確認します</h2></div><div class="admonition"><div class="para">
+ DNSSEC, TSIG, た IXFR のような高度な機能を使用しようとする前に、とくに古いバージョンの BIND や BIND 以外のサーバーを使用するときに、その機能がネットワーク環境にあるすべてのネームサーバーにおいてサポートされていることを確認してください。
+ </div></div></div><div class="para">
+ All of the features mentioned are discussed in greater detail in the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="s2-bind-additional-resources.html#s3-bind-installed-docs">「インストールされているドキュメント」</a>.
+ </div><div class="section" id="s3-bind-features-views"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.1. 複数ビュー</h4></div></div></div><a id="idm20069056" class="indexterm"></a><div class="para">
+ Optionally, different information can be presented to a client depending on the network a request originates from. This is primarily used to deny sensitive DNS entries from clients outside of the local network, while allowing queries from clients inside the local network.
+ </div><div class="para">
+ To configure multiple views, add the <code class="command">view</code> statement to the <code class="filename">/etc/named.conf</code> configuration file. Use the <code class="option">match-clients</code> option to match IP addresses or entire networks and give them special options and zone data.
+ </div></div><div class="section" id="s3-bind-features-ixfr"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.2. Incremental Zone Transfers (IXFR)</h4></div></div></div><a id="idm53247776" class="indexterm"></a><div class="para">
+ <em class="firstterm">Incremental Zone Transfers</em> (<em class="firstterm">IXFR</em>) allow a secondary nameserver to only download the updated portions of a zone modified on a primary nameserver. Compared to the standard transfer process, this makes the notification and update process much more efficient.
+ </div><a id="idm21414256" class="indexterm"></a><div class="para">
+ Note that IXFR is only available when using dynamic updating to make changes to master zone records. If manually editing zone files to make changes, <em class="firstterm">Automatic Zone Transfer</em> (<em class="firstterm">AXFR</em>) is used.
+ </div></div><div class="section" id="s3-bind-features-tsig"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.3. Transaction SIGnatures (TSIG)</h4></div></div></div><a id="idm37329408" class="indexterm"></a><div class="para">
+ <em class="firstterm">Transaction SIGnatures</em> (TSIG) ensure that a shared secret key exists on both primary and secondary nameserver before allowing a transfer. This strengthens the standard IP address-based method of transfer authorization, since attackers would not only need to have access to the IP address to transfer the zone, but they would also need to know the secret key.
+ </div><div class="para">
+ Since version 9, BIND also supports <em class="firstterm">TKEY</em>, which is another shared secret key method of authorizing zone transfers.
+ </div><div class="important"><div class="admonition_header"><h2>Secure the transfer</h2></div><div class="admonition"><div class="para">
+ When communicating over an insecure network, do not rely on IP address-based authentication only.
+ </div></div></div></div><div class="section" id="s3-bind-features-dnssec"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.4. DNS Security Extensions (DNSSEC)</h4></div></div></div><a id="idm59050000" class="indexterm"></a><div class="para">
+ <em class="firstterm">Domain Name System Security Extensions</em> (<em class="firstterm">DNSSEC</em>) provide origin authentication of DNS data, authenticated denial of existence, and data integrity. When a particular domain is marked as secure, the <code class="literal">SERFVAIL</code> response is returned for each resource record that fails the validation.
+ </div><a id="idm66705328" class="indexterm"></a><div class="para">
+ Note that to debug a DNSSEC-signed domain or a DNSSEC-aware resolver, you can use the <code class="command">dig</code> utility as described in <a class="xref" href="s2-bind-dig.html">「dig ユーティリティの使用」</a>. Useful options are <code class="option">+dnssec</code> (requests DNSSEC-related resource records by setting the DNSSEC OK bit), <code class="option">+cd</code> (tells recursive nameserver not to validate the response), and <code class="option">+bufsize=512</code> (changes the packet size to 512B to get through some firewalls).
+ </div></div><div class="section" id="s3-bind-features-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.5. インターネットプロトコル・バージョン 6 (IPv6: Internet Protocol version 6)</h4></div></div></div><a id="idm55158224" class="indexterm"></a><div class="para">
+ <em class="firstterm">Internet Protocol version 6</em> (<em class="firstterm">IPv6</em>) is supported through the use of <code class="option">AAAA</code> resource records, and the <code class="option">listen-on-v6</code> directive as described in <a class="xref" href="s1-BIND.html#table-bind-namedconf-common-options">表12.3「一般的に使用されるオプション」</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-dig.html"><strong>戻る</strong>12.2.4. dig ユーティリティの使用</a></li><li class="up"><a accesskey="u" href="#"><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-bind-mistakes.html"><strong>次へ</strong>12.2.6. よくある間違いを避けるために</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-mistakes.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-mistakes.html
new file mode 100644
index 0000000..1681403
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-mistakes.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>12.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-BIND.html" title="12.2. BIND" /><link rel="prev" href="s2-bind-features.html" title="12.2.5. BIND の高度な機能" /><link rel="next" href="s2-bind-additional-resources.html" title="12.2.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="s2-bind-features.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" h
ref="s2-bind-additional-resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-bind-mistakes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.6. よくある間違いを避けるために</h3></div></div></div><a id="idm49851328" class="indexterm"></a><div class="para">
+ The following is a list of advices how to avoid common mistakes users make when configuring a nameserver:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Use semicolons and curly brackets correctly</span></dt><dd><div class="para">
+ An omitted semicolon or unmatched curly bracket in the <code class="filename">/etc/named.conf</code> file can prevent the <code class="systemitem">named</code> service from starting.
+ </div></dd><dt class="varlistentry"><span class="term">Use period (that is, the <code class="literal">.</code> character) correctly</span></dt><dd><div class="para">
+ In zone files, a period at the end of a domain name denotes a fully qualified domain name. If omitted, the <code class="systemitem">named</code> service will append the name of the zone or the value of <code class="option">$ORIGIN</code> to complete it.
+ </div></dd><dt class="varlistentry"><span class="term">Increment the serial number when editing a zone file</span></dt><dd><div class="para">
+ If the serial number is not incremented, the primary nameserver will have the correct, new information, but the secondary nameservers will never be notified of the change, and will not attempt to refresh their data of that zone.
+ </div></dd><dt class="varlistentry"><span class="term">ファイアウォールを設定します</span></dt><dd><div class="para">
+ ファイアウォールが <code class="systemitem">named</code> サービスから他のネームサーバーへの接続をブロックするならば、推奨される最善策はできる限りファイアウォールの設定を変更することです。
+ </div><div class="warning" id="warning-Warning-Avoid_Using_Fixed_UDP_Source_Ports"><div class="admonition_header"><h2>固定 UDP ポートの使用を避けます</h2></div><div class="admonition"><div class="para">
+ DNS セキュリティに関する最近の研究によると、DNS の問い合わせに固定 UDP ポートを使用することは、潜在的なセキュリティ脆弱性となります。これは、攻撃者がより簡単にキャッシュポイズニングを引き起こせます。これを防ぐには、ファイアウォールがランダム UDP ソースポートから問い合わせをできるように設定します。
+ </div></div></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features.html"><strong>戻る</strong>12.2.5. BIND の高度な機能</a></li><li class="up"><a accesskey="u" href="#"><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-bind-additional-resources.html"><strong>次へ</strong>12.2.7. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-rndc.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-rndc.html
new file mode 100644
index 0000000..4cded7f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-rndc.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>12.2.3. rndc ユーティリティの使用法</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-BIND.html" title="12.2. BIND" /><link rel="prev" href="s2-bind-zone.html" title="12.2.2. ゾーンファイルの編集" /><link rel="next" href="s2-bind-dig.html" title="12.2.4. dig ユーティリティの使用" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-bind-zone.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-
bind-dig.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-bind-rndc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.3. rndc ユーティリティの使用法</h3></div></div></div><a id="idm55252800" class="indexterm"></a><div class="para">
+ <code class="command">rndc</code> ユーティリティは、<code class="systemitem">named</code> サービスをローカルおよびリモートマシンから管理できるコマンドラインツールです。以下のように使用します:
+ </div><pre class="screen"><code class="command">rndc</code> [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command-option</code></em>]</pre><div class="section" id="s3-bind-rndc-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.1. ユーティリティの設定法</h4></div></div></div><div class="para">
+ To prevent unauthorized access to the service, <code class="systemitem">named</code> must be configured to listen on the selected port (that is, <code class="literal">953</code> by default), and an identical key must be used by both the service and the <code class="command">rndc</code> utility.
+ </div><div class="table" id="table-bind-rndc-configuration-files"><h6>表12.7 関連ファイル</h6><div class="table-contents"><table summary="関連ファイル" border="1"><colgroup><col width="38%" class="path" /><col width="63%" class="description" /></colgroup><thead><tr><th class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <a id="idm73466144" class="indexterm"></a>
+ <code class="filename">/etc/named.conf</code>
+ </td><td class="">
+ <code class="systemitem">named</code> サービスのデフォルトの設定ファイルです。
+ </td></tr><tr><td class="">
+ <a id="idm68984000" class="indexterm"></a>
+ <code class="filename">/etc/rndc.conf</code>
+ </td><td class="">
+ <code class="command">rndc</code> ユーティリティのデフォルトの設定ファイルです。
+ </td></tr><tr><td class="">
+ <a id="idm45297520" class="indexterm"></a>
+ <code class="filename">/etc/rndc.key</code>
+ </td><td class="">
+ キーのデフォルトの場所です。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">rndc</code> configuration is located in <code class="filename">/etc/rndc.conf</code>. If the file does not exist, the utility will use the key located in <code class="filename">/etc/rndc.key</code>, which was generated automatically during the installation process using the <code class="command">rndc-confgen -a</code> command.
+ </div><div class="para">
+ The <code class="systemitem">named</code> service is configured using the <code class="option">controls</code> statement in the <code class="filename">/etc/named.conf</code> configuration file as described in <a class="xref" href="s1-BIND.html#s3-bind-namedconf-state-other">「他のステートメント形式」</a>. Unless this statement is present, only the connections from the loopback address (that is, <code class="systemitem">127.0.0.1</code>) will be allowed, and the key located in <code class="filename">/etc/rndc.key</code> will be used.
+ </div><div class="para">
+ For more information on this topic, refer to manual pages and the <em class="citetitle">BIND 9 Administrator Reference Manual</em> listed in <a class="xref" href="s2-bind-additional-resources.html">「その他のリソース」</a>.
+ </div><div class="important"><div class="admonition_header"><h2>正しいパーミッションを設定します</h2></div><div class="admonition"><div class="para">
+ 権限のないユーザーがサービスに制御コマンドを送るのを防ぐには、確実に root のみが <code class="filename">/etc/rndc.key</code> ファイルを読み込めるようにします。
+ </div><pre class="screen">~]# <code class="command">chmod o-rwx /etc/rndc.key</code></pre></div></div></div><div class="section" id="s3-bind-rndc-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.2. サービスの状態の確認法</h4></div></div></div><div class="para">
+ <code class="systemitem">named</code> サービスの現在の状態を確認するには、以下のコマンドを使用します:
+ </div><pre class="screen">~]# <code class="command">rndc status</code>
+version: 9.7.0-P2-RedHat-9.7.0-5.P2.el6
+CPUs found: 1
+worker threads: 1
+number of zones: 16
+debug level: 0
+xfers running: 0
+xfers deferred: 0
+soa queries in progress: 0
+query logging is OFF
+recursive clients: 0/0/1000
+tcp clients: 0/100
+server is up and running</pre></div><div class="section" id="s3-bind-rndc-reload"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.3. 設定およびゾーン情報の再読み込み</h4></div></div></div><div class="para">
+ To reload both the configuration file and zones, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">rndc reload</code>
+server reload successful</pre><div class="para">
+ This will reload the zones while keeping all previously cached responses, so that you can make changes to the zone files without losing all stored name resolutions.
+ </div><div class="para">
+ To reload a single zone, specify its name after the <code class="command">reload</code> command, for example:
+ </div><pre class="screen">~]# <code class="command">rndc reload localhost</code>
+zone reload up-to-date</pre><div class="para">
+ 最後に、設定ファイルを読み込み、新しく追加されたゾーンのみを追加するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">rndc reconfig</code></pre><div class="note"><div class="admonition_header"><h2>ダイナミック DNS を用いたゾーンの編集</h2></div><div class="admonition"><div class="para">
+ ダイナミック DNS (DDNS: Dynamic DNS) を使用するゾーンを手動で編集したければ、まず <code class="command">freeze</code> コマンドを必ず実行してください:
+ </div><pre class="screen">~]# <code class="command">rndc freeze localhost</code></pre><div class="para">
+ 完了すると、再び DDNS を許可するために <code class="command">thaw</code> コマンドを実行して、ゾーンを再読み込みします:
+ </div><pre class="screen">~]# <code class="command">rndc thaw localhost</code>
+The zone reload and thaw was successful.</pre></div></div></div><div class="section" id="s3-bind-rndc-sign"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.4. ゾーンキーの更新</h4></div></div></div><div class="para">
+ DNSSEC キーを更新して、ゾーンを署名するには、<code class="command">sign</code> コマンドを使用します。たとえば:
+ </div><pre class="screen">~]# <code class="command">rndc sign localhost</code></pre><div class="para">
+ 上のコマンドを用いてゾーンを署名するには、<code class="option">auto-dnssec</code> オプションが zone ステートメントにおいて <code class="literal">maintain</code> に設定されていなければいけないことに注意してください。たとえば:
+ </div><pre class="programlisting">zone "localhost" IN {
+ type master;
+ file "named.localhost";
+ allow-update { none; };
+ auto-dnssec maintain;
+};</pre></div><div class="section" id="s3-bind-rndc-validation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.5. DNSSEC 検証の有効化</h4></div></div></div><div class="para">
+ DNSSEC 検証を有効にするには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">rndc validation on</code></pre><div class="para">
+ 同様に、このオプションを無効にするには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">rndc validation off</code></pre><div class="para">
+ <code class="filename">/etc/named.conf</code> においてこのオプションを設定する方法については<code class="option">options</code> statement described in <a class="xref" href="s1-BIND.html#s3-bind-namedconf-state">「一般的なステートメントのタイプ」</a>を参照してください。
+ </div></div><div class="section" id="s3-bind-rndc-querylog"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.3.6. クエリーロギングの有効化</h4></div></div></div><div class="para">
+ クエリーロギングを有効（または現在有効な場合に無効）にするには、以下のコマンドを実行します:
+ </div><pre class="screen">~]# <code class="command">rndc querylog</code></pre><div class="para">
+ 現在の設定を確認するには、<a class="xref" href="s2-bind-rndc.html#s3-bind-rndc-status">「サービスの状態の確認法」</a> で説明されているように <code class="command">status</code> コマンドを使用します。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-zone.html"><strong>戻る</strong>12.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-bind-dig.html"><strong>次へ</strong>12.2.4. dig ユーティリティの使用</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-zone.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-zone.html
new file mode 100644
index 0000000..198539e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-bind-zone.html
@@ -0,0 +1,264 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-BIND.html" title="12.2. BIND" /><link rel="prev" href="s1-BIND.html" title="12.2. BIND" /><link rel="next" href="s2-bind-rndc.html" title="12.2.3. rndc ユーティリティの使用法" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-BIND.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-rndc.html"><strong>次へ</s
trong></a></li></ul><div class="section" id="s2-bind-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.2. ゾーンファイルの編集</h3></div></div></div><a id="idm45101760" class="indexterm"></a><a id="idm45104480" class="indexterm"></a><a id="idm45356400" class="indexterm"></a><a id="idm45359120" class="indexterm"></a><div class="para">
+ As outlined in <a class="xref" href="ch-DNS_Servers.html#s2-dns-introduction-zones">「ネームサーバーゾーン」</a>, zone files contain information about a namespace. They are stored in the <code class="systemitem">named</code> working directory located in <code class="filename">/var/named/</code> by default, and each zone file is named according to the <code class="option">file</code> option in the <code class="option">zone</code> statement, usually in a way that relates to the domain in question and identifies the file as containing zone data, such as <code class="filename">example.com.zone</code>.
+ </div><div class="table" id="table-bind-zone-files"><h6>表12.5 The named service zone files</h6><div class="table-contents"><table summary="The named service zone files" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ パス
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="filename">/var/named/</code>
+ </td><td class="">
+ <code class="systemitem">named</code> サービスの作業ディレクトリです。ネームサーバーはこのディレクトリに書き込みが許可<span class="emphasis"><em>されません</em></span>。
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/slaves/</code>
+ </td><td class="">
+ セカンダリ・ゾーン向けのディレクトリです。このディレクトリは <code class="systemitem">named</code> サービスにより書き込み可能です。
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/dynamic/</code>
+ </td><td class="">
+ The directory for other files, such as dynamic DNS (DDNS) zones or managed DNSSEC keys. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/data/</code>
+ </td><td class="">
+ The directory for various statistics and debugging files. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ A zone file consists of directives and resource records. Directives tell the nameserver to perform tasks or apply special settings to the zone, resource records define the parameters of the zone and assign identities to individual hosts. While the directives are optional, the resource records are required in order to provide name service to a zone.
+ </div><div class="para">
+ すべてのディレクティブとリソースレコードは、個々の行に記載する必要があります。
+ </div><div class="section" id="s3-bind-zone-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.2.1. 一般的なディレクティブ</h4></div></div></div><div class="para">
+ Directives begin with the dollar sign character (that is, <code class="literal">$</code>) followed by the name of the directive, and usually appear at the top of the file. The following directives are commonly used in zone files:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm40893536" class="indexterm"></a>
+ <code class="command">$INCLUDE</code></span></dt><dd><div class="para">
+ The <code class="command">$INCLUDE</code> directive allows you to include another file at the place where it appears, so that other zone settings can be stored in a separate zone file.
+ </div><div class="example" id="example-bind-zone-directive-include"><h6>例12.6 $INCLUDE ディレクティブの使用法</h6><div class="example-contents"><pre class="programlisting">$INCLUDE /var/named/penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm40901040" class="indexterm"></a>
+ <code class="command">$ORIGIN</code></span></dt><dd><div class="para">
+ The <code class="command">$ORIGIN</code> directive allows you to append the domain name to unqualified records, such as those with the hostname only. Note that the use of this directive is not necessary if the zone is specified in <code class="filename">/etc/named.conf</code>, since the zone name is used by default.
+ </div><div class="para">
+ In <a class="xref" href="s2-bind-zone.html#example-bind-zone-directive-origin">例12.7「$ORIGIN ディレクティブの使用法」</a>, any names used in resource records that do not end in a trailing period (that is, the <code class="literal">.</code> character) are appended with <code class="literal">example.com</code>.
+ </div><div class="example" id="example-bind-zone-directive-origin"><h6>例12.7 $ORIGIN ディレクティブの使用法</h6><div class="example-contents"><pre class="programlisting">$ORIGIN example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm51884768" class="indexterm"></a>
+ <code class="command">$TTL</code></span></dt><dd><div class="para">
+ The <code class="command">$TTL</code> directive allows you to set the default <em class="firstterm">Time to Live</em> (TTL) value for the zone, that is, how long is a zone record valid. Each resource record can contain its own TTL value, which overrides this directive.
+ </div><div class="para">
+ この値を増加させると、リモートネームサーバーは、このゾーンの情報をより長時間キャッシュします。こうすると、このゾーンについて行われるクエリの数は減りますが、リソースレコード変更を伝えるのに要する時間は長くなります。
+ </div><div class="example" id="example-bind-zone-directive-ttl"><h6>例12.8 $TTL ディレクティブの使用</h6><div class="example-contents"><pre class="programlisting">$TTL 1D</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s4-bind-zone-rr"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.2.2. Common Resource Records</h4></div></div></div><div class="para">
+ The following resource records are commonly used in zone files:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm46709856" class="indexterm"></a>
+ <code class="command">A</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Address</em> record specifies an IP address to be assigned to a name. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>hostname</code></em> IN A <em class="replaceable"><code>IP-address</code></em></pre><div class="para">
+ If the <em class="replaceable"><code>hostname</code></em> value is omitted, the record will point to the last specified <em class="replaceable"><code>hostname</code></em>.
+ </div><div class="para">
+ In <a class="xref" href="s2-bind-zone.html#example-bind-zone-rr-a">例12.9「A リソースレコードの使用法」</a>, the requests for <code class="systemitem">server1.example.com</code> are pointed to <code class="literal">10.0.1.3</code> or <code class="literal">10.0.1.5</code>.
+ </div><div class="example" id="example-bind-zone-rr-a"><h6>例12.9 A リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">server1 IN A 10.0.1.3
+ IN A 10.0.1.5</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm44499424" class="indexterm"></a>
+ <code class="command">CNAME</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Canonical Name</em> record maps one name to another. Because of this, this type of record is sometimes referred to as an <em class="firstterm">alias record</em>. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>alias-name</code></em> IN CNAME <em class="replaceable"><code>real-name</code></em></pre><div class="para">
+ <code class="command">CNAME</code> records are most commonly used to point to services that use a common naming scheme, such as <code class="literal">www</code> for Web servers. However, there are multiple restrictions for their usage:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ CNAME records should not point to other CNAME records. This is mainly to avoid possible infinite loops.
+ </div></li><li class="listitem"><div class="para">
+ CNAME records should not contain other resource record types (such as A, NS, MX, etc.). The only exception are DNSSEC related records (that is, RRSIG, NSEC, etc.) when the zone is signed.
+ </div></li><li class="listitem"><div class="para">
+ Other resource record that point to the fully qualified domain name (FQDN) of a host (that is, NS, MX, PTR) should not point to a CNAME record.
+ </div></li></ul></div><div class="para">
+ In <a class="xref" href="s2-bind-zone.html#example-bind-zone-rr-cname">例12.10「CNAME リソースレコードの使用法」</a>, the <code class="command">A</code> record binds a hostname to an IP address, while the <code class="command">CNAME</code> record points the commonly used <code class="literal">www</code> hostname to it.
+ </div><div class="example" id="example-bind-zone-rr-cname"><h6>例12.10 CNAME リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">server1 IN A 10.0.1.5
+www IN CNAME server1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm17780816" class="indexterm"></a>
+ <code class="command">MX</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Mail Exchange</em> record specifies where the mail sent to a particular namespace controlled by this zone should go. It takes the following form:
+ </div><pre class="programlisting">IN MX <em class="replaceable"><code>preference-value</code></em> <em class="replaceable"><code>email-server-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>email-server-name</code></em> is a fully qualified domain name (FQDN). The <em class="replaceable"><code>preference-value</code></em> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <code class="command">MX</code> resource record with the lowest <em class="replaceable"><code>preference-value</code></em> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
+ </div><div class="para">
+ In <a class="xref" href="s2-bind-zone.html#example-bind-zone-rr-mx">例12.11「MX リソースレコードの使用法」</a>, the first <code class="systemitem">mail.example.com</code> email server is preferred to the <code class="systemitem">mail2.example.com</code> email server when receiving email destined for the <code class="systemitem">example.com</code> domain.
+ </div><div class="example" id="example-bind-zone-rr-mx"><h6>例12.11 MX リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">example.com. IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm42518864" class="indexterm"></a>
+ <code class="command">NS</code></span></dt><dd><div class="para">
+ <em class="firstterm">ネームサーバー</em>レコードは、他のゾーンに対する権威ネームサーバーを知らせます。以下の形式をとります:
+ </div><pre class="programlisting">IN NS <em class="replaceable"><code>nameserver-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>nameserver-name</code></em> should be a fully qualified domain name (FQDN). Note that when two nameservers are listed as authoritative for the domain, it is not important whether these nameservers are secondary nameservers, or if one of them is a primary server. They are both still considered authoritative.
+ </div><div class="example" id="example-bind-zone-rr-ns"><h6>例12.12 NS リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">IN NS dns1.example.com.
+IN NS dns2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm42527760" class="indexterm"></a>
+ <code class="command">PTR</code></span></dt><dd><div class="para">
+ <em class="firstterm">ポインター</em> レコードは、名前空間の他の場所を示します。以下の形式をとります:
+ </div><pre class="programlisting"><em class="replaceable"><code>last-IP-digit</code></em> IN PTR <em class="replaceable"><code>FQDN-of-system</code></em></pre><div class="para">
+ The <em class="replaceable"><code>last-IP-digit</code></em> directive is the last number in an IP address, and the <em class="replaceable"><code>FQDN-of-system</code></em> is a fully qualified domain name (FQDN).
+ </div><div class="para">
+ <code class="command">PTR</code> records are primarily used for reverse name resolution, as they point IP addresses back to a particular name. Refer to <a class="xref" href="s2-bind-zone.html#s3-bind-configuration-zone-reverse">「逆引き名前解決ゾーンファイル」</a> for more examples of <code class="command">PTR</code> records in use.
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm66677936" class="indexterm"></a>
+ <code class="command">SOA</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Start of Authority</em> record announces important authoritative information about a namespace to the nameserver. Located after the directives, it is the first resource record in a zone file. It takes the following form:
+ </div><pre class="programlisting">@ IN SOA <em class="replaceable"><code>primary-name-server</code></em> <em class="replaceable"><code>hostmaster-email</code></em> (
+ <em class="replaceable"><code>serial-number</code></em>
+ <em class="replaceable"><code>time-to-refresh</code></em>
+ <em class="replaceable"><code>time-to-retry</code></em>
+ <em class="replaceable"><code>time-to-expire</code></em>
+ <em class="replaceable"><code>minimum-TTL</code></em> )</pre><div class="para">
+ ディレクティブは以下のとおりです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="literal">@</code> symbol places the <code class="command">$ORIGIN</code> directive (or the zone's name if the <code class="command">$ORIGIN</code> directive is not set) as the namespace being defined by this <code class="command">SOA</code> resource record.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>primary-name-server</code></em> directive is the hostname of the primary nameserver that is authoritative for this domain.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>hostmaster-email</code></em> directive is the email of the person to contact about the namespace.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>serial-number</code></em> directive is a numerical value incremented every time the zone file is altered to indicate it is time for the <code class="systemitem">named</code> service to reload the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-refresh</code></em> directive is the numerical value secondary nameservers use to determine how long to wait before asking the primary nameserver if any changes have been made to the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-retry</code></em> directive is a numerical value used by secondary nameservers to determine the length of time to wait before issuing a refresh request in the event that the primary nameserver is not answering. If the primary server has not replied to a refresh request before the amount of time specified in the <em class="replaceable"><code>time-to-expire</code></em> directive elapses, the secondary servers stop responding as an authority for requests concerning that namespace.
+ </div></li><li class="listitem"><div class="para">
+ In BIND 4 and 8, the <em class="replaceable"><code>minimum-TTL</code></em> directive is the amount of time other nameservers cache the zone's information. In BIND 9, it defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (that is, <code class="option">3H</code>).
+ </div></li></ul></div><div class="para">
+ When configuring BIND, all times are specified in seconds. However, it is possible to use abbreviations when specifying units of time other than seconds, such as minutes (<code class="literal">M</code>), hours (<code class="literal">H</code>), days (<code class="literal">D</code>), and weeks (<code class="literal">W</code>). <a class="xref" href="s2-bind-zone.html#tb-bind-seconds">表12.6「他の時間単位と比較した秒数」</a> shows an amount of time in seconds and the equivalent time in another format.
+ </div><div class="table" id="tb-bind-seconds"><h6>表12.6 他の時間単位と比較した秒数</h6><div class="table-contents"><table summary="他の時間単位と比較した秒数" border="1"><colgroup><col width="50%" class="seconds" /><col width="50%" class="other" /></colgroup><thead><tr><th class="">
+ 秒
+ </th><th class="">
+ 他の時間単位
+ </th></tr></thead><tbody><tr><td class="">
+ 60
+ </td><td class="">
+ <code class="literal">1M</code>
+ </td></tr><tr><td class="">
+ 1800
+ </td><td class="">
+ <code class="literal">30M</code>
+ </td></tr><tr><td class="">
+ 3600
+ </td><td class="">
+ <code class="literal">1H</code>
+ </td></tr><tr><td class="">
+ 10800
+ </td><td class="">
+ <code class="literal">3H</code>
+ </td></tr><tr><td class="">
+ 21600
+ </td><td class="">
+ <code class="literal">6H</code>
+ </td></tr><tr><td class="">
+ 43200
+ </td><td class="">
+ <code class="literal">12H</code>
+ </td></tr><tr><td class="">
+ 86400
+ </td><td class="">
+ <code class="literal">1D</code>
+ </td></tr><tr><td class="">
+ 259200
+ </td><td class="">
+ <code class="literal">3D</code>
+ </td></tr><tr><td class="">
+ 604800
+ </td><td class="">
+ <code class="literal">1W</code>
+ </td></tr><tr><td class="">
+ 31536000
+ </td><td class="">
+ <code class="literal">365D</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-bind-zone-rr-soa"><h6>例12.13 SOA リソースレコードの使用法</h6><div class="example-contents"><pre class="programlisting">@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s3-bind-zone-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.2.3. コメントタグ</h4></div></div></div><a id="idm51467392" class="indexterm"></a><div class="para">
+ Additionally to resource records and directives, a zone file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to the user. Any text after the semicolon character (that is, <code class="literal">;</code>) to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting"> 604800 ; 1 週間後に期限切れ</pre></div><div class="section" id="s3-bind-zone-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.2.4. 使用例</h4></div></div></div><div class="para">
+ 以下の例はゾーンファイルの基本的な使用法を示しています。
+ </div><div class="section" id="s4-bind-zone-examples-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.2.2.4.1. 簡単なゾーンファイル</h5></div></div></div><a id="idm61840960" class="indexterm"></a><div class="para">
+ <a class="xref" href="s2-bind-zone.html#example-bind-zone-examples-basic">例12.14「簡単なゾーンファイル」</a>は標準的なディレクティブと <code class="command">SOA</code> 値の使用法を説明します。
+ </div><div class="example" id="example-bind-zone-examples-basic"><h6>例12.14 簡単なゾーンファイル</h6><div class="example-contents"><pre class="programlisting">$ORIGIN example.com.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+;
+ IN NS dns1.example.com.
+ IN NS dns2.example.com.
+dns1 IN A 10.0.1.1
+ IN AAAA aaaa:bbbb::1
+dns2 IN A 10.0.1.2
+ IN AAAA aaaa:bbbb::2
+;
+;
+@ IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.
+mail IN A 10.0.1.5
+ IN AAAA aaaa:bbbb::5
+mail2 IN A 10.0.1.6
+ IN AAAA aaaa:bbbb::6
+;
+;
+; This sample zone file illustrates sharing the same IP addresses
+; for multiple services:
+;
+services IN A 10.0.1.10
+ IN AAAA aaaa:bbbb::10
+ IN A 10.0.1.11
+ IN AAAA aaaa:bbbb::11
+
+ftp IN CNAME services.example.com.
+www IN CNAME services.example.com.
+;
+;</pre></div></div><br class="example-break" /><div class="para">
+ In this example, the authoritative nameservers are set as <code class="systemitem">dns1.example.com</code> and <code class="systemitem">dns2.example.com</code>, and are tied to the <code class="systemitem">10.0.1.1</code> and <code class="systemitem">10.0.1.2</code> IP addresses respectively using the <code class="command">A</code> record.
+ </div><div class="para">
+ The email servers configured with the <code class="command">MX</code> records point to <code class="systemitem">mail</code> and <code class="systemitem">mail2</code> via <code class="command">A</code> records. Since these names do not end in a trailing period (that is, the <code class="literal">.</code> character), the <code class="command">$ORIGIN</code> domain is placed after them, expanding them to <code class="systemitem">mail.example.com</code> and <code class="systemitem">mail2.example.com</code>.
+ </div><div class="para">
+ Services available at the standard names, such as <code class="systemitem">www.example.com</code> (<acronym class="acronym">WWW</acronym>), are pointed at the appropriate servers using the <code class="command">CNAME</code> record.
+ </div><div class="para">
+ このゾーンファイルは、<code class="filename">/etc/named.conf</code> ファイルにおいて、以下のような <code class="option">zone</code> ステートメントを用いたサービスの中に呼び出されます:
+ </div><pre class="programlisting">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-update { none; };
+};</pre></div><div class="section" id="s3-bind-configuration-zone-reverse"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.2.2.4.2. 逆引き名前解決ゾーンファイル</h5></div></div></div><a id="idm45099232" class="indexterm"></a><div class="para">
+ 逆引き名前解決ゾーンファイルは、特定の名前空間にある IP アドレスを完全修飾ドメイン名（FQDN）に変換するために使用されます。これは、<a class="xref" href="s2-bind-zone.html#example-bind-zone-examples-reverse">例12.15「逆引き名前解決ゾーンファイル」</a>にあるよように、<code class="command">PTR</code> リソースレコードが IP アドレスを完全修飾ドメイン名にリンクするために使用されることを除いて、標準的なゾーンファイルによく似ています。
+ </div><div class="example" id="example-bind-zone-examples-reverse"><h6>例12.15 逆引き名前解決ゾーンファイル</h6><div class="example-contents"><pre class="programlisting">$ORIGIN 1.0.10.in-addr.arpa.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+@ IN NS dns1.example.com.
+;
+1 IN PTR dns1.example.com.
+2 IN PTR dns2.example.com.
+;
+5 IN PTR server1.example.com.
+6 IN PTR server2.example.com.
+;
+3 IN PTR ftp.example.com.
+4 IN PTR ftp.example.com.</pre></div></div><br class="example-break" /><div class="para">
+ この例において、IP アドレス <code class="systemitem">10.0.1.1</code> から <code class="systemitem">10.0.1.6</code> は対応する完全修飾ドメイン名に対応づけられます。
+ </div><div class="para">
+ このゾーンファイルは、<code class="filename">/etc/named.conf</code> ファイルにおいて、以下のような <code class="option">zone</code> ステートメントを用いたサービスの中に呼び出されます:
+ </div><pre class="programlisting">zone "1.0.10.in-addr.arpa" IN {
+ type master;
+ file "example.com.rr.zone";
+ allow-update { none; };
+};</pre><div class="para">
+ There is very little difference between this example and a standard <code class="command">zone</code> statement, except for the zone name. Note that a reverse name resolution zone requires the first three blocks of the IP address reversed followed by <code class="command">.in-addr.arpa</code>. This allows the single block of IP numbers used in the reverse name resolution zone file to be associated with the zone.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-BIND.html"><strong>戻る</strong>12.2. BIND</a></li><li class="up"><a accesskey="u" href="#"><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-bind-rndc.html"><strong>次へ</strong>12.2.3. rndc ユーティリティの使用法</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-mta-fetchmail.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-mta-fetchmail.html
new file mode 100644
index 0000000..7310595
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-email-mta.html" title="14.3. Mail Transport Agent" /><link rel="prev" href="s2-email-mta-sendmail.html" title="14.3.2. Sendmail" /><link rel="next" href="s2-email-switchmail.html" title="14.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">14.3.3. Fetchmail</h3></div></div></div><a id="idm64193216" class="indexterm"></a><a id="idm60942528" 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">yum install fetchmail</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</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">14.3.3.1. Fetchmail 設定オプション</h4></div></div></div><a id="idm42784672" class="indexterm"></a><a id="idm42782928" 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 hostname, 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 username 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 hostname 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">
+ 以下は <code class="filename">.fetchmailrc</code> ファイルのサンプル例です。:
+ </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">14.3.3.2. グローバルオプション</h4></div></div></div><a id="idm62262000" class="indexterm"></a><a id="idm62259776" 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">14.3.3.3. サーバー オプション</h4></div></div></div><a id="idm46433696" class="indexterm"></a><a id="idm46431504" 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 assumed.
+ </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">14.3.3.4. ユーザー オプション</h4></div></div></div><a id="idm41377904" class="indexterm"></a><a id="idm41375680" 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">14.3.3.5. Fetchmail コマンド オプション</h4></div></div></div><a id="idm44708240" 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">14.3.3.6. 情報オプション、あるいはデバッグ オプション</h4></div></div></div><a id="idm42368880" 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">14.3.3.7. 特別なオプション</h4></div></div></div><a id="idm41345520" 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>14.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>14.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/17/html/System_Administrators_Guide/s2-email-mta-sendmail.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-mta-sendmail.html
new file mode 100644
index 0000000..ea38ba7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-mta-sendmail.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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-email-mta.html" title="14.3. Mail Transport Agent" /><link rel="prev" href="s1-email-mta.html" title="14.3. Mail Transport Agent" /><link rel="next" href="s2-email-mta-fetchmail.html" title="14.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">14.3.2. Sendmail</h3></div></div></div><a id="idm48112560" class="indexterm"></a><a id="idm30011888" 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. However, Sendmail is highly configurable, allowing control over almost every aspect of how email is handled, including the protocol used. Many system administrators elect to use Sendmail as their MTA due to its power and scalability.
+ </div><div class="section" id="s3-email-mta-sendmail-purpose"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">14.3.2.1. 目的と制限</h4></div></div></div><a id="idm30008064" class="indexterm"></a><a id="idm55982048" 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. Refer to 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">14.3.2.2. Sendmail のデフォルトインストール</h4></div></div></div><a id="idm59479504" 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">yum 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">yum install sendmail-cf</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</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">
+ Sendmail の実行ファイルは <code class="filename">/usr/sbin/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>, 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> (<code class="command">~]# make all -C /etc/mail/</code>) to create a new <code class="filename">/etc/mail/sendmail.cf</code> configuration file. 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 will automatically be used by <code class="command">systemctl start|restart|reload sendmail.service</code>.
+ </div></li><li class="listitem"><div class="para">
+ Alternatively you may use the <code class="command">m4</code> macro processor to create a new <code class="filename">/etc/mail/sendmail.cf</code>. The <code class="command">m4</code> macro processor is not installed by default. Before using it to create <code class="filename">/etc/mail/sendmail.cf</code>, install the <span class="package">m4</span> package as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">yum install m4</code></pre></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">
+ さまざまな Sendmail 設定ファイルが <code class="filename">/etc/mail/</code> ディレクトリにインストールされます:
+ </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 <code class="filename">/etc/mail/</code>, 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 command, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command">makemap hash /etc/mail/<em class="replaceable"><code>name</code></em> < /etc/mail/<em class="replaceable"><code>name</code></em></code></pre><div class="para">
+ where <em class="replaceable"><code>name</code></em> represents the name of the configuration file to be updated. 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.service</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="email"><a class="email" href="mailto:bob at other-example.com">bob at other-example.com</a></code>
+ , add the following line to the <code class="filename">virtusertable</code> file:
+ </div><pre class="programlisting"><code class="command">@example.com bob at other-example.com</code></pre><div class="para">
+ 変更を完了するには、<code class="filename">virtusertable.db</code> ファイルを更新しなければいけません:
+ </div><pre class="screen"><code class="command">makemap hash /etc/mail/virtusertable < /etc/mail/virtusertable</code></pre><div class="para">
+ Sendmail will create an updated <code class="filename">virtusertable.db</code> file containing the new configuration.
+ </div></div><div class="section" id="s3-email-mta-sendmail-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">14.3.2.3. 一般的な Sendmail 設定変更</h4></div></div></div><a id="idm68679632" class="indexterm"></a><a id="idm45712048" 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">
+ <code class="filename">sendmail.cf</code> ファイルを変更する前に、バックアップのコピーを作成することは良いアイディアです。
+ </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.service</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.service</code></pre></div></div><div class="para">
+ The default configuration which ships with 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">14.3.2.4. マスカレード</h4></div></div></div><a id="idm58356496" class="indexterm"></a><a id="idm58354752" 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 instance, 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 at example.com</code> instead of <code class="computeroutput">user at 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(`bigcorp.com.')dnl
+MASQUERADE_DOMAIN(`bigcorp.com.')dnl
+MASQUERADE_AS(bigcorp.com)dnl</pre><div class="para">
+ After generating a new <code class="filename">sendmail.cf</code> 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="computeroutput">bigcorp.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">14.3.2.5. スパムの停止</h4></div></div></div><a id="idm35009136" 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.service</code></pre><div class="para">
+ However, many times users are bombarded with spam from other servers throughout 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" 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 to the spammer. 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. Refer to the <code class="filename">/usr/share/sendmail-cf/README</code> 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. Refer to <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">14.3.2.6. LDAP での Sendmail の使用</h4></div></div></div><a id="idm63061936" 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. Refer to <a class="xref" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">「一般的な Sendmail 設定変更」</a> for instructions.
+ </div><div class="para">
+ <code class="systemitem">LDAP</code> の詳細は<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>14.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>14.3.3. Fetchmail</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-procmail-recipes.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-procmail-recipes.html
new file mode 100644
index 0000000..dee7e6c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-procmail-recipes.html
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-email-mda.html" title="14.4. メール配送エージェント" /><link rel="prev" href="s1-email-mda.html" title="14.4. メール配送エージェント" /><link rel="next" href="s1-email-mua.html" title="14.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">14.4.2. Procmail レシピ</h3></div></div></div><a id="idm70666352" class="indexterm"></a><div class="para">
+ New users often find the construction of recipes the most difficult part of learning to use Procmail. To some extent, this is understandable, as recipes do their message matching using <em class="firstterm">regular expressions</em>, which is a particular format used to specify qualifications for a matching string. 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, refer to <a class="xref" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-examples">「レシピの例」</a>.
+ </div><div class="para">
+ Procmail レシピは、次の形式をとります:
+ </div><pre class="programlisting">:0<em class="replaceable"><code>flags</code></em>: <em class="replaceable"><code>lockfile-name</code></em> * <em class="replaceable"><code>special-condition-character</code></em>
+ <em class="replaceable"><code>condition-1</code></em> * <em class="replaceable"><code>special-condition-character</code></em>
+ <em class="replaceable"><code>condition-2</code></em> * <em class="replaceable"><code>special-condition-character</code></em>
+ <em class="replaceable"><code>condition-N</code></em>
+ <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. Refer to <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">14.4.2.1. 配信レシピと非配信</h4></div></div></div><a id="idm47910592" class="indexterm"></a><a id="idm45205856" 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">14.4.2.2. フラグ</h4></div></div></div><a id="idm45831168" class="indexterm"></a><div class="para">
+ フラグは、いかにレシピの条件をメッセージと比較するか、あるいはレシピの条件をメッセージと比較するかどうかを決定する際に非常に重要です。次のフラグが一般に使用されます:
+ </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 the 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">
+ 追加のフラグの詳細な一覧は <code class="filename">procmailrc</code> マニュアルページを参照してください。
+ </div></div><div class="section" id="s3-email-procmail-recipes-lockfile"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">14.4.2.3. ローカルロックファイルの指定</h4></div></div></div><a id="idm35799920" 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">14.4.2.4. 特別な条件とアクション</h4></div></div></div><a id="idm22021120" class="indexterm"></a><a id="idm56440528" 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">14.4.2.5. レシピの例</h4></div></div></div><a id="idm17966432" 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 (such as <a href="http://www.iki.fi/era/procmail/links.html">http://www.iki.fi/era/procmail/links.html</a>). 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</code> man page.
+ </div><div class="para">
+ 次の簡単なサンプルが Procmail レシピの基本的な組み立てを示し、そしてより複雑な構成の基盤を提供します。
+ </div><div class="para">
+ 基本的なレシピには、次の例で示すように条件が付いていないものさえあります：
+ </div><pre class="programlisting">: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="programlisting">:0 * ^From: spammer at domain.com /dev/null</pre><div class="para">
+ With this example, any messages sent by <code class="computeroutput">spammer at 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="programlisting">:0: * ^(From|Cc|To).*tux-lug tuxlug</pre><div class="para">
+ Any messages sent from the <code class="computeroutput">tux-lug at 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">14.4.2.6. スパムフィルタ</h4></div></div></div><a id="idm54405600" class="indexterm"></a><a id="idm54403376" class="indexterm"></a><a id="idm54401632" 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">yum install spamassassin</code></pre><div class="para">
+ Yum を用いたパッケージのインストールに関する詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</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">
+ Fedora においてサービスを設定する方法の詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </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>14.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>14.5. メールユーザーエージェント</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-related-books.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-related-books.html
new file mode 100644
index 0000000..5dfa853
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-email-additional-resources.html" title="14.6. その他のリソース" /><link rel="prev" href="s2-email-useful-websites.html" title="14.6.2. 役に立つ Web サイト" /><link rel="next" href="ch-Directory_Servers.html" title="第15章 ディレクトリー サーバー" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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">14.6.3. 関連書籍</h3></div></div></div><a id="idm56824368" 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>14.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>第15章 ディレクトリー サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-switchmail.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-switchmail.html
new file mode 100644
index 0000000..d5a7f47
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-email-mta.html" title="14.3. Mail Transport Agent" /><link rel="prev" href="s2-email-mta-fetchmail.html" title="14.3.3. Fetchmail" /><link rel="next" href="s1-email-mda.html" title="14.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">14.3.4. Mail Transport Agent (MTA) の設定</h3></div></div></div><a id="idm55555344" class="indexterm"></a><a id="idm55553632" class="indexterm"></a><a id="idm55551888" class="indexterm"></a><a id="idm56196048" class="indexterm"></a><a id="idm56194336" class="indexterm"></a><a id="idm56193104" 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">/bin/mail</code> command to send email containing log messages to the <code class="systemitem">root</code> user of the local system.
+ </div><a id="idm60302448" class="indexterm"></a><a id="idm60301184" class="indexterm"></a><div class="para">
+ Fedora 17 は2つの MTA を提供します: Postfix および Sendmail。どちらもインストールされていれば、Postfix がデフォルトの MTA です。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-mta-fetchmail.html"><strong>戻る</strong>14.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>14.4. メール配送エージェント</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-types-mda.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-types-mda.html
new file mode 100644
index 0000000..f2c63e8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-email-types.html" title="14.2. 電子メールプログラム分類" /><link rel="prev" href="s1-email-types.html" title="14.2. 電子メールプログラム分類" /><link rel="next" href="s2-email-types-mua.html" title="14.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">14.2.2. メール配送エージェント (Mail Delivery Agent)</h3></div></div></div><a id="idm59945568" class="indexterm"></a><a id="idm48914592" class="indexterm"></a><a id="idm48912880" 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>14.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>14.2.3. メール ユーザー エージェント</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-types-mua.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-types-mua.html
new file mode 100644
index 0000000..d2769ae
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-email-types.html" title="14.2. 電子メールプログラム分類" /><link rel="prev" href="s2-email-types-mda.html" title="14.2.2. メール配送エージェント (Mail Delivery Agent)" /><link rel="next" href="s1-email-mta.html" title="14.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">14.2.3. メール ユーザー エージェント</h3></div></div></div><a id="idm69511360" class="indexterm"></a><a id="idm69509168" class="indexterm"></a><a id="idm31946432" 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 the very least, 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>pine</strong></span>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-types-mda.html"><strong>戻る</strong>14.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>14.3. Mail Transport Agent</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-useful-websites.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-useful-websites.html
new file mode 100644
index 0000000..80b0ac2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-email-useful-websites.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>14.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-email-additional-resources.html" title="14.6. その他のリソース" /><link rel="prev" href="s1-email-additional-resources.html" title="14.6. その他のリソース" /><link rel="next" href="s2-email-related-books.html" title="14.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">14.6.2. 役に立つ Web サイト</h3></div></div></div><a id="idm20263152" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.sendmail.org/">http://www.sendmail.org/</a> — 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/</a> — 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://fetchmail.berlios.de/">http://fetchmail.berlios.de/</a> — Fetchmail のホームページです。オンラインマニュアルや全体的な FAQ が特徴です。
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.procmail.org/">http://www.procmail.org/</a> — 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://partmaps.org/era/procmail/mini-faq.html">http://partmaps.org/era/procmail/mini-faq.html</a> — An excellent Procmail FAQ, offers troubleshooting tips, details about file locking, and the use of wildcard characters.
+ </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.org/</a> — SpamAssassin プロジェクトの公式サイトです。
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-additional-resources.html"><strong>戻る</strong>14.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>14.6.3. 関連書籍</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ftp-resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ftp-resources.html
new file mode 100644
index 0000000..7043c9f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html" title="16.2. FTP" /><link rel="prev" href="s2-ftp-vsftpd-conf.html" title="16.2.5. vsftpd 設定オプション" /><link rel="next" href="sec-Printer_Configuration.html" title="16.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">16.2.6. その他のリソース</h3></div></div></div><a id="idm24815920" 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">16.2.6.1. インストールされているドキュメント</h4></div></div></div><a id="idm61198192" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="filename">/usr/share/doc/vsftpd-<em class="replaceable"><code>version-number</code></em>/</code> directory — Replace <em class="replaceable"><code>version-number</code></em> with the installed version of the <code class="filename">vsftpd</code> package. 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">16.2.6.2. 役に立つ Web サイト</h4></div></div></div><a id="idm64463248" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/</a> — 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.com/other/ftp.html</a> — 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.org/rfc/rfc0959.txt</a> — 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>16.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>16.3. プリンタの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ftp-servers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ftp-servers.html
new file mode 100644
index 0000000..dd424d9
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html" title="16.2. FTP" /><link rel="prev" href="s1-FTP.html" title="16.2. FTP" /><link rel="next" href="s3-ftp-vsftpd-conf.html" title="16.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">16.2.2. FTP サーバー</h3></div></div></div><a id="idm70121376" class="indexterm"></a><a id="idm40203760" class="indexterm"></a><a id="idp2837408" class="indexterm"></a><a id="idm40177968" 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">
+ <span class="application"><strong>Red Hat Content Accelerator</strong></span> — A kernel-based Web server that delivers high performance Web server and <code class="systemitem">FTP</code> services. Since speed is its primary design goal, it has limited functionality and runs only as an anonymous <code class="systemitem">FTP</code> server. For more information about configuring and administering <span class="application"><strong>Red Hat Content Accelerator</strong></span>, consult the documentation available online at <a href="http://www.redhat.com/docs/manuals/tux/">http://www.redhat.com/docs/manuals/tux/</a>.
+ </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">16.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>16.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>16.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/17/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html
new file mode 100644
index 0000000..88a6a50
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html" title="16.2. FTP" /><link rel="prev" href="s2-ftp-vsftpd-start.html" title="16.2.4. vsftpd の開始と停止" /><link rel="next" href="s2-ftp-resources.html" title="16.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">16.2.5. <code class="command">vsftpd</code> 設定オプション</h3></div></div></div><a id="idm69682272" class="indexterm"></a><a id="idm48626960" 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>, refer to the Fedora 17 <em class="citetitle">Security Guide</em>.
+ </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">16.2.5.1. デーモンオプション</h4></div></div></div><a id="idm46882048" 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">16.2.5.2. ログインオプションとアクセス制御</h4></div></div></div><a id="idm66980224" class="indexterm"></a><a id="idm41433360" 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">
+ Refer to <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">
+ Refer to <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">16.2.5.3. 匿名ユーザーオプション</h4></div></div></div><a id="idm25143952" 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">16.2.5.4. ローカルユーザーオプション</h4></div></div></div><a id="idm48655808" 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">16.2.5.5. ディレクトリオプション</h4></div></div></div><a id="idm41228416" 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">16.2.5.6. ファイル転送のオプション</h4></div></div></div><a id="idm36832512" 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">16.2.5.7. ロギングのオプション</h4></div></div></div><a id="idm58049344" 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">16.2.5.8. ネットワークオプション</h4></div></div></div><a id="idm61743840" 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. Refer to <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. Refer to <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>16.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>16.2.6. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html
new file mode 100644
index 0000000..8ca38a3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html" title="16.2. FTP" /><link rel="prev" href="s3-ftp-vsftpd-conf.html" title="16.2.3. Files Installed with vsftpd" /><link rel="next" href="s2-ftp-vsftpd-conf.html" title="16.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">16.2.4. <code class="command">vsftpd</code> の開始と停止</h3></div></div></div><a id="idm60252960" class="indexterm"></a><a id="idm63161680" class="indexterm"></a><a id="idm62215520" class="indexterm"></a><a id="idm47529392" class="indexterm"></a><a id="idm18123872" 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>. Refer to <a class="xref" href="ch-Services_and_Daemons.html">8章<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">16.2.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </h4></div></div></div><a id="idm51199200" class="indexterm"></a><a id="idm57772048" 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. Additional information about network configuration scripts can be found in <a class="xref" href="ch-Network_Interfaces.html">7章<em>ネットワーク・インターフェース</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 <a class="xref" href="s1-BIND.html">「BIND」</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>16.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>16.2.5. vsftpd 設定オプション</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-cli.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-cli.html
new file mode 100644
index 0000000..014e56e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-cli.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.3. Configuring kdump on the Command Line</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-configuration.html" title="23.2. Configuring the kdump Service" /><link rel="prev" href="s2-kdump-configuration-gui.html" title="23.2.2. Using the Kernel Dump Configuration Utility" /><link rel="next" href="s2-kdump-configuration-testing.html" title="23.2.4. Testing the 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="s2-kdump-configur
ation-gui.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-kdump-configuration-testing.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-configuration-cli"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.2.3. Configuring kdump on the Command Line</h3></div></div></div><div class="section" id="s3-kdump-configuration-cli-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.1. Configuring the Memory Usage</h4></div></div></div><a id="idm68110576" class="indexterm"></a><a id="idm68108192" class="indexterm"></a><a id="idm68105808" class="indexterm"></a><a id="idm21343824" class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel, as <code class="systemitem">root</code>, edit the <code class="filename">/etc/default/grub</code> file and add the <code class="option">crashkernel=<em class="replaceable"><code><size></code></em>M</code> (or <code class="option">crashkernel=auto</code>) parameter to the list of kernel options (the <code class="option">GRUB_CMDLINE_LINUX</code> line). For example, to reserve 128 MB of memory, use:
+ </div><pre class="programlisting">GRUB_CMDLINE_LINUX="<strong class="userinput"><code>crashkernel=128M</code></strong> quiet rhgb"</pre><div class="para">
+ Then update the configuration file for the GRUB 2 boot loader by typing 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="important"><div class="admonition_header"><h2>Make sure the system has enough memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_17.html#sect-Release_Notes-Hardware_Overview"><em class="citetitle">Hardware Overview</em></a> section of the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><em class="citetitle">Fedora 17 Release Notes</em></a>. When the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Using the crashkernel=auto parameter</h2></div><div class="admonition"><div class="para">
+ In Fedora 17, the <code class="option">crashkernel=auto</code> only reserves memory if the system has 4 GB of physical memory or more.
+ </div></div></div></div><div class="section" id="s3-kdump-configuration-cli-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.2. Configuring the Target Type</h4></div></div></div><a id="idm70483504" class="indexterm"></a><div class="para">
+ When a kernel crash is captured, the core dump can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol. Only one of these options can be set at the moment, and the default option is to store the <code class="filename">vmcore</code> file in the <code class="filename">/var/crash/</code> directory of the local file system. To change this, as <code class="systemitem">root</code>, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor and edit the options as described below.
+ </div><div class="para">
+ To change the local directory in which the core dump is to be saved, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#path /var/crash</code> line, and replace the value with a desired directory path. Optionally, if you wish to write the file to a different partition, follow the same procedure with the <code class="literal">#ext4 /dev/sda3</code> line as well, and change both the file system type and the device (a device name, a file system label, and UUID are all supported) accordingly. For example:
+ </div><pre class="programlisting">ext3 /dev/sda4
+path /usr/local/cores</pre><div class="para">
+ To write the dump directly to a device, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#raw /dev/sda5</code> line, and replace the value with a desired device name. For example:
+ </div><pre class="programlisting">raw /dev/sdb1</pre><div class="para">
+ To store the dump to a remote machine using the NFS protocol, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#net my.server.com:/export/tmp</code> line, and replace the value with a valid hostname and directory path. For example:
+ </div><pre class="programlisting">net penguin.example.com:/export/cores</pre><div class="para">
+ To store the dump to a remote machine using the SSH protocol, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#net user at my.server.com</code> line, and replace the value with a valid username and hostname. For example:
+ </div><pre class="programlisting">net john at penguin.example.com</pre><div class="para">
+ Refer to <a class="xref" href="ch-OpenSSH.html">10章<em>OpenSSH</em></a> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ </div><a id="idm27719248" class="indexterm"></a><div class="para">
+ For a complete list of currently supported targets, see <a class="xref" href="s2-kdump-configuration-gui.html#tab-kdump-supported_targets">表23.1「Supported kdump targets」</a>.
+ </div></div><div class="section" id="s3-kdump-configuration-cli-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.3. Configuring the Core Collector</h4></div></div></div><div class="para">
+ To reduce the size of the <code class="filename">vmcore</code> dump file, <code class="systemitem">kdump</code> allows you to specify an external application (that is, a core collector) to compress the data, and optionally leave out all irrelevant information. Currently, the only fully supported core collector is <code class="command">makedumpfile</code>.
+ </div><div class="para">
+ To enable the core collector, as <code class="systemitem">root</code>, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#core_collector makedumpfile -c --message-level 1 -d 31</code> line, and edit the command line options as described below.
+ </div><a id="idm65415536" class="indexterm"></a><div class="para">
+ To enable the dump file compression, add the <code class="option">-c</code> parameter. For example:
+ </div><pre class="programlisting">core_collector makedumpfile -c</pre><a id="idm17519776" class="indexterm"></a><div class="para">
+ To remove certain pages from the dump, add the <code class="option">-d <em class="replaceable"><code>value</code></em></code> parameter, where <em class="replaceable"><code>value</code></em> is a sum of values of pages you want to omit as described in <a class="xref" href="s2-kdump-configuration-cli.html#table-kdump-configuration-cli-filtering-makedumpfile">表23.2「Supported filtering levels」</a>. For example, to remove both zero and free pages, use the following:
+ </div><pre class="programlisting">core_collector makedumpfile -d 17 -c</pre><div class="para">
+ Refer to the manual page for <code class="command">makedumpfile</code> for a complete list of available options.
+ </div><div class="table" id="table-kdump-configuration-cli-filtering-makedumpfile"><h6>表23.2 Supported filtering levels</h6><div class="table-contents"><table summary="Supported filtering levels" border="1"><colgroup><col width="20%" class="option" /><col width="80%" class="description" /></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">1</code>
+ </td><td class="">
+ Zero pages
+ </td></tr><tr><td class="">
+ <code class="option">2</code>
+ </td><td class="">
+ Cache pages
+ </td></tr><tr><td class="">
+ <code class="option">4</code>
+ </td><td class="">
+ Cache private
+ </td></tr><tr><td class="">
+ <code class="option">8</code>
+ </td><td class="">
+ User pages
+ </td></tr><tr><td class="">
+ <code class="option">16</code>
+ </td><td class="">
+ Free pages
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s3-kdump-configuration-cli-action"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.4. Changing the Default Action</h4></div></div></div><a id="idm43760320" class="indexterm"></a><div class="para">
+ By default, when <code class="systemitem">kdump</code> fails to create a core dump, the root file system is mounted and <code class="command">/sbin/init</code> is run. To change this behavior, as <code class="systemitem">root</code>, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor, remove the hash sign (<span class="quote">「<span class="quote">#</span>」</span>) from the beginning of the <code class="literal">#default shell</code> line, and replace the value with a desired action as described in <a class="xref" href="s2-kdump-configuration-cli.html#table-kdump-configuration-cli-action-actions">表23.3「Supported actions」</a>.
+ </div><div class="table" id="table-kdump-configuration-cli-action-actions"><h6>表23.3 Supported actions</h6><div class="table-contents"><table summary="Supported actions" border="1"><colgroup><col width="20%" class="option" /><col width="80%" class="description" /></colgroup><thead><tr><th class="">
+ オプション
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">reboot</code>
+ </td><td class="">
+ Reboot the system, losing the core in the process.
+ </td></tr><tr><td class="">
+ <code class="option">halt</code>
+ </td><td class="">
+ Halt the system.
+ </td></tr><tr><td class="">
+ <code class="option">poweroff</code>
+ </td><td class="">
+ Power off the system.
+ </td></tr><tr><td class="">
+ <code class="option">shell</code>
+ </td><td class="">
+ Run the <span class="application"><strong>msh</strong></span> session from within the initramfs, allowing a user to record the core manually.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ 例えば:
+ </div><pre class="programlisting">default halt</pre></div><div class="section" id="s3-kdump-configuration-cli-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.3.5. サービスの有効化</h4></div></div></div><a id="idm68696592" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, 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">enable</code> <code class="option">kdump.service</code></pre><div class="para">
+ Similarly, typing <code class="command">systemctl disable kdump.service</code> will disable it. To start the service in the current session, use the following command as <code class="systemitem">root</code>:
+ </div><a id="idm65700192" class="indexterm"></a><pre class="synopsis"><code class="command">systemctl</code> <code class="option">start</code> <code class="option">kdump.service</code></pre><div class="para">
+ For more information on services and their configuration, refer to <a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-configuration-gui.html"><strong>戻る</strong>23.2.2. Using the Kernel Dump Configuration Utili...</a></li><li class="up"><a accesskey="u" href="#"><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-kdump-configuration-testing.html"><strong>次へ</strong>23.2.4. Testing the Configuration</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-gui.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-gui.html
new file mode 100644
index 0000000..c74479f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-gui.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>23.2.2. Using the Kernel Dump Configuration Utility</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-configuration.html" title="23.2. Configuring the kdump Service" /><link rel="prev" href="s1-kdump-configuration.html" title="23.2. Configuring the kdump Service" /><link rel="next" href="s2-kdump-configuration-cli.html" title="23.2.3. Configuring kdump on the Command Line" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump-configuration.html">
<strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-kdump-configuration-cli.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-configuration-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.2.2. Using the Kernel Dump Configuration Utility</h3></div></div></div><a id="idm20355568" class="indexterm"></a><a id="idm20353648" class="indexterm"></a><div class="para">
+ To start the <span class="application"><strong>Kernel Dump Configuration</strong></span> utility, select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>Other</strong></span> → <span class="guimenuitem"><strong>Kernel crash dumps</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">system-config-kdump</code> at a shell prompt. You will be presented with a window as shown in <a class="xref" href="s2-kdump-configuration-gui.html#fig-kdump-kernel_dump_configuration">図23.1「Basic Settings」</a>.
+ </div><div class="para">
+ The utility allows you to configure <code class="systemitem">kdump</code> as well as to enable or disable starting the service at boot time. When you are done, click <span class="guibutton"><strong>Apply</strong></span> to save the changes. The system reboot will be requested, and unless you are already authenticated, you will be prompted to enter the superuser password.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure the system has enough memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_17.html#sect-Release_Notes-Hardware_Overview"><em class="citetitle">Hardware Overview</em></a> section of the <a href="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><em class="citetitle">Fedora 17 Release Notes</em></a>. When the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ </div></div></div><div class="section" id="s3-kdump-configuration-gui-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.1. サービスの有効化</h4></div></div></div><a id="idm54228736" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, click the <span class="guibutton"><strong>Enable</strong></span> button on the toolbar. This will enable the service and start it for the current session. Similarly, clicking the <span class="guibutton"><strong>Disable</strong></span> button will disable it and stop the service immediately.
+ </div><div class="para">
+ For more information on system services and their configuration, refer to <a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>.
+ </div></div><div class="section" id="s3-kdump-configuration-gui-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.2. The Basic Settings Tab</h4></div></div></div><a id="idm54222720" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Basic Settings</strong></span> tab enables you to configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel. To do so, select the <span class="guilabel"><strong>Manual kdump memory settings</strong></span> radio button, and click the up and down arrow buttons next to the <span class="guilabel"><strong>New kdump Memory</strong></span> field to increase or decrease the value. Notice that the <span class="guilabel"><strong>Usable Memory</strong></span> field changes accordingly showing you the remaining memory that will be available to the system.
+ </div><div class="figure" id="fig-kdump-kernel_dump_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration.png" alt="Basic Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Basic Settings</strong></span>
+ </div></div></div></div><h6>図23.1 Basic Settings</h6></div><br class="figure-break" /></div><div class="section" id="s3-kdump-configuration-gui-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.3. The Target Settings Tab</h4></div></div></div><a id="idm61189792" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Target Settings</strong></span> tab enables you to specify the target location for the <code class="filename">vmcore</code> dump. It can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol.
+ </div><div class="figure" id="fig-kdump-kernel_dump_configuration-target_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-target_settings.png" alt="Target Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Target Settings</strong></span>
+ </div></div></div></div><h6>図23.2 Target Settings</h6></div><br class="figure-break" /><div class="para">
+ To save the dump to the local file system, select the <span class="guilabel"><strong>Local filesystem</strong></span> radio button. Optionally, you can customize the settings by choosing a different partition from the <span class="guilabel"><strong>Partition</strong></span>, and a target directory from the <span class="guilabel"><strong>Path</strong></span> pulldown lists.
+ </div><div class="para">
+ To write the dump directly to a device, select the <span class="guilabel"><strong>Raw device</strong></span> radio button, and choose the desired target device from the pulldown list next to it.
+ </div><div class="para">
+ To store the dump to a remote machine, select the <span class="guilabel"><strong>Network</strong></span> radio button. To use the NFS protocol, select the <span class="guilabel"><strong>NFS</strong></span> radio button, and fill the <span class="guilabel"><strong>Server name</strong></span> and <span class="guilabel"><strong>Path to directory</strong></span> fields. To use the SSH protocol, select the <span class="guilabel"><strong>SSH</strong></span> radio button, and fill the <span class="guilabel"><strong>Server name</strong></span>, <span class="guilabel"><strong>Path to directory</strong></span>, and <span class="guilabel"><strong>User name</strong></span> fields with the remote server address, target directory, and a valid remote user name respectively. Refer to <a class="xref" href="ch-OpenSSH.html">10章<em>OpenSSH</em></a> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ </div><a id="idm55124608" class="indexterm"></a><div class="para">
+ For a complete list of currently supported targets, see <a class="xref" href="s2-kdump-configuration-gui.html#tab-kdump-supported_targets">表23.1「Supported kdump targets」</a>.
+ </div><div class="table" id="tab-kdump-supported_targets"><h6>表23.1 Supported kdump targets</h6><div class="table-contents"><table summary="Supported kdump targets" border="1"><colgroup><col width="20%" class="type" /><col width="40%" class="supported" /><col width="40%" class="unsupported" /></colgroup><thead><tr><th class="">
+ タイプ（Type）
+ </th><th class="">
+ Supported Targets
+ </th><th class="">
+ Unsupported Targets
+ </th></tr></thead><tbody><tr><td class="" valign="middle">
+ Raw device
+ </td><td class="">
+ All locally attached raw disks and partitions.
+ </td><td class="">
+ —
+ </td></tr><tr><td class="" valign="middle">
+ Local file system
+ </td><td class="">
+ <code class="systemitem">ext2</code>, <code class="systemitem">ext3</code>, <code class="systemitem">ext4</code>, <code class="systemitem">minix</code> file systems on directly attached disk drives, hardware RAID logical drives, LVM devices, and <code class="systemitem">mdraid</code> arrays.
+ </td><td class="">
+ The <code class="systemitem">eCryptfs</code> file system.
+ </td></tr><tr><td class="" rowspan="7" valign="middle">
+ Remote directory
+ </td><td class="">
+ Remote directories accessed using the <code class="systemitem">NFS</code> or <code class="systemitem">SSH</code> protocol over <code class="systemitem">IPv4</code>.
+ </td><td class="">
+ Remote directories on the <code class="systemitem">rootfs</code> file system accessed using the <code class="systemitem">NFS</code> protocol.
+ </td></tr><tr><td class="">
+ Remote directories accessed using the <code class="systemitem">iSCSI</code> protocol over hardware initiators.
+ </td><td class="">
+ Remote directories accessed using the <code class="systemitem">iSCSI</code> protocol over software initiators.
+ </td></tr><tr><td class="" rowspan="5">
+ —
+ </td><td class="">
+ Remote directories accessed over <code class="systemitem">IPv6</code>.
+ </td></tr><tr><td class="">
+ Remote directories accessed using the <code class="systemitem">SMB</code>/<code class="systemitem">CIFS</code> protocol.
+ </td></tr><tr><td class="">
+ Remote directories accessed using the <code class="systemitem">FCoE</code> (<em class="firstterm">Fibre Channel over Ethernet</em>) protocol.
+ </td></tr><tr><td class="">
+ Remote directories accessed using wireless network interfaces.
+ </td></tr><tr><td class="">
+ Multipath-based storages.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s3-kdump-configuration-gui-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.4. The Filtering Settings Tab</h4></div></div></div><a id="idm49137392" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Filtering Settings</strong></span> tab enables you to select the filtering level for the <code class="filename">vmcore</code> dump.
+ </div><div class="figure" id="fig-kdump-kernel_dump_configuration-filtering_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-filtering_settings.png" alt="Filtering Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Filtering Settings</strong></span>
+ </div></div></div></div><h6>図23.3 Filtering Settings</h6></div><br class="figure-break" /><div class="para">
+ To exclude the <span class="guilabel"><strong>zero page</strong></span>, <span class="guilabel"><strong>cache page</strong></span>, <span class="guilabel"><strong>cache private</strong></span>, <span class="guilabel"><strong>user data</strong></span>, or <span class="guilabel"><strong>free page</strong></span> from the dump, select the checkbox next to the appropriate label.
+ </div></div><div class="section" id="s3-kdump-configuration-gui-expert"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">23.2.2.5. The Expert Settings Tab</h4></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Expert Settings</strong></span> tab enables you to choose which kernel and initial RAM disk to use, as well as to customize the options that are passed to the kernel and the core collector program.
+ </div><div class="figure" id="fig-kdump-kernel_dump_configuration-expert_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-expert_settings.png" alt="Expert Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Expert Settings</strong></span>
+ </div></div></div></div><h6>図23.4 Expert Settings</h6></div><br class="figure-break" /><a id="idm70064544" class="indexterm"></a><div class="para">
+ To use a different initial RAM disk, select the <span class="guilabel"><strong>Custom initrd</strong></span> radio button, and choose the desired RAM disk from the pulldown list next to it.
+ </div><a id="idm70061264" class="indexterm"></a><div class="para">
+ To capture a different kernel, select the <span class="guilabel"><strong>Custom kernel</strong></span> radio button, and choose the desired kernel image from the pulldown list on the right.
+ </div><a id="idm70057872" class="indexterm"></a><div class="para">
+ To adjust the list of options that are passed to the kernel at boot time, edit the content of the <span class="guilabel"><strong>Edited</strong></span> text field. Note that you can always revert your changes by clicking the <span class="guibutton"><strong>Refresh</strong></span> button.
+ </div><a id="idm50231392" class="indexterm"></a><div class="para">
+ To choose what action to perform when <code class="systemitem">kdump</code> fails to create a core dump, select an appropriate option from the <span class="guilabel"><strong>Default action</strong></span> pulldown list. Available options are <span class="guimenuitem"><strong>mount rootfs and run /sbin/init</strong></span> (the default action), <span class="guimenuitem"><strong>reboot</strong></span> (to reboot the system), <span class="guimenuitem"><strong>shell</strong></span> (to present a user with an interactive shell prompt), <span class="guimenuitem"><strong>halt</strong></span> (to halt the system), and <span class="guimenuitem"><strong>poweroff</strong></span> (to power the system off).
+ </div><a id="idm55601232" class="indexterm"></a><div class="para">
+ To customize the options that are passed to the <code class="command">makedumpfile</code> core collector, edit the <span class="guilabel"><strong>Core collector</strong></span> text field; see <a class="xref" href="s2-kdump-configuration-cli.html#s3-kdump-configuration-cli-filtering">「Configuring the Core Collector」</a> for more information.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kdump-configuration.html"><strong>戻る</strong>23.2. Configuring the kdump 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-kdump-configuration-cli.html"><strong>次へ</strong>23.2.3. Configuring kdump on the Command Line</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-testing.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-testing.html
new file mode 100644
index 0000000..3c2062a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-configuration-testing.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>23.2.4. Testing the 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-configuration.html" title="23.2. Configuring the kdump Service" /><link rel="prev" href="s2-kdump-configuration-cli.html" title="23.2.3. Configuring kdump on the Command Line" /><link rel="next" href="s1-kdump-crash.html" title="23.3. Analyzing the Core Dump" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump-configuration-cli.html"><strong>æˆ
»ã‚‹</strong></a></li><li class="next"><a accesskey="n" href="s1-kdump-crash.html"><strong>次ã¸</strong></a></li></ul><div class="section" id="s2-kdump-configuration-testing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.2.4. Testing the Configuration</h3></div></div></div><a id="idm51790416" class="indexterm"></a><div class="warning"><div class="admonition_header"><h2>Be careful when using these commands</h2></div><div class="admonition"><div class="para">
+ The commands below will cause the kernel to crash. Use caution when following these steps, and by no means use them on a production machine.
+ </div></div></div><div class="para">
+ To test the configuration, reboot the system with <code class="systemitem">kdump</code> enabled, and make sure that the service is running (refer to <a class="xref" href="s1-services-running.html">「サービスの実行」</a> for more information on how to run a service in Fedora):
+ </div><pre class="screen"><code class="command">systemctl is-active kdump.service</code></pre><div class="para">
+ Then type the following commands at a shell prompt:
+ </div><pre class="screen"><code class="command">echo 1 > /proc/sys/kernel/sysrq</code>
+<code class="command">echo c > /proc/sysrq-trigger</code></pre><div class="para">
+ This will force the Linux kernel to crash, and the <code class="filename"><em class="replaceable"><code>address</code></em>-<em class="replaceable"><code>YYYY-MM-DD</code></em>-<em class="replaceable"><code>HH:MM:SS</code></em>/vmcore</code> file will be copied to the location you have selected in the configuration (that is, to <code class="filename">/var/crash/</code> by default).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-configuration-cli.html"><strong>戻る</strong>23.2.3. Configuring kdump on the Command Line</a></li><li class="up"><a accesskey="u" href="#"><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-kdump-crash.html"><strong>次へ</strong>23.3. Analyzing the Core Dump</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-backtrace.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-backtrace.html
new file mode 100644
index 0000000..3701b8e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-backtrace.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>23.3.3. Displaying a Backtrace</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-crash.html" title="23.3. Analyzing the Core Dump" /><link rel="prev" href="s2-kdump-crash-log.html" title="23.3.2. Displaying the Message Buffer" /><link rel="next" href="s2-kdump-crash-processes.html" title="23.3.4. Displaying a Process Status" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump-crash-log.html"><strong>戻る</strong></a></li>
<li class="next"><a accesskey="n" href="s2-kdump-crash-processes.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-crash-backtrace"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.3. Displaying a Backtrace</h3></div></div></div><a id="idm52230608" class="indexterm"></a><div class="para">
+ To display the kernel stack trace, type the <code class="command">bt</code> command at the interactive prompt. You can use <code class="command">bt <em class="replaceable"><code>pid</code></em></code> to display the backtrace of the selected process.
+ </div><div class="example" id="ex-kdump-crash-backtrace"><h6>例23.3 Displaying the kernel stack trace</h6><div class="example-contents"><pre class="screen">crash> <code class="command">bt</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ #0 [ef4dbdcc] crash_kexec at c0494922
+ #1 [ef4dbe20] oops_end at c080e402
+ #2 [ef4dbe34] no_context at c043089d
+ #3 [ef4dbe58] bad_area at c0430b26
+ #4 [ef4dbe6c] do_page_fault at c080fb9b
+ #5 [ef4dbee4] error_code (via page_fault) at c080d809
+ EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000 EBP: 00000000
+ DS: 007b ESI: c0a09ca0 ES: 007b EDI: 00000286 GS: 00e0
+ CS: 0060 EIP: c068124f ERR: ffffffff EFLAGS: 00010096
+ #6 [ef4dbf18] sysrq_handle_crash at c068124f
+ #7 [ef4dbf24] __handle_sysrq at c0681469
+ #8 [ef4dbf48] write_sysrq_trigger at c068150a
+ #9 [ef4dbf54] proc_reg_write at c0569ec2
+#10 [ef4dbf74] vfs_write at c051de4e
+#11 [ef4dbf94] sys_write at c051e8cc
+#12 [ef4dbfb0] system_call at c0409ad5
+ EAX: ffffffda EBX: 00000001 ECX: b7776000 EDX: 00000002
+ DS: 007b ESI: 00000002 ES: 007b EDI: b7776000
+ SS: 007b ESP: bfcb2088 EBP: bfcb20b4 GS: 0033
+ CS: 0073 EIP: 00edc416 ERR: 00000004 EFLAGS: 00000246</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help bt</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-log.html"><strong>戻る</strong>23.3.2. Displaying the Message Buffer</a></li><li class="up"><a accesskey="u" href="#"><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-kdump-crash-processes.html"><strong>次へ</strong>23.3.4. Displaying a Process Status</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-exit.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-exit.html
new file mode 100644
index 0000000..9fb80a6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-exit.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7. Exiting the Utility</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-crash.html" title="23.3. Analyzing the Core Dump" /><link rel="prev" href="s2-kdump-crash-files.html" title="23.3.6. Displaying Open Files" /><link rel="next" href="s1-kdump-resources.html" title="23.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-kdump-crash-files.html"><strong>戻る</strong></a></li><li class="next
"><a accesskey="n" href="s1-kdump-resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-crash-exit"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.7. Exiting the Utility</h3></div></div></div><div class="para">
+ To exit the interactive prompt and terminate <span class="application"><strong>crash</strong></span>, type <code class="command">exit</code> or <code class="command">q</code>.
+ </div><div class="example" id="ex-kdump-crash-exit"><h6>例23.7 Exiting the crash utility</h6><div class="example-contents"><pre class="screen">crash> <code class="command">exit</code>
+~]#</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-files.html"><strong>戻る</strong>23.3.6. Displaying Open Files</a></li><li class="up"><a accesskey="u" href="#"><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-kdump-resources.html"><strong>次へ</strong>23.4. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-files.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-files.html
new file mode 100644
index 0000000..0ae04a9
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-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>23.3.6. Displaying Open Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-crash.html" title="23.3. Analyzing the Core Dump" /><link rel="prev" href="s2-kdump-crash-memory.html" title="23.3.5. Displaying Virtual Memory Information" /><link rel="next" href="s2-kdump-crash-exit.html" title="23.3.7. Exiting the Utility" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump-crash-memory.html"><strong>戻る</strong></a></li
><li class="next"><a accesskey="n" href="s2-kdump-crash-exit.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-crash-files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.6. Displaying Open Files</h3></div></div></div><a id="idm38158960" class="indexterm"></a><div class="para">
+ To display information about open files, type the <code class="command">files</code> command at the interactive prompt. You can use <code class="command">files <em class="replaceable"><code>pid</code></em></code> to display files opened by the selected process.
+ </div><div class="example" id="ex-kdump-crash-files"><h6>例23.6 Displaying information about open files of the current context</h6><div class="example-contents"><pre class="screen">crash> <code class="command">files</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ROOT: / CWD: /root
+ FD FILE DENTRY INODE TYPE PATH
+ 0 f734f640 eedc2c6c eecd6048 CHR /pts/0
+ 1 efade5c0 eee14090 f00431d4 REG /proc/sysrq-trigger
+ 2 f734f640 eedc2c6c eecd6048 CHR /pts/0
+ 10 f734f640 eedc2c6c eecd6048 CHR /pts/0
+255 f734f640 eedc2c6c eecd6048 CHR /pts/0</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help files</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-memory.html"><strong>戻る</strong>23.3.5. Displaying Virtual Memory 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-kdump-crash-exit.html"><strong>次へ</strong>23.3.7. Exiting the Utility</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-log.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-log.html
new file mode 100644
index 0000000..a71b8fc
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-log.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>23.3.2. Displaying the Message Buffer</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-crash.html" title="23.3. Analyzing the Core Dump" /><link rel="prev" href="s1-kdump-crash.html" title="23.3. Analyzing the Core Dump" /><link rel="next" href="s2-kdump-crash-backtrace.html" title="23.3.3. Displaying a Backtrace" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump-crash.html"><strong>戻る</strong></a></li><li class="next"><a a
ccesskey="n" href="s2-kdump-crash-backtrace.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-crash-log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.2. Displaying the Message Buffer</h3></div></div></div><a id="idm41937584" class="indexterm"></a><div class="para">
+ To display the kernel message buffer, type the <code class="command">log</code> command at the interactive prompt.
+ </div><div class="example" id="ex-kdump-crash-log"><h6>例23.2 Displaying the kernel message buffer</h6><div class="example-contents"><pre class="screen">crash> <code class="command">log</code>
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+EIP: 0060:[<c068124f>] EFLAGS: 00010096 CPU: 2
+EIP is at sysrq_handle_crash+0xf/0x20
+EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000
+ESI: c0a09ca0 EDI: 00000286 EBP: 00000000 ESP: ef4dbf24
+ DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
+Process bash (pid: 5591, ti=ef4da000 task=f196d560 task.ti=ef4da000)
+Stack:
+ c068146b c0960891 c0968653 00000003 00000000 00000002 efade5c0 c06814d0
+<0> fffffffb c068150f b7776000 f2600c40 c0569ec4 ef4dbf9c 00000002 b7776000
+<0> efade5c0 00000002 b7776000 c0569e60 c051de50 ef4dbf9c f196d560 ef4dbfb4
+Call Trace:
+ [<c068146b>] ? __handle_sysrq+0xfb/0x160
+ [<c06814d0>] ? write_sysrq_trigger+0x0/0x50
+ [<c068150f>] ? write_sysrq_trigger+0x3f/0x50
+ [<c0569ec4>] ? proc_reg_write+0x64/0xa0
+ [<c0569e60>] ? proc_reg_write+0x0/0xa0
+ [<c051de50>] ? vfs_write+0xa0/0x190
+ [<c051e8d1>] ? sys_write+0x41/0x70
+ [<c0409adc>] ? syscall_call+0x7/0xb
+Code: a0 c0 01 0f b6 41 03 19 d2 f7 d2 83 e2 03 83 e0 cf c1 e2 04 09 d0 88 41 03 f3 c3 90 c7 05 c8 1b 9e c0 01 00 00 00 0f ae f8 89 f6 <c6> 05 00 00 00 00 01 c3 89 f6 8d bc 27 00 00 00 00 8d 50 d0 83
+EIP: [<c068124f>] sysrq_handle_crash+0xf/0x20 SS:ESP 0068:ef4dbf24
+CR2: 0000000000000000</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help log</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kdump-crash.html"><strong>戻る</strong>23.3. Analyzing the Core Dump</a></li><li class="up"><a accesskey="u" href="#"><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-kdump-crash-backtrace.html"><strong>次へ</strong>23.3.3. Displaying a Backtrace</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-memory.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-memory.html
new file mode 100644
index 0000000..b316733
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-memory.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>23.3.5. Displaying Virtual Memory 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-crash.html" title="23.3. Analyzing the Core Dump" /><link rel="prev" href="s2-kdump-crash-processes.html" title="23.3.4. Displaying a Process Status" /><link rel="next" href="s2-kdump-crash-files.html" title="23.3.6. Displaying Open Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump-crash-processes.html"><strong>戻る</strong></a></li>
<li class="next"><a accesskey="n" href="s2-kdump-crash-files.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-crash-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.5. Displaying Virtual Memory Information</h3></div></div></div><a id="idm57224544" class="indexterm"></a><div class="para">
+ To display basic virtual memory information, type the <code class="command">vm</code> command at the interactive prompt. You can use <code class="command">vm <em class="replaceable"><code>pid</code></em></code> to display information on the selected process.
+ </div><div class="example" id="ex-kdump-crash-memory"><h6>例23.5 Displaying virtual memory information of the current context</h6><div class="example-contents"><pre class="screen">crash> <code class="command">vm</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ MM PGD RSS TOTAL_VM
+f19b5900 ef9c6000 1648k 5084k
+ VMA START END FLAGS FILE
+f1bb0310 242000 260000 8000875 /lib/ld-2.12.so
+f26af0b8 260000 261000 8100871 /lib/ld-2.12.so
+efbc275c 261000 262000 8100873 /lib/ld-2.12.so
+efbc2a18 268000 3ed000 8000075 /lib/libc-2.12.so
+efbc23d8 3ed000 3ee000 8000070 /lib/libc-2.12.so
+efbc2888 3ee000 3f0000 8100071 /lib/libc-2.12.so
+efbc2cd4 3f0000 3f1000 8100073 /lib/libc-2.12.so
+efbc243c 3f1000 3f4000 100073
+efbc28ec 3f6000 3f9000 8000075 /lib/libdl-2.12.so
+efbc2568 3f9000 3fa000 8100071 /lib/libdl-2.12.so
+efbc2f2c 3fa000 3fb000 8100073 /lib/libdl-2.12.so
+f26af888 7e6000 7fc000 8000075 /lib/libtinfo.so.5.7
+f26aff2c 7fc000 7ff000 8100073 /lib/libtinfo.so.5.7
+efbc211c d83000 d8f000 8000075 /lib/libnss_files-2.12.so
+efbc2504 d8f000 d90000 8100071 /lib/libnss_files-2.12.so
+efbc2950 d90000 d91000 8100073 /lib/libnss_files-2.12.so
+f26afe00 edc000 edd000 4040075
+f1bb0a18 8047000 8118000 8001875 /bin/bash
+f1bb01e4 8118000 811d000 8101873 /bin/bash
+f1bb0c70 811d000 8122000 100073
+f26afae0 9fd9000 9ffa000 100073
+<span class="emphasis"><em>... several lines omitted ...</em></span></pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help vm</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-processes.html"><strong>戻る</strong>23.3.4. Displaying a Process Status</a></li><li class="up"><a accesskey="u" href="#"><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-kdump-crash-files.html"><strong>次へ</strong>23.3.6. Displaying Open Files</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-processes.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-processes.html
new file mode 100644
index 0000000..6c19de8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-crash-processes.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.3.4. Displaying a Process Status</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-crash.html" title="23.3. Analyzing the Core Dump" /><link rel="prev" href="s2-kdump-crash-backtrace.html" title="23.3.3. Displaying a Backtrace" /><link rel="next" href="s2-kdump-crash-memory.html" title="23.3.5. Displaying Virtual Memory 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-kdump-crash-backtrace.html"><strong>戻る</stro
ng></a></li><li class="next"><a accesskey="n" href="s2-kdump-crash-memory.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-crash-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.3.4. Displaying a Process Status</h3></div></div></div><a id="idm68499904" class="indexterm"></a><div class="para">
+ To display status of processes in the system, type the <code class="command">ps</code> command at the interactive prompt. You can use <code class="command">ps <em class="replaceable"><code>pid</code></em></code> to display the status of the selected process.
+ </div><div class="example" id="ex-kdump-crash-processes"><h6>例23.4 Displaying status of processes in the system</h6><div class="example-contents"><pre class="screen">crash> <code class="command">ps</code>
+ PID PPID CPU TASK ST %MEM VSZ RSS COMM
+> 0 0 0 c09dc560 RU 0.0 0 0 [swapper]
+> 0 0 1 f7072030 RU 0.0 0 0 [swapper]
+ 0 0 2 f70a3a90 RU 0.0 0 0 [swapper]
+> 0 0 3 f70ac560 RU 0.0 0 0 [swapper]
+ 1 0 1 f705ba90 IN 0.0 2828 1424 init
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+ 5566 1 1 f2592560 IN 0.0 12876 784 auditd
+ 5567 1 2 ef427560 IN 0.0 12876 784 auditd
+ 5587 5132 0 f196d030 IN 0.0 11064 3184 sshd
+> 5591 5587 2 f196d560 RU 0.0 5084 1648 bash</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help ps</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-backtrace.html"><strong>戻る</strong>23.3.3. Displaying a Backtrace</a></li><li class="up"><a accesskey="u" href="#"><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-kdump-crash-memory.html"><strong>次へ</strong>23.3.5. Displaying Virtual Memory Information</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-resources-online.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-resources-online.html
new file mode 100644
index 0000000..7a5c8aa
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kdump-resources-online.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>23.4.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kdump-resources.html" title="23.4. その他のリソース" /><link rel="prev" href="s1-kdump-resources.html" title="23.4. その他のリソース" /><link rel="next" href="appe-Consistent_Network_Device_Naming.html" title="付録A Consistent Network Device Naming" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-kdump-resources.html"><strong>戻る</
strong></a></li><li class="next"><a accesskey="n" href="appe-Consistent_Network_Device_Naming.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kdump-resources-online"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">23.4.2. 役に立つ Web サイト</h3></div></div></div><a id="idm50725696" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="https://access.redhat.com/kb/docs/DOC-6039">https://access.redhat.com/kb/docs/DOC-6039</a></span></dt><dd><div class="para">
+ The Red Hat Knowledgebase article about the <code class="command">kexec</code> and <code class="systemitem">kdump</code> configuration.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="https://access.redhat.com/kb/docs/DOC-45183">https://access.redhat.com/kb/docs/DOC-45183</a></span></dt><dd><div class="para">
+ The Red Hat Knowledgebase article about supported <code class="systemitem">kdump</code> targets.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://people.redhat.com/anderson/">http://people.redhat.com/anderson/</a></span></dt><dd><div class="para">
+ The <span class="application"><strong>crash</strong></span> utility homepage.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kdump-resources.html"><strong>戻る</strong>23.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="appe-Consistent_Network_Device_Naming.html"><strong>次へ</strong>付録A Consistent Network Device Naming</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html
new file mode 100644
index 0000000..580a259
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>21.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kernel-boot-loader.html" title="21.6. ブートローダの確認" /><link rel="prev" href="s1-kernel-boot-loader.html" title="21.6. ブートローダの確認" /><link rel="next" href="s2-kernel-boot-loader-pseries.html" title="21.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">21.6.2. Configuring the OS/400 Boot Loader</h3></div></div></div><a id="idm57982912" class="indexterm"></a><a id="idm57981472" 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>21.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>21.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/17/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html
new file mode 100644
index 0000000..eebc253
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>21.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kernel-boot-loader.html" title="21.6. ブートローダの確認" /><link rel="prev" href="s2-kernel-boot-loader-iseries.html" title="21.6.2. Configuring the OS/400 Boot Loader" /><link rel="next" href="ch-Working_with_Kernel_Modules.html" title="第22章 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">21.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>21.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>第22章 Working with Kernel Modules</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kernel-modules-additional-resources-websites.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kernel-modules-additional-resources-websites.html
new file mode 100644
index 0000000..6c2ae45
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-kernel-modules-additional-resources-websites.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>22.8.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-kernel-modules-additional-resources.html" title="22.8. その他のリソース" /><link rel="prev" href="s1-kernel-modules-additional-resources.html" title="22.8. その他のリソース" /><link rel="next" href="ch-kdump.html" title="第23章 The kdump Crash Recovery 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="s1-kernel-modules-additional-
resources.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ch-kdump.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-kernel-modules-additional-resources-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.8.2. 役に立つ Web サイト</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel Module HOWTO</a></span></dt><dd><div class="para">
+ The <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> from the Linux Documentation Project contains further information on working with kernel modules.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-modules-additional-resources.html"><strong>戻る</strong>22.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="ch-kdump.html"><strong>次へ</strong>第23章 The kdump Crash Recovery Service</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-keys-checking.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-keys-checking.html
new file mode 100644
index 0000000..f2725b2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-keys-checking.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>B.3.2. Verifying Signature of 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-check-rpm-sig.html" title="B.3. パッケージの署名を確認する" /><link rel="prev" href="s1-check-rpm-sig.html" title="B.3. パッケージの署名を確認する" /><link rel="next" href="s1-rpm-impressing.html" title="B.4. Practical and 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-check-rpm-sig.html"><strong
>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-rpm-impressing.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-keys-checking"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.3.2. Verifying Signature of Packages</h3></div></div></div><div class="para">
+ To check the GnuPG signature of an RPM file after importing the builder's GnuPG key, use the following command (replace <em class="replaceable"><code><rpm_file></code></em> with the file name of the RPM package):
+ </div><pre class="screen">
+<code class="command">rpm -K <em class="replaceable"><code><rpm_file></code></em> </code>
+</pre><div class="para">
+ If all goes well, the following message is displayed: <code class="computeroutput">rsa sha1 (md5) pgp md5 OK</code>. This means that the signature of the package has been verified, that it is not corrupt, and is therefore safe to install and use.
+ </div><div class="para">
+ For more information, including a list of currently-used Fedora Project keys and their fingerprints, refer to <a href="http://fedoraproject.org/en/keys">http://fedoraproject.org/en/keys</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-check-rpm-sig.html"><strong>戻る</strong>B.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-rpm-impressing.html"><strong>次へ</strong>B.4. Practical and Common Examples of RPM Usage</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-log-files-useful-websites.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-log-files-useful-websites.html
new file mode 100644
index 0000000..b92b81c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-log-files-useful-websites.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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-log-files-additional-resources.html" title="18.6. その他のリソース" /><link rel="prev" href="s1-log-files-additional-resources.html" title="18.6. その他のリソース" /><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="s1-log-files-additio
nal-resources.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="s2-log-files-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.6.2. 役に立つ Web サイト</h3></div></div></div><a id="idm36827008" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/">http://www.rsyslog.com/</a> — <span class="package">rsyslog</span> の機能、ドキュメント、設定例、およびビデオチュートリアルの包括的な技術詳細を提供します。
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://wiki.rsyslog.com/index.php/Main_Page">http://wiki.rsyslog.com/index.php/Main_Page</a> — 有用な <code class="filename">/etc/rsyslog.conf</code> 設定例があります。
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-log-files-additional-resources.html"><strong>戻る</strong>18.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="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/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-alias.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-alias.html
new file mode 100644
index 0000000..fd4ee5d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-alias.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>7.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-networkscripts-interfaces.html" title="7.2. インターフェース設定ファイル" /><link rel="prev" href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html" title="7.2.4. Setting up 802.1q VLAN tagging" /><link rel="next" href="s2-networkscripts-interfaces-ppp0.html" title="7.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="p
revious"><a accesskey="p" href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-ppp0.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-networkscripts-interfaces-alias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.5. エイリアス ファイルとクローン ファイル</h3></div></div></div><a id="idm69877904" class="indexterm"></a><a id="idm58607440" class="indexterm"></a><div class="para">
+ Two lesser-used types of interface configuration files are <em class="firstterm">alias</em> and <em class="firstterm">clone</em> files. As the <code class="command">ip</code> command of the <span class="package">iproute</span> package now supports assigning multiple address to the same interface it is no longer necessary to use this method of binding multiple addresses to the same interface.
+ </div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ At the time of writing, <span class="application"><strong>NetworkManager</strong></span> does not detect IP aliases in <code class="filename">ifcfg</code> files. For example, if <code class="filename">ifcfg-eth0</code> and <code class="filename">ifcfg-eth0:1</code> files are present, <span class="application"><strong>NetworkManager</strong></span> creates two connections, which will cause confusion.
+ </div></div></div><div class="para">
+ For new installations, users should select the <span class="guilabel"><strong>Manual</strong></span> method on the IPv4 or IPv6 tab in <span class="application"><strong>NetworkManager</strong></span> to assign multiple IP address to the same interface. For more information on using this tool, refer to <a class="xref" href="ch-NetworkManager.html">6章<em>NetworkManager</em></a>.
+ </div><div class="para">
+ Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the <code class="filename">ifcfg-<em class="replaceable"><code>if-name</code></em>:<em class="replaceable"><code>alias-value</code></em></code> naming scheme.
+ </div><div class="para">
+ For example, an <code class="filename">ifcfg-eth0:0</code> file could be configured to specify <code class="literal">DEVICE=eth0:0</code> and a static IP address of <code class="systemitem">10.0.0.2</code>, serving as an alias of an Ethernet interface already configured to receive its IP information via DHCP in <code class="filename">ifcfg-eth0</code>. Under this configuration, <code class="systemitem">eth0</code> is bound to a dynamic IP address, but the same physical network card can receive requests via the fixed, <code class="systemitem">10.0.0.2</code> IP address.
+ </div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
+ エイリアス インターフェースは DHCP をサポートしません。
+ </div></div></div><div class="para">
+ A clone interface configuration file should use the following naming convention: <code class="filename">ifcfg-<em class="replaceable"><code>if-name</code></em>-<em class="replaceable"><code>clone-name</code></em></code>. While an alias file allows multiple addresses for an existing interface, a clone file is used to specify additional options for an interface. For example, a standard DHCP Ethernet interface called <code class="systemitem">eth0</code>, may look similar to this:
+ </div><pre class="programlisting">DEVICE=eth0
+ONBOOT=yes
+BOOTPROTO=dhcp</pre><div class="para">
+ Since the default value for the <code class="option">USERCTL</code> directive is <code class="literal">no</code> if it is not specified, users cannot bring this interface up and down. To give users the ability to control the interface, create a clone by copying <code class="filename">ifcfg-eth0</code> to <code class="filename">ifcfg-eth0-user</code> and add the following line to <code class="filename">ifcfg-eth0-user</code>:
+ </div><pre class="programlisting">USERCTL=yes</pre><div class="para">
+ This way a user can bring up the <code class="systemitem">eth0</code> interface using the <code class="command">/sbin/ifup eth0-user</code> command because the configuration options from <code class="filename">ifcfg-eth0</code> and <code class="filename">ifcfg-eth0-user</code> are combined. While this is a very basic example, this method can be used with a variety of options and interfaces.
+ </div><div class="para">
+ It is no longer possible to create alias and clone interface configuration files using a graphical tool. However, as explained at the beginning of this section, it is no longer necessary to use this method as it is now possible to directly assign multiple IP address to the same interface. For new installations, users should select the <span class="guilabel"><strong>Manual</strong></span> method on the IPv4 or IPv6 tab in <span class="application"><strong>NetworkManager</strong></span> to assign multiple IP address to the same interface. For more information on using this tool, refer to <a class="xref" href="ch-NetworkManager.html">6章<em>NetworkManager</em></a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html"><strong>戻る</strong>7.2.4. Setting up 802.1q VLAN tagging</a></li><li class="up"><a accesskey="u" href="#"><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-networkscripts-interfaces-ppp0.html"><strong>次へ</strong>7.2.6. ダイヤルアップ インターフェース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-chan.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-chan.html
new file mode 100644
index 0000000..a4e9bf2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-chan.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-networkscripts-interfaces.html" title="7.2. インターフェース設定ファイル" /><link rel="prev" href="s1-networkscripts-interfaces.html" title="7.2. インターフェース設定ファイル" /><link rel="next" href="s2-networkscripts-interfaces_network-bridge.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 acce
sskey="p" href="s1-networkscripts-interfaces.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces_network-bridge.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-networkscripts-interfaces-chan"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. チャンネル・ボンディング・インターフェース</h3></div></div></div><a id="idm69116368" class="indexterm"></a><a id="idm69114512" class="indexterm"></a><div class="para">
+ Fedora は管理者が <code class="filename">bonding</code> カーネルモジュールおよび<em class="firstterm">チャネルボンディングインターフェース</em>と呼ばれる特別なネットワークインターフェースを使用して単一チャネルの中に複数のネットワークインターフェースを一緒にバインドできます。チャネルボンディングは、同時に帯域を増加させて冗長性を提供する、2つ以上のネットワークインターフェースを1つとして動作させることができます。
+ </div><div class="para">
+ To create a channel bonding interface, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file can be identical to whatever type of interface is getting bonded, such as an Ethernet interface. The only difference is that the <code class="option">DEVICE</code> directive is <code class="option">bond<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface.
+ </div><div class="para">
+ 以下は、チャンネル ボンディング設定ファイルの例です。
+ </div><div class="example" id="ex-Sample_ifcfg-bond0_interface_configuration_file"><h6>例7.1 ifcfg-bond0 インターフェース設定ファイルの例</h6><div class="example-contents"><pre class="programlisting">DEVICE=bond0
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+ONBOOT=yes
+BOOTPROTO=none
+USERCTL=no
+BONDING_OPTS="<em class="replaceable"><code>スペースで区切ってボンディングのパラメーター</code></em>"</pre></div></div><br class="example-break" /><div class="para">
+ After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the <code class="option">MASTER</code> and <code class="option">SLAVE</code> directives to their configuration files. The configuration files for each of the channel-bonded interfaces can be nearly identical.
+ </div><div class="para">
+ For example, if two Ethernet interfaces are being channel bonded, both <code class="systemitem">eth0</code> and <code class="systemitem">eth1</code> may look like the following example:
+ </div><pre class="programlisting">DEVICE=eth<em class="replaceable"><code>N</code></em>
+BOOTPROTO=none
+ONBOOT=yes
+MASTER=bond0
+SLAVE=yes
+USERCTL=no</pre><div class="para">
+ この例では、<em class="replaceable"><code>N</code></em> をインターフェースの数値に置き換えます。
+ </div><div class="para">
+ For a channel bonding interface to be valid, the kernel module must be loaded. To ensure that the module is loaded when the channel bonding interface is brought up, create a new file as root named <code class="filename"><em class="replaceable"><code>bonding</code></em>.conf</code> in the <code class="filename">/etc/modprobe.d/</code> directory. Note that you can name this file anything you like as long as it ends with a <code class="filename">.conf</code> extension. Insert the following line in this new file:
+ </div><pre class="programlisting">alias bond<em class="replaceable"><code>N</code></em> bonding</pre><div class="para">
+ Replace <em class="replaceable"><code>N</code></em> with the interface number, such as <code class="literal">0</code>. For each configured channel bonding interface, there must be a corresponding entry in your new <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code> file.
+ </div><div class="important"><div class="admonition_header"><h2>ifcfg-bondN ファイルにすべてのボンディングモジュールパラメーターを書きます</h2></div><div class="admonition"><div class="para">
+ Parameters for the bonding kernel module must be specified as a space-separated list in the <code class="option">BONDING_OPTS="<em class="replaceable"><code>bonding parameters</code></em>"</code> directive in the <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code> interface file. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file. For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to <a class="xref" href="sec-Using_Channel_Bonding.html">「Using Channel Bonding」</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-interfaces.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="s2-networkscripts-interfaces_network-bridge.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/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-other.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-other.html
new file mode 100644
index 0000000..b74e53e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-other.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>7.2.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-networkscripts-interfaces.html" title="7.2. インターフェース設定ファイル" /><link rel="prev" href="s2-networkscripts-interfaces-ppp0.html" title="7.2.6. ダイヤルアップ インターフェース" /><link rel="next" href="s1-networkscripts-control.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="s2-networkscripts-interfaces-ppp0.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-control.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-networkscripts-interfaces-other"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.7. 他のインターフェース</h3></div></div></div><div class="para">
+ 他の一般的なインターフェイス設定ファイルは次の項目を含みます：
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-lo</code></span></dt><dd><div class="para">
+ ローカルの <em class="firstterm">ループバック インターフェイス</em> はよくテストで 使用されるだけでなく、同じシステムを指定し直す IP アドレスを必要とするさまざまなアプリケーションでも使用されます。ループバックデバイスに送信されたデータはすぐにホストのネットワーク層に戻されます。
+ </div><div class="warning"><div class="admonition_header"><h2>ifrcfg-lo スクリプトは手動で編集しません</h2></div><div class="admonition"><div class="para">
+ ループバックインターフェースのスクリプト <code class="filename">/etc/sysconfig/network-scripts/ifcfg-lo</code> は、手動で編集すべきではありません。そうすると、システムが正しく動作しなくなる可能性がありません。
+ </div></div></div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-irlan0</code></span></dt><dd><div class="para">
+ <em class="firstterm">赤外線インターフェース</em> によって、ラップトップとプリンタなどデバイス間の情報を赤外線リンク上で流すことができます。これは、通常ピアツーピア接続で可能という事以外はイーサネットと同じような方法で動作します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-plip0</code></span></dt><dd><div class="para">
+ A <em class="firstterm">Parallel Line Interface Protocol</em> (<acronym class="acronym">PLIP</acronym>) connection works much the same way as an Ethernet device, except that it utilizes a parallel port.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-ppp0.html"><strong>戻る</strong>7.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-networkscripts-control.html"><strong>次へ</strong>7.3. インターフェース制御スクリプト</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-ppp0.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-ppp0.html
new file mode 100644
index 0000000..cd65c44
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces-ppp0.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>7.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-networkscripts-interfaces.html" title="7.2. インターフェース設定ファイル" /><link rel="prev" href="s2-networkscripts-interfaces-alias.html" title="7.2.5. エイリアス ファイルとクローン ファイル" /><link rel="next" href="s2-networkscripts-interfaces-other.html" title="7.2.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="prev
ious"><a accesskey="p" href="s2-networkscripts-interfaces-alias.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-other.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-networkscripts-interfaces-ppp0"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.6. ダイヤルアップ インターフェース</h3></div></div></div><a id="idm47310960" class="indexterm"></a><div class="para">
+ ダイヤルアップ接続を通してインターネットに接続する場合、インターフェース用に設定ファイルが必要です。
+ </div><div class="para">
+ PPP インターフェイス ファイルは、以下の形式を使用して名付けられます:
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-ppp<em class="replaceable"><code>X</code></em> </code></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>X</code></em> は特定のインターフェースに対応する一意な番号です。
+ </div></dd></dl></div>
+
+ </div><div class="para">
+ ダイヤルアップアカウントを作成するために、<code class="command">wvdial</code>、<span class="application"><strong>ネットワーク管理ツール</strong></span> または <span class="application"><strong>Kppp</strong></span> を使用するとき、PPP インターフェース設定ファイルが自動的に作成されます。手動でこのファイルを作成および編集することもできます。
+ </div><div class="para">
+ 以下は一般的な <code class="filename">ifcfg-ppp0</code> ファイルです:
+ </div><pre class="programlisting">DEVICE=ppp0
+NAME=test
+WVDIALSECT=test
+MODEMPORT=/dev/modem
+LINESPEED=115200
+PAPNAME=test
+USERCTL=true
+ONBOOT=no
+PERSIST=no
+DEFROUTE=yes
+PEERDNS=yes
+DEMAND=no
+IDLETIMEOUT=600
+</pre><div class="para">
+ <em class="firstterm">Serial Line Internet Protocol </em> (<acronym class="acronym">SLIP</acronym>) is another dialup interface, although it is used less frequently. SLIP files have interface configuration file names such as <code class="filename">ifcfg-sl0</code>.
+ </div><div class="para">
+ これらのファイルで使用できる他のオプションを以下に示します：
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">DEFROUTE</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このインターフェースをデフォルトルートとして設定します。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — このインターフェースをデフォルトルートとして設定しません。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">DEMAND</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — このインターフェースは <code class="command">pppd</code> が使用しようとするときに接続を初期化できます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — 接続はこのインターフェースに対して手動で確立する必要があります。
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">IDLETIMEOUT</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>value</code></em> is the number of seconds of idle activity before the interface disconnects itself.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">INITSTRING</code>=<em class="replaceable"><code>string</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>string</code></em> is the initialization string passed to the modem device. This option is primarily used in conjunction with SLIP interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">LINESPEED</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>value</code></em> is the baud rate of the device. Possible standard values include <code class="literal">57600</code>, <code class="literal">38400</code>, <code class="literal">19200</code>, and <code class="literal">9600</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">MODEMPORT</code>=<em class="replaceable"><code>device</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>device</code></em> is the name of the serial device that is used to establish the connection for the interface.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">MTU</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>value</code></em> is the <em class="firstterm">Maximum Transfer Unit</em> (<acronym class="acronym">MTU</acronym>) setting for the interface. The MTU refers to the largest number of bytes of data a frame can carry, not counting its header information. In some dialup situations, setting this to a value of <code class="literal">576</code> results in fewer packets dropped and a slight improvement to the throughput for a connection.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">NAME</code>=<em class="replaceable"><code>name</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>name</code></em> is the reference to the title given to a collection of dialup connection configurations.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">PAPNAME</code>=<em class="replaceable"><code>name</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>name</code></em> is the username given during the <em class="firstterm">Password Authentication Protocol</em> (<acronym class="acronym">PAP</acronym>) exchange that occurs to allow connections to a remote system.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">PERSIST</code>=<em class="replaceable"><code>answer</code></em></span></dt><dd><div class="para">
+ ここで <em class="replaceable"><code>answer</code></em> は次のいずれかです:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — This interface should be kept active at all times, even if deactivated after a modem hang up.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — This interface should not be kept active at all times.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="option">REMIP</code>=<em class="replaceable"><code>address</code></em></span></dt><dd><div class="para">
+ where <em class="replaceable"><code>address</code></em> is the IP address of the remote system. This is usually left unspecified.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">WVDIALSECT</code>=<em class="replaceable"><code>name</code></em> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code>name</code></em> associates this interface with a dialer configuration in <code class="filename">/etc/wvdial.conf</code>. This file contains the phone number to be dialed and other important information for the interface.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-alias.html"><strong>戻る</strong>7.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-networkscripts-interfaces-other.html"><strong>次へ</strong>7.2.7. 他のインターフェース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces_802.1q-vlan-tagging.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces_802.1q-vlan-tagging.html
new file mode 100644
index 0000000..4c02eff
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces_802.1q-vlan-tagging.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>7.2.4. Setting up 802.1q VLAN tagging</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-networkscripts-interfaces.html" title="7.2. インターフェース設定ファイル" /><link rel="prev" href="s2-networkscripts-interfaces_network-bridge.html" title="7.2.3. ネットワークブリッジ" /><link rel="next" href="s2-networkscripts-interfaces-alias.html" title="7.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 cl
ass="previous"><a accesskey="p" href="s2-networkscripts-interfaces_network-bridge.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-alias.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-networkscripts-interfaces_802.1q-vlan-tagging"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.4. Setting up 802.1q VLAN tagging</h3></div></div></div><a id="idm58480272" class="indexterm"></a><a id="idm58478352" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Ensure that the module is loaded by entering the following command:
+ </div><pre class="screen"><code class="command"> lsmod | grep 8021q</code></pre></li><li class="step"><div class="para">
+ If the module is not loaded, load it with the following command:
+ </div><pre class="screen"><code class="command">modprobe 8021q</code></pre></li><li class="step"><div class="para">
+ Configure your physical interface in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth<em class="replaceable"><code>X</code></em></code>, where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface, as follows:
+ </div><pre class="screen">DEVICE=ethX
+TYPE=Ethernet
+BOOTPROTO=none
+ONBOOT=yes</pre></li><li class="step"><div class="para">
+ Configure the VLAN interface configuration in <code class="filename">/etc/sysconfig/network-scripts</code>. The configuration filename should be the physical interface plus a <code class="literal">.</code> character plus the VLAN ID number. For example, if the VLAN ID is 192, and the physical interface is <code class="systemitem">eth0</code>, then the configuration filename should be <code class="filename">ifcfg-eth0.192</code>:
+ </div><pre class="screen">DEVICE=ethX.192
+BOOTPROTO=static
+ONBOOT=yes
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+USERCTL=no
+NETWORK=192.168.1.0
+VLAN=yes</pre><div class="para">
+ If there is a need to configure a second VLAN, with for example, VLAN ID 193, on the same interface, <code class="systemitem">eth0</code> , add a new file with the name <code class="filename">eth0.193</code> with the VLAN configuration details.
+ </div></li><li class="step"><div class="para">
+ Restart the networking service, in order for the changes to take effect by running as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command"> systemctl restart network.service </code></pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces_network-bridge.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="s2-networkscripts-interfaces-alias.html"><strong>次へ</strong>7.2.5. エイリアス ファイルとクローン ファイル</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces_network-bridge.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces_network-bridge.html
new file mode 100644
index 0000000..9ec0d3a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces_network-bridge.html
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-networkscripts-interfaces.html" title="7.2. インターフェース設定ファイル" /><link rel="prev" href="s2-networkscripts-interfaces-chan.html" title="7.2.2. チャンネル・ボンディング・インターフェース" /><link rel="next" href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html" title="7.2.4. Setting up 802.1q VLAN tagging" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></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="s2-networkscripts-interfaces-chan.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces_802.1q-vlan-tagging.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-networkscripts-interfaces_network-bridge"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. ネットワークブリッジ</h3></div></div></div><a id="idm40109024" class="indexterm"></a><div class="para">
+ A network bridge is a Link Layer device which forwards traffic between networks based on MAC addresses and is therefore also referred to as a Layer 2 device. It makes forwarding decisions based on tables of MAC addresses which it builds by learning what hosts are connected to each network. A software bridge can be used within a Linux host in order to emulate a hardware bridge, for example in virtualization applications for sharing a NIC with one or more virtual NICs. This case will be illustrated here as an example.
+ </div><div class="para">
+ To create a network bridge, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-br<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file is similar to whatever type of interface is getting bridged to, such as an Ethernet interface. The differences in this example are as follows:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="option">DEVICE</code> directive is given an interface name as its argument in the format <code class="option">br<em class="replaceable"><code>N</code></em></code>, where <em class="replaceable"><code>N</code></em> is replaced with the number of the interface.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">TYPE</code> directive is given an argument <code class="option">Bridge</code> or <code class="option">Ethernet</code>. This directive determines the device type and the argument is case sensitive.
+ </div></li><li class="listitem"><div class="para">
+ The bridge interface configuration file now has the IP address and the physical interface has only a MAC address.
+ </div></li><li class="listitem"><div class="para">
+ An extra directive, <code class="option">DELAY=0</code>, is added to prevent the bridge from waiting while it monitors traffic, learns where hosts are located, and builds a table of MAC addresses on which to base its filtering decisions. The default delay of 30 seconds is not needed if no routing loops are possible.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">NM_CONTROLLED=no</code> should be added to the Ethernet interface to prevent <span class="application"><strong>NetworkManager</strong></span> from altering the file. It can also be added to the bridge configuration file in case future versions of <span class="application"><strong>NetworkManager</strong></span> support bridge configuration.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The following is a sample bridge interface configuration file using a static IP address:
+ </div><div class="example" id="ex-Sample_ifcfg-br0_interface_configuration_file"><h6>例7.2 ifcfg-br0 インターフェース設定ファイルの例</h6><div class="example-contents"><pre class="programlisting">DEVICE=br0
+TYPE=Bridge
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+ONBOOT=yes
+BOOTPROTO=static
+NM_CONTROLLED=no
+DELAY=0</pre></div></div><br class="example-break" /><div class="para">
+ To complete the bridge another interface is created, or an existing interface is modified, and pointed to the bridge interface. The following is a sample Ethernet interface configuration file pointing to a bridge interface. Configure your physical interface in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth<em class="replaceable"><code>X</code></em></code>, where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface, as follows:
+ </div><div class="example" id="ex-Sample_ifcfg-eth0_interface_configuration_file"><h6>例7.3 ifcfg-ethX インターフェース設定ファイルの例</h6><div class="example-contents"><pre class="programlisting">DEVICE=ethX
+TYPE=Ethernet
+HWADDR=AA:BB:CC:DD:EE:FF
+BOOTPROTO=none
+ONBOOT=yes
+NM_CONTROLLED=no
+BRIDGE=br0</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ For the <code class="option">DEVICE</code> directive, almost any interface name could be used as it does not determine the device type. Other commonly used names include <code class="option">tap</code>, <code class="option">dummy</code> and <code class="option">bond</code> for example. <code class="option">TYPE=Ethernet</code> is not strictly required. If the <code class="option">TYPE</code> directive is not set, the device is treated as an Ethernet device (unless it's name explicitly matches a different interface configuration file.)
+ </div></div></div><div class="para">
+ You can refer to <a class="xref" href="s1-networkscripts-interfaces.html">「インターフェース設定ファイル」</a> for a review of the directives and options used in network interface config files.
+ </div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
+ If you are configuring bridging on a remote host, and you are connected to that host over the physical NIC you are configuring, please consider the implications of losing connectivity before proceeding. You will lose connectivity when restarting the service and may not be able to regain connectivity if any errors have been made. Console, or out-of-band access is advised.
+ </div></div></div><div class="para">
+ Restart the networking service, in order for the changes to take effect by running as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command"> systemctl restart network.service </code></pre><div class="para">
+ An example of a network bridge formed from two or more bonded Ethernet interfaces will now be given as this is another common application in a virtualization environment. If you are not very familiar with the configuration files for bonded interfaces then please refer to <a class="xref" href="s2-networkscripts-interfaces-chan.html">「チャンネル・ボンディング・インターフェース」</a>
+ </div><div class="para">
+ Create or edit two or more Ethernet interface configuration files, which are to be bonded, as follows:
+<pre class="programlisting">DEVICE=ethX
+TYPE=Ethernet
+USERCTL=no
+SLAVE=yes
+MASTER=bond0
+BOOTPROTO=none
+HWADDR=AA:BB:CC:DD:EE:FF
+NM_CONTROLLED=no</pre>
+
+ </div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ Using <code class="systemitem">eth<em class="replaceable"><code>X</code></em></code> as the interface name is common practice but almost any name could be used. Names such as <code class="option">tap</code>, <code class="option">dummy</code> and <code class="option">bond</code> are commonly used.
+ </div></div></div><div class="para">
+ Create or edit one interface configuration file, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond0</code>, as follows:
+<pre class="programlisting">DEVICE=bond0
+ONBOOT=yes
+BONDING_OPTS='mode=1 miimon=100'
+BRIDGE=brbond0
+NM_CONTROLLED=no</pre>
+ For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to <a class="xref" href="sec-Using_Channel_Bonding.html">「Using Channel Bonding」</a>.
+ </div><div class="para">
+ Create or edit one interface configuration file, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-brbond0</code>, as follows:
+<pre class="programlisting">DEVICE=brbond0
+ONBOOT=yes
+TYPE=Bridge
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+NM_CONTROLLED=no</pre>
+
+ </div><div class="figure" id="exam-Network_Interfaces-bridge-with-bond"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Interfaces-bridge-with-bond.png"><img src="images/Network_Interfaces-bridge-with-bond.png" alt="A network bridge consisting of two bonded Ethernet interfaces." /><div class="longdesc"><div class="para">
+ A diagram of two Ethernet interfaces on the left feeding into a virtual interface labeled <code class="literal">bond 0</code>. This in turn leads to a virtual interface called <code class="literal">BR Bond 0</code> on the right. From there a path leads to a virtual network below.
+ </div></div></div></div><h6>図7.1 A network bridge consisting of two bonded Ethernet interfaces.</h6></div><br class="figure-break" /><div class="para">
+ We now have two or more interface configuration files with the <code class="option">MASTER=bond0</code> directive. These point to the configuration file named <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond0</code>, which contains the <code class="option">DEVICE=bond0</code> directive. This <code class="filename">ifcfg-bond0</code> in turn points to the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-brbond0</code> configuration file, which contains the IP address, and acts as an interface to the virtual networks inside the host.
+ </div><div class="para">
+ Restart the networking service, in order for the changes to take effect by running as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code class="command"> systemctl restart network.service </code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-chan.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="s2-networkscripts-interfaces_802.1q-vlan-tagging.html"><strong>次へ</strong>7.2.4. Setting up 802.1q VLAN tagging</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-openssh-useful-websites.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-openssh-useful-websites.html
new file mode 100644
index 0000000..af6c619
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-openssh-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>10.5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-openssh-additional-resources.html" title="10.5. 追加のリソース" /><link rel="prev" href="s1-openssh-additional-resources.html" title="10.5. 追加のリソース" /><link rel="next" href="part-Servers.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="s1-openssh-additional-resources.html"><strong>戻る</stron
g></a></li><li class="next"><a accesskey="n" href="part-Servers.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-openssh-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.5.2. 役に立つ Web サイト</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.openssh.com/">http://www.openssh.com/</a></span></dt><dd><div class="para">
+ さらなるドキュメント、よくある質問、メーリングリストへのリンク、バグ報告、および他の有用なリソースがある OpenSSH のホームページです。
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.openssl.org/">http://www.openssl.org/</a></span></dt><dd><div class="para">
+ さらなるドキュメント、よくある質問、メーリングリストへのリンク、および他の有用なリソースがある OpenSSL のホームページです。
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.freesshd.com/">http://www.freesshd.com/</a></span></dt><dd><div class="para">
+ SSH サーバーのもう一つの実装です。
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-openssh-additional-resources.html"><strong>戻る</strong>10.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="part-Servers.html"><strong>次へ</strong>パート V. サーバー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-events.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-events.html
new file mode 100644
index 0000000..c3ad12a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-events.html
@@ -0,0 +1,225 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-oprofile-configuring.html" title="20.2. Configuring OProfile" /><link rel="prev" href="s1-oprofile-configuring.html" title="20.2. Configuring OProfile" /><link rel="next" href="s2-oprofile-starting-separate.html" title="20.2.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.2.2. Setting Events to Monitor</h3></div></div></div><a id="idm83328976" 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.2「OProfile Processors and Counters」</a>, the number of counters available depends on the processor.
+ </div><div class="table" id="tb-oprofile-processors"><h6>表20.2 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 Athlon
+ </td><td class="">
+ i386/athlon
+ </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="">
+ 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 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 Pentium 4 (non-hyper-threaded)
+ </td><td class="">
+ i386/p4
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Pentium 4 (hyper-threaded)
+ </td><td class="">
+ i386/p4-ht
+ </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="">
+ 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.2「OProfile Processors and Counters」</a> to verify that the correct processor type was detected and to determine the number of events that can be monitored simultaneously. <code class="computeroutput">timer</code> is used as the processor type if the processor does not have supported performance monitoring hardware.
+ </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 counter 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.3「Default Events」</a>.
+ </div><div class="table" id="tb-oprofile-default-events"><h6>表20.3 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="">
+ 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 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="">
+ 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="idm21091408" class="indexterm"></a><a id="idm21089296" class="indexterm"></a><pre class="screen">~]# <code class="command">ophelp</code></pre><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, refer to <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.2.2.1. Sampling Rate</h4></div></div></div><a id="idm48791472" 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 whatever the jiffy rate is 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 as if it is 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.2.2.2. Unit Masks</h4></div></div></div><a id="idm54665056" 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></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-configuring.html"><strong>戻る</strong>20.2. Configuring 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-oprofile-starting-separate.html"><strong>次へ</strong>20.2.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/17/html/System_Administrators_Guide/s2-oprofile-module-output.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-module-output.html
new file mode 100644
index 0000000..876eeee
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="20.5. Analyzing the Data" /><link rel="prev" href="s2-oprofile-reading-opreport-single.html" title="20.5.2. Using opreport on a Single Executable" /><link rel="next" href="s2-oprofile-reading-opannotate.html" title="20.5.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.5.3. Getting more detailed output on the modules</h3></div></div></div><a id="idm21742656" class="indexterm"></a><a id="idm30503104" 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 have 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 sample 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 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.5.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.5.4. Using opannotate </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html
new file mode 100644
index 0000000..f135080
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="20.5. Analyzing the Data" /><link rel="prev" href="s2-oprofile-module-output.html" title="20.5.3. Getting more detailed output on the modules" /><link rel="next" href="s1-oprofile-dev-oprofile.html" title="20.6. Understanding /dev/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-oprofile-module-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.5.4. Using <code class="command">opannotate</code> </h3></div></div></div><a id="idm49187088" class="indexterm"></a><a id="idm49184864" 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 files generated 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. By default, Fedora <span class="package">debuginfo</span> packages are not installed together with their corresponding packages, which contain the executable, so that you have to obtain and install the <span class="package">debuginfo</span> packages 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">
+ The directory containing the source code and the executable to be analyzed must be specified. Refer to the <code class="command">opannotate</code> man 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.5.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.6. Understanding /dev/oprofile/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html
new file mode 100644
index 0000000..5f9fc08
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="20.5. Analyzing the Data" /><link rel="prev" href="s1-oprofile-analyzing-data.html" title="20.5. Analyzing the Data" /><link rel="next" href="s2-oprofile-module-output.html" title="20.5.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.5.2. Using opreport on a Single Executable</h3></div></div></div><a id="idm60252544" class="indexterm"></a><a id="idm60249840" class="indexterm"></a><div class="para">
+ To retrieve more detailed profiled information about a specific executable, use <code class="command">opreport</code>:
+ </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">
+ <em class="replaceable"><code>executable</code></em> must be the full path to the executable to be analyzed. <em class="replaceable"><code>mode</code></em> must be one of the following:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">-l</code></span></dt><dd><div class="para">
+ List sample data by symbols. For example, the following is part of the output from running the command <code class="command">opreport -l /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ </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@@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, the following output is from the command <code class="command">opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ </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">
+ List sample data by symbols with more detail than <code class="option">-l</code>. For example, the following output is from the command <code class="command">opreport -l -d __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ </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">-x</code> <em class="replaceable"><code>symbol-name</code></em> </span></dt><dd><div class="para">
+ Exclude the comma-separated list of symbols from the output.
+ </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">
+ Specify the full path to the session or a directory relative to the <code class="filename">/var/lib/oprofile/samples/</code> directory.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-analyzing-data.html"><strong>戻る</strong>20.5. 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.5.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/17/html/System_Administrators_Guide/s2-oprofile-starting-separate.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-starting-separate.html
new file mode 100644
index 0000000..dc24fb6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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.2.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-oprofile-configuring.html" title="20.2. Configuring OProfile" /><link rel="prev" href="s2-oprofile-events.html" title="20.2.2. Setting Events to Monitor" /><link rel="next" href="s1-oprofile-starting.html" title="20.3. Starting and Stopping 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-oprofile-events.html"><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.2.3. Separating Kernel and User-space Profiles</h3></div></div></div><a id="idm47066480" 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>:<em class="replaceable"><code>kernel</code></em>: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>:<em class="replaceable"><code>kernel</code></em>: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">
+ <em class="replaceable"><code>choice</code></em> 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.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-starting.html"><strong>次へ</strong>20.3. Starting and Stopping OProfile</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-useful-websites.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-useful-websites.html
new file mode 100644
index 0000000..7148799
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-oprofile-useful-websites.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.11.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-oprofile-additional-resources.html" title="20.11. 追加のリソース" /><link rel="prev" href="s1-oprofile-additional-resources.html" title="20.11. 追加のリソース" /><link rel="next" href="part-Kernel_Module_and_Driver_Configuration.html" title="パート VII. カーネル、モジュールおよびドライバーの設定" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="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="s1-oprofile-additional-resources.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="s2-oprofile-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.11.2. 役に立つ Web サイト</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://oprofile.sourceforge.net/">http://oprofile.sourceforge.net/</a> — Contains the latest documentation, mailing lists, IRC channels, and more.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/SystemTap_Beginners_Guide/index.html">SystemTap 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-additional-resources.html"><strong>戻る</strong>20.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="part-Kernel_Module_and_Driver_Configuration.html"><strong>次へ</strong>パート VII. カーネル、モジュールおよびドライバーの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-cmdline.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-cmdline.html
new file mode 100644
index 0000000..25ef90e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-cmdline.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>E.2.2. /proc/cmdline</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="next" href="s2-proc-cpuinfo.html" title="E.2.3. /proc/cpuinfo" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-topfiles.html"><strong>戻る</strong></a><
/li><li class="next"><a accesskey="n" href="s2-proc-cpuinfo.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.2. /proc/cmdline </h3></div></div></div><a id="idm73354704" class="indexterm"></a><div class="para">
+ This file shows the parameters passed to the kernel at the time it is started. A sample <code class="filename">/proc/cmdline</code> file looks like the following:
+ </div><pre class="screen">
+ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3
+</pre><div class="para">
+ This tells us that the kernel is mounted read-only (signified by <code class="computeroutput">(ro)</code>), located on the first logical volume (<code class="computeroutput">LogVol00</code>) of the first volume group (<code class="computeroutput">/dev/VolGroup00</code>). <code class="computeroutput">LogVol00</code> is the equivalent of a disk partition in a non-LVM system (Logical Volume Management), just as <code class="computeroutput">/dev/VolGroup00</code> is similar in concept to <code class="filename">/dev/hda1</code>, but much more extensible.
+ </div><div class="para">
+ For more information on LVM used in Fedora, refer to <a href="http://www.tldp.org/HOWTO/LVM-HOWTO/index.html">http://www.tldp.org/HOWTO/LVM-HOWTO/index.html</a>.
+ </div><div class="para">
+ Next, <code class="computeroutput">rhgb</code> signals that the <code class="filename">rhgb</code> package has been installed, and graphical booting is supported, assuming <code class="filename">/etc/inittab</code> shows a default runlevel set to <code class="command">id:5:initdefault:</code>.
+ </div><div class="para">
+ Finally, <code class="computeroutput">quiet</code> indicates all verbose kernel messages are suppressed at boot time.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-topfiles.html"><strong>戻る</strong>E.2. Top-level Files within the proc File 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="s2-proc-cpuinfo.html"><strong>次へ</strong>E.2.3. /proc/cpuinfo </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-cpuinfo.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-cpuinfo.html
new file mode 100644
index 0000000..f578bd0
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-cpuinfo.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>E.2.3. /proc/cpuinfo</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-cmdline.html" title="E.2.2. /proc/cmdline" /><link rel="next" href="s2-proc-crypto.html" title="E.2.4. /proc/crypto" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-cmdline.html"><strong>戻る</strong></a></li><li class="next"><a accesske
y="n" href="s2-proc-crypto.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-cpuinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.3. /proc/cpuinfo </h3></div></div></div><a id="idm50333568" class="indexterm"></a><div class="para">
+ This virtual file identifies the type of processor used by your system. The following is an example of the output typical of <code class="filename">/proc/cpuinfo</code>:
+ </div><pre class="screen">
+processor : 0
+vendor_id : GenuineIntel
+cpu family : 15
+model : 2
+model name : Intel(R) Xeon(TM) CPU 2.40GHz
+stepping : 7 cpu
+MHz : 2392.371
+cache size : 512 KB
+physical id : 0
+siblings : 2
+runqueue : 0
+fdiv_bug : no
+hlt_bug : no
+f00f_bug : no
+coma_bug : no
+fpu : yes
+fpu_exception : yes
+cpuid level : 2
+wp : yes
+flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
+bogomips : 4771.02
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">processor</code> — Provides each processor with an identifying number. On systems that have one processor, only a <code class="computeroutput">0</code> is present.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu family</code> — Authoritatively identifies the type of processor in the system. For an Intel-based system, place the number in front of "86" to determine the value. This is particularly helpful for those attempting to identify the architecture of an older system such as a 586, 486, or 386. Because some RPM packages are compiled for each of these particular architectures, this value also helps users determine which packages to install.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">model name</code> — Displays the common name of the processor, including its project name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu MHz</code> — Shows the precise speed in megahertz for the processor to the thousandths decimal place.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cache size</code> — Displays the amount of level 2 memory cache available to the processor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">siblings</code> — Displays the number of sibling CPUs on the same physical CPU for architectures which use hyper-threading.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">flags</code> — Defines a number of different qualities about the processor, such as the presence of a floating point unit (FPU) and the ability to process MMX instructions.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-cmdline.html"><strong>戻る</strong>E.2.2. /proc/cmdline </a></li><li class="up"><a accesskey="u" href="#"><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-proc-crypto.html"><strong>次へ</strong>E.2.4. /proc/crypto </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-crypto.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-crypto.html
new file mode 100644
index 0000000..6692ea2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-crypto.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>E.2.4. /proc/crypto</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-cpuinfo.html" title="E.2.3. /proc/cpuinfo" /><link rel="next" href="s2-proc-devices.html" title="E.2.5. /proc/devices" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-cpuinfo.html"><strong>戻る</strong></a></li><li class="next"><a access
key="n" href="s2-proc-devices.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-crypto"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.4. /proc/crypto </h3></div></div></div><a id="idm53261856" class="indexterm"></a><div class="para">
+ This file lists all installed cryptographic ciphers used by the Linux kernel, including additional details for each. A sample <code class="filename">/proc/crypto</code> file looks like the following:
+ </div><pre class="screen">
+name : sha1
+module : kernel
+type : digest
+blocksize : 64
+digestsize : 20
+name : md5
+module : md5
+type : digest
+blocksize : 64
+digestsize : 16
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-cpuinfo.html"><strong>戻る</strong>E.2.3. /proc/cpuinfo </a></li><li class="up"><a accesskey="u" href="#"><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-proc-devices.html"><strong>次へ</strong>E.2.5. /proc/devices </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-devices.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-devices.html
new file mode 100644
index 0000000..4b8731d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-devices.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>E.2.5. /proc/devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-crypto.html" title="E.2.4. /proc/crypto" /><link rel="next" href="s2-proc-dma.html" title="E.2.6. /proc/dma" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-crypto.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" hre
f="s2-proc-dma.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.5. /proc/devices </h3></div></div></div><a id="idm67672416" class="indexterm"></a><a id="idm67669344" class="indexterm"></a><a id="idm67666272" class="indexterm"></a><a id="idm67664640" class="indexterm"></a><a id="idm41446640" class="indexterm"></a><a id="idm41444528" class="indexterm"></a><div class="para">
+ This file displays the various character and block devices currently configured (not including devices whose modules are not loaded). Below is a sample output from this file:
+ </div><pre class="screen">
+Character devices:
+ 1 mem
+ 4 /dev/vc/0
+ 4 tty
+ 4 ttyS
+ 5 /dev/tty
+ 5 /dev/console
+ 5 /dev/ptmx
+ 7 vcs
+ 10 misc
+ 13 input
+ 29 fb
+ 36 netlink
+ 128 ptm
+ 136 pts
+ 180 usb
+
+Block devices:
+ 1 ramdisk
+ 3 ide0
+ 9 md
+ 22 ide1
+ 253 device-mapper
+ 254 mdp
+</pre><div class="para">
+ The output from <code class="filename">/proc/devices</code> includes the major number and name of the device, and is broken into two major sections: <code class="computeroutput">Character devices</code> and <code class="computeroutput">Block devices</code>.
+ </div><div class="para">
+ <em class="firstterm">Character devices</em> are similar to <em class="firstterm">block devices</em>, except for two basic differences:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Character devices do not require buffering. Block devices have a buffer available, allowing them to order requests before addressing them. This is important for devices designed to store information — such as hard drives — because the ability to order the information before writing it to the device allows it to be placed in a more efficient order.
+ </div></li><li class="listitem"><div class="para">
+ Character devices send data with no preconfigured size. Block devices can send and receive information in blocks of a size configured per device.
+ </div></li></ol></div><div class="para">
+ For more information about devices refer to the following installed documentation:
+ </div><pre class="screen">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/devices.txt</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-crypto.html"><strong>戻る</strong>E.2.4. /proc/crypto </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dma.html"><strong>次へ</strong>E.2.6. /proc/dma </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-bus.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-bus.html
new file mode 100644
index 0000000..a9b4234
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-bus.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>E.3.2. /proc/bus/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="next" href="s2-proc-pci.html" title="E.3.3. /proc/bus/pci" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-directories.html"><strong>戻る</strong></a></li><li class="next"><a accessk
ey="n" href="s2-proc-pci.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dir-bus"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.2. /proc/bus/ </h3></div></div></div><a id="idm64188512" class="indexterm"></a><div class="para">
+ This directory contains information specific to the various buses available on the system. For example, on a standard system containing PCI and USB buses, current data on each of these buses is available within a subdirectory within <code class="filename">/proc/bus/</code> by the same name, such as <code class="filename">/proc/bus/pci/</code>.
+ </div><div class="para">
+ The subdirectories and files available within <code class="filename">/proc/bus/</code> vary depending on the devices connected to the system. However, each bus type has at least one directory. Within these bus directories are normally at least one subdirectory with a numerical name, such as <code class="filename">001</code>, which contain binary files.
+ </div><div class="para">
+ For example, the <code class="filename">/proc/bus/usb/</code> subdirectory contains files that track the various devices on any USB buses, as well as the drivers required for them. The following is a sample listing of a <code class="filename">/proc/bus/usb/</code> directory:
+ </div><pre class="screen">
+total 0 dr-xr-xr-x 1 root root 0 May 3 16:25 001
+-r--r--r-- 1 root root 0 May 3 16:25 devices
+-r--r--r-- 1 root root 0 May 3 16:25 drivers
+</pre><div class="para">
+ The <code class="filename">/proc/bus/usb/001/</code> directory contains all devices on the first USB bus and the <code class="filename">devices</code> file identifies the USB root hub on the motherboard.
+ </div><div class="para">
+ The following is a example of a <code class="filename">/proc/bus/usb/devices</code> file:
+ </div><pre class="screen">
+T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
+B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
+D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
+P: Vendor=0000 ProdID=0000 Rev= 0.00
+S: Product=USB UHCI Root Hub
+S: SerialNumber=d400
+C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
+I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
+E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-directories.html"><strong>戻る</strong>E.3. Directories within /proc/</a></li><li class="up"><a accesskey="u" href="#"><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-proc-pci.html"><strong>次へ</strong>E.3.3. /proc/bus/pci </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-driver.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-driver.html
new file mode 100644
index 0000000..ee94a46
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-driver.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>E.3.4. /proc/driver/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-pci.html" title="E.3.3. /proc/bus/pci" /><link rel="next" href="s2-proc-dir-fs.html" title="E.3.5. /proc/fs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-pci.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-fs.
html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dir-driver"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.4. /proc/driver/ </h3></div></div></div><a id="idm48320912" class="indexterm"></a><div class="para">
+ This directory contains information for specific drivers in use by the kernel.
+ </div><div class="para">
+ A common file found here is <code class="filename">rtc</code> which provides output from the driver for the system's <em class="firstterm">Real Time Clock (RTC)</em>, the device that keeps the time while the system is switched off. Sample output from <code class="filename">/proc/driver/rtc</code> looks like the following:
+ </div><pre class="screen">
+rtc_time : 16:21:00
+rtc_date : 2004-08-31
+rtc_epoch : 1900
+alarm : 21:16:27
+DST_enable : no
+BCD : yes
+24hr : yes
+square_wave : no
+alarm_IRQ : no
+update_IRQ : no
+periodic_IRQ : no
+periodic_freq : 1024
+batt_status : okay
+</pre><div class="para">
+ For more information about the RTC, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/rtc.txt</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-pci.html"><strong>戻る</strong>E.3.3. /proc/bus/pci </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dir-fs.html"><strong>次へ</strong>E.3.5. /proc/fs </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-fs.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-fs.html
new file mode 100644
index 0000000..81b9d4a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-fs.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>E.3.5. /proc/fs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-driver.html" title="E.3.4. /proc/driver/" /><link rel="next" href="s2-proc-dir-irq.html" title="E.3.6. /proc/irq/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-driver.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href
="s2-proc-dir-irq.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dir-fs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.5. /proc/fs </h3></div></div></div><a id="idm20458512" class="indexterm"></a><div class="para">
+ This directory shows which file systems are exported. If running an NFS server, typing <code class="command">cat /proc/fs/nfsd/exports</code> displays the file systems being shared and the permissions granted for those file systems. For more on file system sharing with NFS, refer to the <em class="citetitle">Network File System (NFS)</em> chapter of the <em class="citetitle">Storage Administration Guide</em>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-driver.html"><strong>戻る</strong>E.3.4. /proc/driver/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dir-irq.html"><strong>次へ</strong>E.3.6. /proc/irq/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-irq.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-irq.html
new file mode 100644
index 0000000..56b19a3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-irq.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>E.3.6. /proc/irq/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-fs.html" title="E.3.5. /proc/fs" /><link rel="next" href="s2-proc-dir-net.html" title="E.3.7. /proc/net/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-fs.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir
-net.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dir-irq"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.6. /proc/irq/ </h3></div></div></div><a id="idm20452144" class="indexterm"></a><div class="para">
+ This directory is used to set IRQ to CPU affinity, which allows the system to connect a particular IRQ to only one CPU. Alternatively, it can exclude a CPU from handling any IRQs.
+ </div><div class="para">
+ Each IRQ has its own directory, allowing for the individual configuration of each IRQ. The <code class="filename">/proc/irq/prof_cpu_mask</code> file is a bitmask that contains the default values for the <code class="filename">smp_affinity</code> file in the IRQ directory. The values in <code class="filename">smp_affinity</code> specify which CPUs handle that particular IRQ.
+ </div><div class="para">
+ For more information about the <code class="filename">/proc/irq/</code> directory, refer to the following installed documentation:
+ </div><pre class="screen">
+/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-fs.html"><strong>戻る</strong>E.3.5. /proc/fs </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dir-net.html"><strong>次へ</strong>E.3.7. /proc/net/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-net.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-net.html
new file mode 100644
index 0000000..9c2ae16
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-net.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>E.3.7. /proc/net/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-irq.html" title="E.3.6. /proc/irq/" /><link rel="next" href="s2-proc-dir-scsi.html" title="E.3.8. /proc/scsi/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-irq.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-pr
oc-dir-scsi.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dir-net"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.7. /proc/net/ </h3></div></div></div><a id="idm30975664" class="indexterm"></a><div class="para">
+ This directory provides a comprehensive look at various networking parameters and statistics. Each directory and virtual file within this directory describes aspects of the system's network configuration. Below is a partial list of the <code class="filename">/proc/net/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">arp</code> — Lists the kernel's ARP table. This file is particularly useful for connecting a hardware address to an IP address on a system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">atm/</code> directory — The files within this directory contain <em class="firstterm">Asynchronous Transfer Mode (ATM)</em> settings and statistics. This directory is primarily used with ATM networking and ADSL cards.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dev</code> — Lists the various network devices configured on the system, complete with transmit and receive statistics. This file displays the number of bytes each interface has sent and received, the number of packets inbound and outbound, the number of errors seen, the number of packets dropped, and more.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dev_mcast</code> — Lists Layer2 multicast groups on which each device is listening.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">igmp</code> — Lists the IP multicast addresses which this system joined.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_conntrack</code> — Lists tracked network connections for machines that are forwarding IP connections.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_tables_names</code> — Lists the types of <code class="command">iptables</code> in use. This file is only present if <code class="command">iptables</code> is active on the system and contains one or more of the following values: <code class="filename">filter</code>, <code class="filename">mangle</code>, or <code class="filename">nat</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_mr_cache</code> — Lists the multicast routing cache.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_mr_vif</code> — Lists multicast virtual interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">netstat</code> — Contains a broad yet detailed collection of networking statistics, including TCP timeouts, SYN cookies sent and received, and much more.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">psched</code> — Lists global packet scheduler parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">raw</code> — Lists raw device statistics.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">route</code> — Lists the kernel's routing table.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rt_cache</code> — Contains the current routing cache.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">snmp</code> — List of Simple Network Management Protocol (SNMP) data for various networking protocols in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sockstat</code> — Provides socket statistics.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp</code> — Contains detailed TCP socket information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tr_rif</code> — Lists the token ring RIF routing table.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">udp</code> — Contains detailed UDP socket information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">unix</code> — Lists UNIX domain sockets currently in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wireless</code> — Lists wireless interface data.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-irq.html"><strong>戻る</strong>E.3.6. /proc/irq/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dir-scsi.html"><strong>次へ</strong>E.3.8. /proc/scsi/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-scsi.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-scsi.html
new file mode 100644
index 0000000..f6930b8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-scsi.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.3.8. /proc/scsi/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-net.html" title="E.3.7. /proc/net/" /><link rel="next" href="s2-proc-dir-sys.html" title="E.3.9. /proc/sys/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-net.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-proc
-dir-sys.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dir-scsi"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.8. /proc/scsi/ </h3></div></div></div><a id="idm59425104" class="indexterm"></a><div class="para">
+ The primary file in this directory is <code class="filename">/proc/scsi/scsi</code>, which contains a list of every recognized SCSI device. From this listing, the type of device, as well as the model name, vendor, SCSI channel and ID data is available.
+ </div><div class="para">
+ For example, if a system contains a SCSI CD-ROM, a tape drive, a hard drive, and a RAID controller, this file looks similar to the following:
+ </div><pre class="screen">
+Attached devices:
+Host: scsi1
+Channel: 00
+Id: 05
+Lun: 00
+Vendor: NEC
+Model: CD-ROM DRIVE:466
+Rev: 1.06
+Type: CD-ROM
+ANSI SCSI revision: 02
+Host: scsi1
+Channel: 00
+Id: 06
+Lun: 00
+Vendor: ARCHIVE
+Model: Python 04106-XXX
+Rev: 7350
+Type: Sequential-Access
+ANSI SCSI revision: 02
+Host: scsi2
+Channel: 00
+Id: 06
+Lun: 00
+Vendor: DELL
+Model: 1x6 U2W SCSI BP
+Rev: 5.35
+Type: Processor
+ANSI SCSI revision: 02
+Host: scsi2
+Channel: 02
+Id: 00
+Lun: 00
+Vendor: MegaRAID
+Model: LD0 RAID5 34556R
+Rev: 1.01
+Type: Direct-Access
+ANSI SCSI revision: 02
+</pre><div class="para">
+ Each SCSI driver used by the system has its own directory within <code class="filename">/proc/scsi/</code>, which contains files specific to each SCSI controller using that driver. From the previous example, <code class="filename">aic7xxx/</code> and <code class="filename">megaraid/</code> directories are present, since two drivers are in use. The files in each of the directories typically contain an I/O address range, IRQ information, and statistics for the SCSI controller using that driver. Each controller can report a different type and amount of information. The Adaptec AIC-7880 Ultra SCSI host adapter's file in this example system produces the following output:
+ </div><pre class="screen">
+Adaptec AIC7xxx driver version: 5.1.20/3.2.4
+Compile Options:
+TCQ Enabled By Default : Disabled
+AIC7XXX_PROC_STATS : Enabled
+AIC7XXX_RESET_DELAY : 5
+Adapter Configuration:
+SCSI Adapter: Adaptec AIC-7880 Ultra SCSI host adapter
+Ultra Narrow Controller PCI MMAPed
+I/O Base: 0xfcffe000
+Adapter SEEPROM Config: SEEPROM found and used.
+Adaptec SCSI BIOS: Enabled
+IRQ: 30
+SCBs: Active 0, Max Active 1, Allocated 15, HW 16, Page 255
+Interrupts: 33726
+BIOS Control Word: 0x18a6
+Adapter Control Word: 0x1c5f
+Extended Translation: Enabled
+Disconnect Enable Flags: 0x00ff
+Ultra Enable Flags: 0x0020
+Tag Queue Enable Flags: 0x0000
+Ordered Queue Tag Flags: 0x0000
+Default Tag Queue Depth: 8
+Tagged Queue By Device array for aic7xxx
+host instance 1: {255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
+Actual queue depth per device for aic7xxx host instance 1: {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
+Statistics:
+
+(scsi1:0:5:0) Device using Narrow/Sync transfers at 20.0 MByte/sec, offset 15
+Transinfo settings: current(12/15/0/0), goal(12/15/0/0), user(12/15/0/0)
+Total transfers 0 (0 reads and 0 writes)
+ < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
+Reads: 0 0 0 0 0 0 0 0
+Writes: 0 0 0 0 0 0 0 0
+
+(scsi1:0:6:0) Device using Narrow/Sync transfers at 10.0 MByte/sec, offset 15
+Transinfo settings: current(25/15/0/0), goal(12/15/0/0), user(12/15/0/0)
+Total transfers 132 (0 reads and 132 writes)
+ < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
+Reads: 0 0 0 0 0 0 0 0
+Writes: 0 0 0 1 131 0 0 0
+</pre><div class="para">
+ This output reveals the transfer speed to the SCSI devices connected to the controller based on channel ID, as well as detailed statistics concerning the amount and sizes of files read or written by that device. For example, this controller is communicating with the CD-ROM at 20 megabytes per second, while the tape drive is only communicating at 10 megabytes per second.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-net.html"><strong>戻る</strong>E.3.7. /proc/net/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dir-sys.html"><strong>次へ</strong>E.3.9. /proc/sys/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-sys.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-sys.html
new file mode 100644
index 0000000..f18698f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-sys.html
@@ -0,0 +1,332 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.3.9. /proc/sys/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-scsi.html" title="E.3.8. /proc/scsi/" /><link rel="next" href="s2-proc-dir-sysvipc.html" title="E.3.10. /proc/sysvipc/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-scsi.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" h
ref="s2-proc-dir-sysvipc.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dir-sys"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.9. /proc/sys/ </h3></div></div></div><a id="idm62157248" class="indexterm"></a><a id="idm45169392" class="indexterm"></a><a id="idm45167760" class="indexterm"></a><a id="idm45164208" class="indexterm"></a><a id="idm64707888" class="indexterm"></a><a id="idm64706256" class="indexterm"></a><div class="para">
+ The <code class="filename">/proc/sys/</code> directory is different from others in <code class="filename">/proc/</code> because it not only provides information about the system but also allows the system administrator to immediately enable and disable kernel features.
+ </div><div class="warning"><div class="admonition_header"><h2>Be careful when changing the content of /proc/sys/</h2></div><div class="admonition"><div class="para">
+ Use caution when changing settings on a production system using the various files in the <code class="filename">/proc/sys/</code> directory. Changing the wrong setting may render the kernel unstable, requiring a system reboot.
+ </div><div class="para">
+ For this reason, be sure the options are valid for that file before attempting to change any value in <code class="filename">/proc/sys/</code>.
+ </div></div></div><div class="para">
+ A good way to determine if a particular file can be configured, or if it is only designed to provide information, is to list it with the <code class="option">-l</code> option at the shell prompt. If the file is writable, it may be used to configure the kernel. For example, a partial listing of <code class="filename">/proc/sys/fs</code> looks like the following:
+ </div><pre class="screen">
+-r--r--r-- 1 root root 0 May 10 16:14 dentry-state
+-rw-r--r-- 1 root root 0 May 10 16:14 dir-notify-enable
+-rw-r--r-- 1 root root 0 May 10 16:14 file-max
+-r--r--r-- 1 root root 0 May 10 16:14 file-nr
+</pre><div class="para">
+ In this listing, the files <code class="filename">dir-notify-enable</code> and <code class="filename">file-max</code> can be written to and, therefore, can be used to configure the kernel. The other files only provide feedback on current settings.
+ </div><div class="para">
+ Changing a value within a <code class="filename">/proc/sys/</code> file is done by echoing the new value into the file. For example, to enable the System Request Key on a running kernel, type the command:
+ </div><pre class="screen">
+echo 1 > /proc/sys/kernel/sysrq
+</pre><div class="para">
+ This changes the value for <code class="filename">sysrq</code> from <code class="computeroutput">0</code> (off) to <code class="computeroutput">1</code> (on).
+ </div><div class="para">
+ A few <code class="filename">/proc/sys/</code> configuration files contain more than one value. To correctly send new values to them, place a space character between each value passed with the <code class="command">echo</code> command, such as is done in this example:
+ </div><pre class="screen">
+echo 4 2 45 > /proc/sys/kernel/acct
+</pre><div class="note"><div class="admonition_header"><h2>Changes made using the echo command are not persistent</h2></div><div class="admonition"><div class="para">
+ Any configuration changes made using the <code class="command">echo</code> command disappear when the system is restarted. To make configuration changes take effect after the system is rebooted, refer to <a class="xref" href="s1-proc-sysctl.html">「Using the sysctl Command」</a>.
+ </div></div></div><div class="para">
+ The <code class="filename">/proc/sys/</code> directory contains several subdirectories controlling different aspects of a running kernel.
+ </div><div class="section" id="s3-proc-sys-dev"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.1. /proc/sys/dev/ </h4></div></div></div><a id="idm26469040" class="indexterm"></a><div class="para">
+ This directory provides parameters for particular devices on the system. Most systems have at least two directories, <code class="filename">cdrom/</code> and <code class="filename">raid/</code>. Customized kernels can have other directories, such as <code class="filename">parport/</code>, which provides the ability to share one parallel port between multiple device drivers.
+ </div><div class="para">
+ The <code class="filename">cdrom/</code> directory contains a file called <code class="filename">info</code>, which reveals a number of important CD-ROM parameters:
+ </div><pre class="screen">
+CD-ROM information, Id: cdrom.c 3.20 2003/12/17
+drive name: hdc
+drive speed: 48
+drive # of slots: 1
+Can close tray: 1
+Can open tray: 1
+Can lock tray: 1
+Can change speed: 1
+Can select disk: 0
+Can read multisession: 1
+Can read MCN: 1
+Reports media changed: 1
+Can play audio: 1
+Can write CD-R: 0
+Can write CD-RW: 0
+Can read DVD: 0
+Can write DVD-R: 0
+Can write DVD-RAM: 0
+Can read MRW: 0
+Can write MRW: 0
+Can write RAM: 0
+</pre><div class="para">
+ This file can be quickly scanned to discover the qualities of an unknown CD-ROM. If multiple CD-ROMs are available on a system, each device is given its own column of information.
+ </div><div class="para">
+ Various files in <code class="filename">/proc/sys/dev/cdrom</code>, such as <code class="filename">autoclose</code> and <code class="filename">checkmedia</code>, can be used to control the system's CD-ROM. Use the <code class="command">echo</code> command to enable or disable these features.
+ </div><div class="para">
+ If RAID support is compiled into the kernel, a <code class="filename">/proc/sys/dev/raid/</code> directory becomes available with at least two files in it: <code class="filename">speed_limit_min</code> and <code class="filename">speed_limit_max</code>. These settings determine the acceleration of RAID devices for I/O intensive tasks, such as resyncing the disks.
+ </div></div><div class="section" id="s3-proc-sys-fs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.2. /proc/sys/fs/ </h4></div></div></div><a id="idm40938944" class="indexterm"></a><div class="para">
+ This directory contains an array of options and information concerning various aspects of the file system, including quota, file handle, inode, and dentry information.
+ </div><div class="para">
+ The <code class="filename">binfmt_misc/</code> directory is used to provide kernel support for miscellaneous binary formats.
+ </div><div class="para">
+ The important files in <code class="filename">/proc/sys/fs/</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">dentry-state</code> — Provides the status of the directory cache. The file looks similar to the following:
+ </div><pre class="screen">
+57411 52939 45 0 0 0
+</pre><div class="para">
+ The first number reveals the total number of directory cache entries, while the second number displays the number of unused entries. The third number tells the number of seconds between when a directory has been freed and when it can be reclaimed, and the fourth measures the pages currently requested by the system. The last two numbers are not used and display only zeros.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">file-max</code> — Lists the maximum number of file handles that the kernel allocates. Raising the value in this file can resolve errors caused by a lack of available file handles.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">file-nr</code> — Lists the number of allocated file handles, used file handles, and the maximum number of file handles.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overflowgid</code> and <code class="filename">overflowuid</code> — Defines the fixed group ID and user ID, respectively, for use with file systems that only support 16-bit group and user IDs.
+ </div></li></ul></div></div><div class="section" id="s3-proc-sys-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.3. /proc/sys/kernel/ </h4></div></div></div><a id="idm73553760" class="indexterm"></a><a id="idm73550096" class="indexterm"></a><a id="idm73548352" class="indexterm"></a><a id="idm73546128" class="indexterm"></a><a id="idm73543904" class="indexterm"></a><div class="para">
+ This directory contains a variety of different configuration files that directly affect the operation of the kernel. Some of the most important files include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">acct</code> — Controls the suspension of process accounting based on the percentage of free space available on the file system containing the log. By default, the file looks like the following:
+ </div><pre class="screen">
+4 2 30
+</pre><div class="para">
+ The first value dictates the percentage of free space required for logging to resume, while the second value sets the threshold percentage of free space when logging is suspended. The third value sets the interval, in seconds, that the kernel polls the file system to see if logging should be suspended or resumed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ctrl-alt-del</code> — Controls whether <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> gracefully restarts the computer using <code class="command">init</code> (<code class="computeroutput">0</code>) or forces an immediate reboot without syncing the dirty buffers to disk (<code class="computeroutput">1</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">domainname</code> — Configures the system domain name, such as <code class="computeroutput">example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">exec-shield</code> — Configures the Exec Shield feature of the kernel. Exec Shield provides protection against certain types of buffer overflow attacks.
+ </div><div class="para">
+ There are two possible values for this virtual file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">0</code> — Disables Exec Shield.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">1</code> — Enables Exec Shield. This is the default value.
+ </div></li></ul></div><div class="important"><div class="admonition_header"><h2>Using Exec Shield</h2></div><div class="admonition"><div class="para">
+ If a system is running security-sensitive applications that were started while Exec Shield was disabled, these applications must be restarted when Exec Shield is enabled in order for Exec Shield to take effect.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname</code> — Configures the system hostname, such as <code class="computeroutput">www.example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hotplug</code> — Configures the utility to be used when a configuration change is detected by the system. This is primarily used with USB and Cardbus PCI. The default value of <code class="computeroutput">/sbin/hotplug</code> should not be changed unless testing a new program to fulfill this role.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">modprobe</code> — Sets the location of the program used to load kernel modules. The default value is <code class="computeroutput">/sbin/modprobe</code> which means <code class="command">kmod</code> calls it to load the module when a kernel thread calls <code class="command">kmod</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmax</code> — Sets the maximum size of any message sent from one process to another and is set to <code class="computeroutput">8192</code> bytes by default. Be careful when raising this value, as queued messages between processes are stored in non-swappable kernel memory. Any increase in <code class="filename">msgmax</code> would increase RAM requirements for the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmnb</code> — Sets the maximum number of bytes in a single message queue. The default is <code class="computeroutput">16384</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmni</code> — Sets the maximum number of message queue identifiers. The default is <code class="computeroutput">4008</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">osrelease</code> — Lists the Linux kernel release number. This file can only be altered by changing the kernel source and recompiling.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ostype</code> — Displays the type of operating system. By default, this file is set to <code class="computeroutput">Linux</code>, and this value can only be changed by changing the kernel source and recompiling.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overflowgid</code> and <code class="filename">overflowuid</code> — Defines the fixed group ID and user ID, respectively, for use with system calls on architectures that only support 16-bit group and user IDs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">panic</code> — Defines the number of seconds the kernel postpones rebooting when the system experiences a kernel panic. By default, the value is set to <code class="computeroutput">0</code>, which disables automatic rebooting after a panic.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">printk</code> — This file controls a variety of settings related to printing or logging error messages. Each error message reported by the kernel has a <em class="firstterm">loglevel</em> associated with it that defines the importance of the message. The loglevel values break down in this order:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">0</code> — Kernel emergency. The system is unusable.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">1</code> — Kernel alert. Action must be taken immediately.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">2</code> — Condition of the kernel is considered critical.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">3</code> — General kernel error condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">4</code> — General kernel warning condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">5</code> — Kernel notice of a normal but significant condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">6</code> — Kernel informational message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">7</code> — Kernel debug-level messages.
+ </div></li></ul></div><div class="para">
+ Four values are found in the <code class="filename">printk</code> file:
+ </div><pre class="screen">
+6 4 1 7
+</pre><div class="para">
+ Each of these values defines a different rule for dealing with error messages. The first value, called the <em class="firstterm">console loglevel</em>, defines the lowest priority of messages printed to the console. (Note that, the lower the priority, the higher the loglevel number.) The second value sets the default loglevel for messages without an explicit loglevel attached to them. The third value sets the lowest possible loglevel configuration for the console loglevel. The last value sets the default value for the console loglevel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">random/</code> directory — Lists a number of values related to generating random numbers for the kernel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sem</code> — Configures <em class="firstterm">semaphore</em> settings within the kernel. A semaphore is a System V IPC object that is used to control utilization of a particular process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmall</code> — Sets the total amount of shared memory that can be used at one time on the system, in bytes. By default, this value is <code class="computeroutput">2097152</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmmax</code> — Sets the largest shared memory segment size allowed by the kernel. By default, this value is <code class="computeroutput">33554432</code>. However, the kernel supports much larger values than this.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmmni</code> — Sets the maximum number of shared memory segments for the whole system. By default, this value is <code class="computeroutput">4096</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sysrq</code> — Activates the System Request Key, if this value is set to anything other than zero (<code class="computeroutput">0</code>), the default.
+ </div><div class="para">
+ The System Request Key allows immediate input to the kernel through simple key combinations. For example, the System Request Key can be used to immediately shut down or restart a system, sync all mounted file systems, or dump important information to the console. To initiate a System Request Key, type <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>SysRq</strong></span>+<span class="keycap"><strong> <em class="replaceable"><code>system request code</code></em> </strong></span> . Replace <em class="replaceable"><code>system request code</code></em> with one of the following system request codes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">r</code> — Disables raw mode for the keyboard and sets it to XLATE (a limited keyboard mode which does not recognize modifiers such as <span class="keycap"><strong>Alt</strong></span>, <span class="keycap"><strong>Ctrl</strong></span>, or <span class="keycap"><strong>Shift</strong></span> for all keys).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">k</code> — Kills all processes active in a virtual console. Also called <em class="firstterm">Secure Access Key</em> (<em class="firstterm">SAK</em>), it is often used to verify that the login prompt is spawned from <code class="command">init</code> and not a trojan copy designed to capture usernames and passwords.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">b</code> — Reboots the kernel without first unmounting file systems or syncing disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">c</code> — Crashes the system without first unmounting file systems or syncing disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">o</code> — Shuts off the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">s</code> — Attempts to sync disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">u</code> — Attempts to unmount and remount all file systems as read-only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">p</code> — Outputs all flags and registers to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">t</code> — Outputs a list of processes to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">m</code> — Outputs memory statistics to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">0</code> through <code class="command">9</code> — Sets the log level for the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">e</code> — Kills all processes except <code class="command">init</code> using SIGTERM.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">i</code> — Kills all processes except <code class="command">init</code> using SIGKILL.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">l</code> — Kills all processes using SIGKILL (including <code class="command">init</code>). <span class="emphasis"><em>The system is unusable after issuing this System Request Key code.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">h</code> — Displays help text.
+ </div></li></ul></div><div class="para">
+ This feature is most beneficial when using a development kernel or when experiencing system freezes.
+ </div><div class="warning"><div class="admonition_header"><h2>Be careful when enabling the System Request Key feature</h2></div><div class="admonition"><div class="para">
+ The System Request Key feature is considered a security risk because an unattended console provides an attacker with access to the system. For this reason, it is turned off by default.
+ </div></div></div><div class="para">
+ Refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysrq.txt</code> for more information about the System Request Key.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tainted</code> — Indicates whether a non-GPL module is loaded.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">0</code> — No non-GPL modules are loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">1</code> — At least one module without a GPL license (including modules with no license) is loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">2</code> — At least one module was force-loaded with the command <code class="command">insmod -f</code>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="filename">threads-max</code> — Sets the maximum number of threads to be used by the kernel, with a default value of <code class="computeroutput">2048</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">version</code> — Displays the date and time the kernel was last compiled. The first field in this file, such as <code class="computeroutput">#3</code>, relates to the number of times a kernel was built from the source base.
+ </div></li></ul></div></div><div class="section" id="s3-proc-sys-net"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.4. /proc/sys/net/ </h4></div></div></div><a id="idm52356256" class="indexterm"></a><a id="idm52352592" class="indexterm"></a><a id="idm52350880" class="indexterm"></a><a id="idm52349168" class="indexterm"></a><div class="para">
+ This directory contains subdirectories concerning various networking topics. Various configurations at the time of kernel compilation make different directories available here, such as <code class="filename">ethernet/</code>, <code class="filename">ipv4/</code>, <code class="filename">ipx/</code>, and <code class="filename">ipv6/</code>. By altering the files within these directories, system administrators are able to adjust the network configuration on a running system.
+ </div><div class="para">
+ Given the wide variety of possible networking options available with Linux, only the most common <code class="filename">/proc/sys/net/</code> directories are discussed.
+ </div><div class="para">
+ The <code class="filename">/proc/sys/net/core/</code> directory contains a variety of settings that control the interaction between the kernel and networking layers. The most important of these files are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">message_burst</code> — Sets the amount of time in tenths of a second required to write a new warning message. This setting is used to mitigate <em class="firstterm">Denial of Service</em> (<em class="firstterm">DoS</em>) attacks. The default setting is <code class="computeroutput">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">message_cost</code> — Sets a cost on every warning message. The higher the value of this file (default of <code class="computeroutput">5</code>), the more likely the warning message is ignored. This setting is used to mitigate DoS attacks.
+ </div><div class="para">
+ The idea of a DoS attack is to bombard the targeted system with requests that generate errors and fill up disk partitions with log files or require all of the system's resources to handle the error logging. The settings in <code class="filename">message_burst</code> and <code class="filename">message_cost</code> are designed to be modified based on the system's acceptable risk versus the need for comprehensive logging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">netdev_max_backlog</code> — Sets the maximum number of packets allowed to queue when a particular interface receives packets faster than the kernel can process them. The default value for this file is <code class="computeroutput">1000</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">optmem_max</code> — Configures the maximum ancillary buffer size allowed per socket.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rmem_default</code> — Sets the receive socket buffer default size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rmem_max</code> — Sets the receive socket buffer maximum size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wmem_default</code> — Sets the send socket buffer default size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wmem_max</code> — Sets the send socket buffer maximum size in bytes.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">/proc/sys/net/ipv4/</code> directory contains additional networking settings. Many of these settings, used in conjunction with one another, are useful in preventing attacks on the system or when using the system to act as a router.
+ </div><div class="warning"><div class="admonition_header"><h2>Be careful when changing these files</h2></div><div class="admonition"><div class="para">
+ An erroneous change to these files may affect remote connectivity to the system.
+ </div></div></div><div class="para">
+ The following is a list of some of the more important files within the <code class="filename">/proc/sys/net/ipv4/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">icmp_echo_ignore_all</code> and <code class="filename">icmp_echo_ignore_broadcasts</code> — Allows the kernel to ignore ICMP ECHO packets from every host or only those originating from broadcast and multicast addresses, respectively. A value of <code class="computeroutput">0</code> allows the kernel to respond, while a value of <code class="computeroutput">1</code> ignores the packets.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_default_ttl</code> — Sets the default <em class="firstterm">Time To Live (TTL)</em>, which limits the number of hops a packet may make before reaching its destination. Increasing this value can diminish system performance.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_forward</code> — Permits interfaces on the system to forward packets to one other. By default, this file is set to <code class="computeroutput">0</code>. Setting this file to <code class="computeroutput">1</code> enables network packet forwarding.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_local_port_range</code> — Specifies the range of ports to be used by TCP or UDP when a local port is needed. The first number is the lowest port to be used and the second number specifies the highest port. Any systems that expect to require more ports than the default 1024 to 4999 should use a range from 32768 to 61000.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_syn_retries</code> — Provides a limit on the number of times the system re-transmits a SYN packet when attempting to make a connection.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_retries1</code> — Sets the number of permitted re-transmissions attempting to answer an incoming connection. Default of <code class="computeroutput">3</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_retries2</code> — Sets the number of permitted re-transmissions of TCP packets. Default of <code class="computeroutput">15</code>.
+ </div></li></ul></div><div class="para">
+ The file called
+ </div><pre class="screen">
+<code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/ip-sysctl.txt</code>
+</pre><div class="para">
+ contains a complete list of files and options available in the <code class="filename">/proc/sys/net/ipv4/</code> directory.
+ </div><div class="para">
+ A number of other directories exist within the <code class="filename">/proc/sys/net/ipv4/</code> directory and each covers a different aspect of the network stack. The <code class="filename">/proc/sys/net/ipv4/conf/</code> directory allows each system interface to be configured in different ways, including the use of default settings for unconfigured devices (in the <code class="filename">/proc/sys/net/ipv4/conf/default/</code> subdirectory) and settings that override all special configurations (in the <code class="filename">/proc/sys/net/ipv4/conf/all/</code> subdirectory).
+ </div><div class="para">
+ The <code class="filename">/proc/sys/net/ipv4/neigh/</code> directory contains settings for communicating with a host directly connected to the system (called a network neighbor) and also contains different settings for systems more than one hop away.
+ </div><div class="para">
+ Routing over IPV4 also has its own directory, <code class="filename">/proc/sys/net/ipv4/route/</code>. Unlike <code class="filename">conf/</code> and <code class="filename">neigh/</code>, the <code class="filename">/proc/sys/net/ipv4/route/</code> directory contains specifications that apply to routing with any interfaces on the system. Many of these settings, such as <code class="filename">max_size</code>, <code class="filename">max_delay</code>, and <code class="filename">min_delay</code>, relate to controlling the size of the routing cache. To clear the routing cache, write any value to the <code class="filename">flush</code> file.
+ </div><div class="para">
+ Additional information about these directories and the possible values for their configuration files can be found in:
+ </div><pre class="screen">
+/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" id="s3-proc-sys-vm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">E.3.9.5. /proc/sys/vm/ </h4></div></div></div><a id="idm52897776" class="indexterm"></a><a id="idm50196576" class="indexterm"></a><a id="idm50194832" class="indexterm"></a><div class="para">
+ This directory facilitates the configuration of the Linux kernel's virtual memory (VM) subsystem. The kernel makes extensive and intelligent use of virtual memory, which is commonly referred to as swap space.
+ </div><div class="para">
+ The following files are commonly found in the <code class="filename">/proc/sys/vm/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">block_dump</code> — Configures block I/O debugging when enabled. All read/write and block dirtying operations done to files are logged accordingly. This can be useful if diagnosing disk spin up and spin downs for laptop battery conservation. All output when <code class="filename">block_dump</code> is enabled can be retrieved via <code class="command">dmesg</code>. The default value is <code class="computeroutput">0</code>.
+ </div><div class="note"><div class="admonition_header"><h2>Stopping the klogd daemon</h2></div><div class="admonition"><div class="para">
+ If <code class="filename">block_dump</code> is enabled at the same time as kernel debugging, it is prudent to stop the <code class="command">klogd</code> daemon, as it generates erroneous disk activity caused by <code class="filename">block_dump</code>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_background_ratio</code> — Starts background writeback of dirty data at this percentage of total memory, via a pdflush daemon. The default value is <code class="command">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_expire_centisecs</code> — Defines when dirty in-memory data is old enough to be eligible for writeout. Data which has been dirty in-memory for longer than this interval is written out next time a pdflush daemon wakes up. The default value is <code class="command">3000</code>, expressed in hundredths of a second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_ratio</code> — Starts active writeback of dirty data at this percentage of total memory for the generator of dirty data, via pdflush. The default value is <code class="command">20</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_writeback_centisecs</code> — Defines the interval between pdflush daemon wakeups, which periodically writes dirty in-memory data out to disk. The default value is <code class="command">500</code>, expressed in hundredths of a second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">laptop_mode</code> — Minimizes the number of times that a hard disk needs to spin up by keeping the disk spun down for as long as possible, therefore conserving battery power on laptops. This increases efficiency by combining all future I/O processes together, reducing the frequency of spin ups. The default value is <code class="computeroutput">0</code>, but is automatically enabled in case a battery on a laptop is used.
+ </div><div class="para">
+ This value is controlled automatically by the acpid daemon once a user is notified battery power is enabled. No user modifications or interactions are necessary if the laptop supports the ACPI (Advanced Configuration and Power Interface) specification.
+ </div><div class="para">
+ For more information, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/laptop-mode.txt</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">max_map_count</code> — Configures the maximum number of memory map areas a process may have. In most cases, the default value of <code class="computeroutput">65536</code> is appropriate.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">min_free_kbytes</code> — Forces the Linux VM (virtual memory manager) to keep a minimum number of kilobytes free. The VM uses this number to compute a <code class="filename">pages_min</code> value for each <code class="filename">lowmem</code> zone in the system. The default value is in respect to the total memory on the machine.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nr_hugepages</code> — Indicates the current number of configured <code class="filename">hugetlb</code> pages in the kernel.
+ </div><div class="para">
+ For more information, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/vm/hugetlbpage.txt</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nr_pdflush_threads</code> — Indicates the number of pdflush daemons that are currently running. This file is read-only, and should not be changed by the user. Under heavy I/O loads, the default value of two is increased by the kernel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overcommit_memory</code> — Configures the conditions under which a large memory request is accepted or denied. The following three modes are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">0</code> — The kernel performs heuristic memory over commit handling by estimating the amount of memory available and failing requests that are blatantly invalid. Unfortunately, since memory is allocated using a heuristic rather than a precise algorithm, this setting can sometimes allow available memory on the system to be overloaded. This is the default setting.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">1</code> — The kernel performs no memory over commit handling. Under this setting, the potential for memory overload is increased, but so is performance for memory intensive tasks (such as those executed by some scientific software).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">2</code> — The kernel fails requests for memory that add up to all of swap plus the percent of physical RAM specified in <code class="filename">/proc/sys/vm/overcommit_ratio</code>. This setting is best for those who desire less risk of memory overcommitment.
+ </div><div class="note"><div class="admonition_header"><h2>Using this setting</h2></div><div class="admonition"><div class="para">
+ This setting is only recommended for systems with swap areas larger than physical memory.
+ </div></div></div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="filename">overcommit_ratio</code> — Specifies the percentage of physical RAM considered when <code class="filename">/proc/sys/vm/overcommit_memory</code> is set to <code class="command">2</code>. The default value is <code class="command">50</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">page-cluster</code> — Sets the number of pages read in a single attempt. The default value of <code class="computeroutput">3</code>, which actually relates to 16 pages, is appropriate for most systems.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">swappiness</code> — Determines how much a machine should swap. The higher the value, the more swapping occurs. The default value, as a percentage, is set to <code class="computeroutput">60</code>.
+ </div></li></ul></div><div class="para">
+ All kernel-based documentation can be found in the following locally installed location:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/</code>, which contains additional information.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-scsi.html"><strong>戻る</strong>E.3.8. /proc/scsi/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dir-sysvipc.html"><strong>次へ</strong>E.3.10. /proc/sysvipc/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-sysvipc.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-sysvipc.html
new file mode 100644
index 0000000..ae466a5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dir-sysvipc.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>E.3.10. /proc/sysvipc/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-sys.html" title="E.3.9. /proc/sys/" /><link rel="next" href="s2-proc-tty.html" title="E.3.11. /proc/tty/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-sys.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-tt
y.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dir-sysvipc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.10. /proc/sysvipc/ </h3></div></div></div><a id="idm45813488" class="indexterm"></a><div class="para">
+ This directory contains information about System V IPC resources. The files in this directory relate to System V IPC calls for messages (<code class="filename">msg</code>), semaphores (<code class="filename">sem</code>), and shared memory (<code class="filename">shm</code>).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-sys.html"><strong>戻る</strong>E.3.9. /proc/sys/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-tty.html"><strong>次へ</strong>E.3.11. /proc/tty/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dma.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dma.html
new file mode 100644
index 0000000..f52ec83
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-dma.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>E.2.6. /proc/dma</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-devices.html" title="E.2.5. /proc/devices" /><link rel="next" href="s2-proc-execdomains.html" title="E.2.7. /proc/execdomains" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-devices.html"><strong>戻る</strong></a></li><li class="next"><
a accesskey="n" href="s2-proc-execdomains.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-dma"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.6. /proc/dma </h3></div></div></div><a id="idm48015904" class="indexterm"></a><div class="para">
+ This file contains a list of the registered ISA DMA channels in use. A sample <code class="filename">/proc/dma</code> files looks like the following:
+ </div><pre class="screen">
+4: cascade
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-devices.html"><strong>戻る</strong>E.2.5. /proc/devices </a></li><li class="up"><a accesskey="u" href="#"><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-proc-execdomains.html"><strong>次へ</strong>E.2.7. /proc/execdomains </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-execdomains.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-execdomains.html
new file mode 100644
index 0000000..6632bd6
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-execdomains.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>E.2.7. /proc/execdomains</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-dma.html" title="E.2.6. /proc/dma" /><link rel="next" href="s2-proc-fb.html" title="E.2.8. /proc/fb" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dma.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-
fb.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-execdomains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.7. /proc/execdomains </h3></div></div></div><a id="idm48010720" class="indexterm"></a><a id="idm48008128" class="indexterm"></a><a id="idm48006016" class="indexterm"></a><div class="para">
+ This file lists the <em class="firstterm">execution domains</em> currently supported by the Linux kernel, along with the range of personalities they support.
+ </div><pre class="screen">
+0-0 Linux [kernel]
+</pre><div class="para">
+ Think of execution domains as the "personality" for an operating system. Because other binary formats, such as Solaris, UnixWare, and FreeBSD, can be used with Linux, programmers can change the way the operating system treats system calls from these binaries by changing the personality of the task. Except for the <code class="computeroutput">PER_LINUX</code> execution domain, different personalities can be implemented as dynamically loadable modules.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dma.html"><strong>戻る</strong>E.2.6. /proc/dma </a></li><li class="up"><a accesskey="u" href="#"><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-proc-fb.html"><strong>次へ</strong>E.2.8. /proc/fb </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-fb.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-fb.html
new file mode 100644
index 0000000..507b975
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-fb.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>E.2.8. /proc/fb</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-execdomains.html" title="E.2.7. /proc/execdomains" /><link rel="next" href="s2-proc-filesystems.html" title="E.2.9. /proc/filesystems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-execdomains.html"><strong>戻る</strong></a></li><li cl
ass="next"><a accesskey="n" href="s2-proc-filesystems.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-fb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.8. /proc/fb </h3></div></div></div><a id="idm58113104" class="indexterm"></a><a id="idm58110512" class="indexterm"></a><div class="para">
+ This file contains a list of frame buffer devices, with the frame buffer device number and the driver that controls it. Typical output of <code class="filename">/proc/fb</code> for systems which contain frame buffer devices looks similar to the following:
+ </div><pre class="screen">
+0 VESA VGA
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-execdomains.html"><strong>戻る</strong>E.2.7. /proc/execdomains </a></li><li class="up"><a accesskey="u" href="#"><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-proc-filesystems.html"><strong>次へ</strong>E.2.9. /proc/filesystems </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-filesystems.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-filesystems.html
new file mode 100644
index 0000000..7f16a7d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-filesystems.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>E.2.9. /proc/filesystems</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-fb.html" title="E.2.8. /proc/fb" /><link rel="next" href="s2-proc-interrupts.html" title="E.2.10. /proc/interrupts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-fb.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n"
href="s2-proc-interrupts.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.9. /proc/filesystems </h3></div></div></div><a id="idm58105648" class="indexterm"></a><div class="para">
+ This file displays a list of the file system types currently supported by the kernel. Sample output from a generic <code class="filename">/proc/filesystems</code> file looks similar to the following:
+ </div><pre class="screen">
+nodev sysfs
+nodev rootfs
+nodev bdev
+nodev proc
+nodev sockfs
+nodev binfmt_misc
+nodev usbfs
+nodev usbdevfs
+nodev futexfs
+nodev tmpfs
+nodev pipefs
+nodev eventpollfs
+nodev devpts
+ ext2
+nodev ramfs
+nodev hugetlbfs
+ iso9660
+nodev mqueue
+ ext3
+nodev rpc_pipefs
+nodev autofs
+</pre><div class="para">
+ The first column signifies whether the file system is mounted on a block device. Those beginning with <code class="computeroutput">nodev</code> are not mounted on a device. The second column lists the names of the file systems supported.
+ </div><div class="para">
+ The <code class="command">mount</code> command cycles through the file systems listed here when one is not specified as an argument.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-fb.html"><strong>戻る</strong>E.2.8. /proc/fb </a></li><li class="up"><a accesskey="u" href="#"><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-proc-interrupts.html"><strong>次へ</strong>E.2.10. /proc/interrupts </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-interrupts.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-interrupts.html
new file mode 100644
index 0000000..60d87bd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-interrupts.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>E.2.10. /proc/interrupts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-filesystems.html" title="E.2.9. /proc/filesystems" /><link rel="next" href="s2-proc-iomem.html" title="E.2.11. /proc/iomem" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-filesystems.html"><strong>戻る</strong></a></li><li class="next">
<a accesskey="n" href="s2-proc-iomem.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-interrupts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.10. /proc/interrupts </h3></div></div></div><a id="idm48035536" class="indexterm"></a><div class="para">
+ This file records the number of interrupts per IRQ on the x86 architecture. A standard <code class="filename">/proc/interrupts</code> looks similar to the following:
+ </div><pre class="screen">
+ CPU0
+ 0: 80448940 XT-PIC timer
+ 1: 174412 XT-PIC keyboard
+ 2: 0 XT-PIC cascade
+ 8: 1 XT-PIC rtc
+ 10: 410964 XT-PIC eth0
+ 12: 60330 XT-PIC PS/2 Mouse
+ 14: 1314121 XT-PIC ide0
+ 15: 5195422 XT-PIC ide1
+NMI: 0
+ERR: 0
+</pre><div class="para">
+ For a multi-processor machine, this file may look slightly different:
+ </div><pre class="screen">
+ CPU0 CPU1
+ 0: 1366814704 0 XT-PIC timer
+ 1: 128 340 IO-APIC-edge keyboard
+ 2: 0 0 XT-PIC cascade
+ 8: 0 1 IO-APIC-edge rtc
+ 12: 5323 5793 IO-APIC-edge PS/2 Mouse
+ 13: 1 0 XT-PIC fpu
+ 16: 11184294 15940594 IO-APIC-level Intel EtherExpress Pro 10/100 Ethernet
+ 20: 8450043 11120093 IO-APIC-level megaraid
+ 30: 10432 10722 IO-APIC-level aic7xxx
+ 31: 23 22 IO-APIC-level aic7xxx
+NMI: 0
+ERR: 0
+</pre><div class="para">
+ The first column refers to the IRQ number. Each CPU in the system has its own column and its own number of interrupts per IRQ. The next column reports the type of interrupt, and the last column contains the name of the device that is located at that IRQ.
+ </div><div class="para">
+ Each of the types of interrupts seen in this file, which are architecture-specific, mean something different. For x86 machines, the following values are common:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">XT-PIC</code> — This is the old AT computer interrupts.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">IO-APIC-edge</code> — The voltage signal on this interrupt transitions from low to high, creating an <span class="emphasis"><em>edge</em></span>, where the interrupt occurs and is only signaled once. This kind of interrupt, as well as the <code class="computeroutput">IO-APIC-level</code> interrupt, are only seen on systems with processors from the 586 family and higher.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">IO-APIC-level</code> — Generates interrupts when its voltage signal is high until the signal is low again.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-filesystems.html"><strong>戻る</strong>E.2.9. /proc/filesystems </a></li><li class="up"><a accesskey="u" href="#"><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-proc-iomem.html"><strong>次へ</strong>E.2.11. /proc/iomem </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-iomem.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-iomem.html
new file mode 100644
index 0000000..18a8edc
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-iomem.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>E.2.11. /proc/iomem</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-interrupts.html" title="E.2.10. /proc/interrupts" /><link rel="next" href="s2-proc-ioports.html" title="E.2.12. /proc/ioports" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-interrupts.html"><strong>戻る</strong></a></li><li class="next
"><a accesskey="n" href="s2-proc-ioports.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-iomem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.11. /proc/iomem </h3></div></div></div><a id="idm51133024" class="indexterm"></a><div class="para">
+ This file shows you the current map of the system's memory for each physical device:
+ </div><pre class="screen">
+00000000-0009fbff : System RAM
+0009fc00-0009ffff : reserved
+000a0000-000bffff : Video RAM area
+000c0000-000c7fff : Video ROM
+000f0000-000fffff : System ROM
+00100000-07ffffff : System RAM
+00100000-00291ba8 : Kernel code
+00291ba9-002e09cb : Kernel data
+e0000000-e3ffffff : VIA Technologies, Inc. VT82C597 [Apollo VP3] e4000000-e7ffffff : PCI Bus #01
+e4000000-e4003fff : Matrox Graphics, Inc. MGA G200 AGP
+e5000000-e57fffff : Matrox Graphics, Inc. MGA G200 AGP
+e8000000-e8ffffff : PCI Bus #01
+e8000000-e8ffffff : Matrox Graphics, Inc. MGA G200 AGP
+ea000000-ea00007f : Digital Equipment Corporation DECchip 21140 [FasterNet]
+ea000000-ea00007f : tulip ffff0000-ffffffff : reserved
+</pre><div class="para">
+ The first column displays the memory registers used by each of the different types of memory. The second column lists the kind of memory located within those registers and displays which memory registers are used by the kernel within the system RAM or, if the network interface card has multiple Ethernet ports, the memory registers assigned for each port.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-interrupts.html"><strong>戻る</strong>E.2.10. /proc/interrupts </a></li><li class="up"><a accesskey="u" href="#"><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-proc-ioports.html"><strong>次へ</strong>E.2.12. /proc/ioports </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-ioports.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-ioports.html
new file mode 100644
index 0000000..8e56ea3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-ioports.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>E.2.12. /proc/ioports</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-iomem.html" title="E.2.11. /proc/iomem" /><link rel="next" href="s2-proc-kcore.html" title="E.2.13. /proc/kcore" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-iomem.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n"
href="s2-proc-kcore.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-ioports"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.12. /proc/ioports </h3></div></div></div><a id="idm51126464" class="indexterm"></a><div class="para">
+ The output of <code class="filename">/proc/ioports</code> provides a list of currently registered port regions used for input or output communication with a device. This file can be quite long. The following is a partial listing:
+ </div><pre class="screen">
+0000-001f : dma1
+0020-003f : pic1
+0040-005f : timer
+0060-006f : keyboard
+0070-007f : rtc
+0080-008f : dma page reg
+00a0-00bf : pic2
+00c0-00df : dma2
+00f0-00ff : fpu
+0170-0177 : ide1
+01f0-01f7 : ide0
+02f8-02ff : serial(auto)
+0376-0376 : ide1
+03c0-03df : vga+
+03f6-03f6 : ide0
+03f8-03ff : serial(auto)
+0cf8-0cff : PCI conf1
+d000-dfff : PCI Bus #01
+e000-e00f : VIA Technologies, Inc. Bus Master IDE
+e000-e007 : ide0
+e008-e00f : ide1
+e800-e87f : Digital Equipment Corporation DECchip 21140 [FasterNet]
+e800-e87f : tulip
+</pre><div class="para">
+ The first column gives the I/O port address range reserved for the device listed in the second column.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-iomem.html"><strong>戻る</strong>E.2.11. /proc/iomem </a></li><li class="up"><a accesskey="u" href="#"><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-proc-kcore.html"><strong>次へ</strong>E.2.13. /proc/kcore </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-kcore.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-kcore.html
new file mode 100644
index 0000000..d20cf5f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-kcore.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>E.2.13. /proc/kcore</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-ioports.html" title="E.2.12. /proc/ioports" /><link rel="next" href="s2-proc-kmsg.html" title="E.2.14. /proc/kmsg" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-ioports.html"><strong>戻る</strong></a></li><li class="next"><a accesskey=
"n" href="s2-proc-kmsg.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-kcore"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.13. /proc/kcore </h3></div></div></div><a id="idm44549072" class="indexterm"></a><div class="para">
+ This file represents the physical memory of the system and is stored in the core file format. Unlike most <code class="filename">/proc/</code> files, <code class="filename">kcore</code> displays a size. This value is given in bytes and is equal to the size of the physical memory (RAM) used plus 4 KB.
+ </div><div class="para">
+ The contents of this file are designed to be examined by a debugger, such as <code class="command">gdb</code>, and is not human readable.
+ </div><div class="warning"><div class="admonition_header"><h2>Do not attempt to view the content of /proc/kcore</h2></div><div class="admonition"><div class="para">
+ Do not view the <code class="filename">/proc/kcore</code> virtual file. The contents of the file scramble text output on the terminal. If this file is accidentally viewed, press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>C</strong></span> to stop the process and then type <code class="command">reset</code> to bring back the command line prompt.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-ioports.html"><strong>戻る</strong>E.2.12. /proc/ioports </a></li><li class="up"><a accesskey="u" href="#"><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-proc-kmsg.html"><strong>次へ</strong>E.2.14. /proc/kmsg </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-kmsg.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-kmsg.html
new file mode 100644
index 0000000..28fec63
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-kmsg.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>E.2.14. /proc/kmsg</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-kcore.html" title="E.2.13. /proc/kcore" /><link rel="next" href="s2-proc-loadavg.html" title="E.2.15. /proc/loadavg" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-kcore.html"><strong>戻る</strong></a></li><li class="next"><a accesskey=
"n" href="s2-proc-loadavg.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-kmsg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.14. /proc/kmsg </h3></div></div></div><a id="idm44538800" class="indexterm"></a><div class="para">
+ This file is used to hold messages generated by the kernel. These messages are then picked up by other programs, such as <code class="command">/sbin/klogd</code> or <code class="command">/bin/dmesg</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-kcore.html"><strong>戻る</strong>E.2.13. /proc/kcore </a></li><li class="up"><a accesskey="u" href="#"><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-proc-loadavg.html"><strong>次へ</strong>E.2.15. /proc/loadavg </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-loadavg.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-loadavg.html
new file mode 100644
index 0000000..ba88e5c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-loadavg.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>E.2.15. /proc/loadavg</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-kmsg.html" title="E.2.14. /proc/kmsg" /><link rel="next" href="s2-proc-locks.html" title="E.2.16. /proc/locks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-kmsg.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" hre
f="s2-proc-locks.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-loadavg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.15. /proc/loadavg </h3></div></div></div><a id="idm50710032" class="indexterm"></a><div class="para">
+ This file provides a look at the load average in regard to both the CPU and IO over time, as well as additional data used by <code class="command">uptime</code> and other commands. A sample <code class="filename">/proc/loadavg</code> file looks similar to the following:
+ </div><pre class="screen">
+0.20 0.18 0.12 1/80 11206
+</pre><div class="para">
+ The first three columns measure CPU and IO utilization of the last one, five, and 15 minute periods. The fourth column shows the number of currently running processes and the total number of processes. The last column displays the last process ID used.
+ </div><div class="para">
+ In addition, load average also refers to the number of processes ready to run (i.e. in the run queue, waiting for a CPU share.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-kmsg.html"><strong>戻る</strong>E.2.14. /proc/kmsg </a></li><li class="up"><a accesskey="u" href="#"><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-proc-locks.html"><strong>次へ</strong>E.2.16. /proc/locks </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-locks.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-locks.html
new file mode 100644
index 0000000..60326a3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-locks.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>E.2.16. /proc/locks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-loadavg.html" title="E.2.15. /proc/loadavg" /><link rel="next" href="s2-proc-mdstat.html" title="E.2.17. /proc/mdstat" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-loadavg.html"><strong>戻る</strong></a></li><li class="next"><a access
key="n" href="s2-proc-mdstat.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-locks"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.16. /proc/locks </h3></div></div></div><a id="idm50702752" class="indexterm"></a><div class="para">
+ This file displays the files currently locked by the kernel. The contents of this file contain internal kernel debugging data and can vary tremendously, depending on the use of the system. A sample <code class="filename">/proc/locks</code> file for a lightly loaded system looks similar to the following:
+ </div><pre class="screen">
+1: POSIX ADVISORY WRITE 3568 fd:00:2531452 0 EOF
+2: FLOCK ADVISORY WRITE 3517 fd:00:2531448 0 EOF
+3: POSIX ADVISORY WRITE 3452 fd:00:2531442 0 EOF
+4: POSIX ADVISORY WRITE 3443 fd:00:2531440 0 EOF
+5: POSIX ADVISORY WRITE 3326 fd:00:2531430 0 EOF
+6: POSIX ADVISORY WRITE 3175 fd:00:2531425 0 EOF
+7: POSIX ADVISORY WRITE 3056 fd:00:2548663 0 EOF
+</pre><div class="para">
+ Each lock has its own line which starts with a unique number. The second column refers to the class of lock used, with <code class="computeroutput">FLOCK</code> signifying the older-style UNIX file locks from a <code class="command">flock</code> system call and <code class="computeroutput">POSIX</code> representing the newer POSIX locks from the <code class="command">lockf</code> system call.
+ </div><div class="para">
+ The third column can have two values: <code class="computeroutput">ADVISORY</code> or <code class="computeroutput">MANDATORY</code>. <code class="computeroutput">ADVISORY</code> means that the lock does not prevent other people from accessing the data; it only prevents other attempts to lock it. <code class="computeroutput">MANDATORY</code> means that no other access to the data is permitted while the lock is held. The fourth column reveals whether the lock is allowing the holder <code class="computeroutput">READ</code> or <code class="computeroutput">WRITE</code> access to the file. The fifth column shows the ID of the process holding the lock. The sixth column shows the ID of the file being locked, in the format of <code class="computeroutput"><em class="replaceable"><code>MAJOR-DEVICE</code></em>:<em class="replaceable"><code>MINOR-DEVICE</code></em>:<em class="replaceable"><code>INODE-NUMBER</code></em> </code>. The seventh and eighth column shows the start and end o
f the file's locked region.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-loadavg.html"><strong>戻る</strong>E.2.15. /proc/loadavg </a></li><li class="up"><a accesskey="u" href="#"><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-proc-mdstat.html"><strong>次へ</strong>E.2.17. /proc/mdstat </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mdstat.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mdstat.html
new file mode 100644
index 0000000..83c7180
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mdstat.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>E.2.17. /proc/mdstat</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-locks.html" title="E.2.16. /proc/locks" /><link rel="next" href="s2-proc-meminfo.html" title="E.2.18. /proc/meminfo" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-locks.html"><strong>戻る</strong></a></li><li class="next"><a accesskey=
"n" href="s2-proc-meminfo.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-mdstat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.17. /proc/mdstat </h3></div></div></div><a id="idm67187088" class="indexterm"></a><div class="para">
+ This file contains the current information for multiple-disk, RAID configurations. If the system does not contain such a configuration, then <code class="filename">/proc/mdstat</code> looks similar to the following:
+ </div><pre class="screen">
+Personalities : read_ahead not set unused devices: <none>
+</pre><div class="para">
+ This file remains in the same state as seen above unless a software RAID or <code class="filename">md</code> device is present. In that case, view <code class="filename">/proc/mdstat</code> to find the current status of <code class="filename">md<em class="replaceable"><code>X</code></em> </code> RAID devices.
+ </div><div class="para">
+ The <code class="filename">/proc/mdstat</code> file below shows a system with its <code class="filename">md0</code> configured as a RAID 1 device, while it is currently re-syncing the disks:
+ </div><pre class="screen">
+Personalities : [linear] [raid1] read_ahead 1024 sectors
+md0: active raid1 sda2[1] sdb2[0] 9940 blocks [2/2] [UU] resync=1% finish=12.3min algorithm 2 [3/3] [UUU]
+unused devices: <none>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-locks.html"><strong>戻る</strong>E.2.16. /proc/locks </a></li><li class="up"><a accesskey="u" href="#"><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-proc-meminfo.html"><strong>次へ</strong>E.2.18. /proc/meminfo </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-meminfo.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-meminfo.html
new file mode 100644
index 0000000..653fb15
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-meminfo.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>E.2.18. /proc/meminfo</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mdstat.html" title="E.2.17. /proc/mdstat" /><link rel="next" href="s2-proc-misc.html" title="E.2.19. /proc/misc" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-mdstat.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n"
href="s2-proc-misc.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-meminfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.18. /proc/meminfo </h3></div></div></div><a id="idm25329936" class="indexterm"></a><div class="para">
+ This is one of the more commonly used files in the <code class="filename">/proc/</code> directory, as it reports a large amount of valuable information about the systems RAM usage.
+ </div><div class="para">
+ The following sample <code class="filename">/proc/meminfo</code> virtual file is from a system with 256 MB of RAM and 512 MB of swap space:
+ </div><pre class="screen">
+MemTotal: 255908 kB
+MemFree: 69936 kB
+Buffers: 15812 kB
+Cached: 115124 kB
+SwapCached: 0 kB
+Active: 92700 kB
+Inactive: 63792 kB
+HighTotal: 0 kB
+HighFree: 0 kB
+LowTotal: 255908 kB
+LowFree: 69936 kB
+SwapTotal: 524280 kB
+SwapFree: 524280 kB
+Dirty: 4 kB
+Writeback: 0 kB
+Mapped: 42236 kB
+Slab: 25912 kB
+Committed_AS: 118680 kB
+PageTables: 1236 kB
+VmallocTotal: 3874808 kB
+VmallocUsed: 1416 kB
+VmallocChunk: 3872908 kB
+HugePages_Total: 0
+HugePages_Free: 0
+Hugepagesize: 4096 kB
+</pre><div class="para">
+ Much of the information here is used by the <code class="command">free</code>, <code class="command">top</code>, and <code class="command">ps</code> commands. In fact, the output of the <code class="command">free</code> command is similar in appearance to the contents and structure of <code class="filename">/proc/meminfo</code>. But by looking directly at <code class="filename">/proc/meminfo</code>, more details are revealed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">MemTotal</code> — Total amount of physical RAM, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">MemFree</code> — The amount of physical RAM, in kilobytes, left unused by the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Buffers</code> — The amount of physical RAM, in kilobytes, used for file buffers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Cached</code> — The amount of physical RAM, in kilobytes, used as cache memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapCached</code> — The amount of swap, in kilobytes, used as cache memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Active</code> — The total amount of buffer or page cache memory, in kilobytes, that is in active use. This is memory that has been recently used and is usually not reclaimed for other purposes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Inactive</code> — The total amount of buffer or page cache memory, in kilobytes, that are free and available. This is memory that has not been recently used and can be reclaimed for other purposes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HighTotal</code> and <code class="computeroutput">HighFree</code> — The total and free amount of memory, in kilobytes, that is not directly mapped into kernel space. The <code class="computeroutput">HighTotal</code> value can vary based on the type of kernel used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">LowTotal</code> and <code class="computeroutput">LowFree</code> — The total and free amount of memory, in kilobytes, that is directly mapped into kernel space. The <code class="computeroutput">LowTotal</code> value can vary based on the type of kernel used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapTotal</code> — The total amount of swap available, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapFree</code> — The total amount of swap free, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Dirty</code> — The total amount of memory, in kilobytes, waiting to be written back to the disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Writeback</code> — The total amount of memory, in kilobytes, actively being written back to the disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Mapped</code> — The total amount of memory, in kilobytes, which have been used to map devices, files, or libraries using the <code class="command">mmap</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Slab</code> — The total amount of memory, in kilobytes, used by the kernel to cache data structures for its own use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Committed_AS</code> — The total amount of memory, in kilobytes, estimated to complete the workload. This value represents the worst case scenario value, and also includes swap memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">PageTables</code> — The total amount of memory, in kilobytes, dedicated to the lowest page table level.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocTotal</code> — The total amount of memory, in kilobytes, of total allocated virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocUsed</code> — The total amount of memory, in kilobytes, of used virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocChunk</code> — The largest contiguous block of memory, in kilobytes, of available virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HugePages_Total</code> — The total number of hugepages for the system. The number is derived by dividing <code class="computeroutput">Hugepagesize</code> by the megabytes set aside for hugepages specified in <code class="filename">/proc/sys/vm/hugetlb_pool</code>. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HugePages_Free</code> — The total number of hugepages available for the system. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Hugepagesize</code> — The size for each hugepages unit in kilobytes. By default, the value is 4096 KB on uniprocessor kernels for 32 bit architectures. For SMP, hugemem kernels, and AMD64, the default is 2048 KB. For Itanium architectures, the default is 262144 KB. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mdstat.html"><strong>戻る</strong>E.2.17. /proc/mdstat </a></li><li class="up"><a accesskey="u" href="#"><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-proc-misc.html"><strong>次へ</strong>E.2.19. /proc/misc </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-misc.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-misc.html
new file mode 100644
index 0000000..927d84e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-misc.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>E.2.19. /proc/misc</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-meminfo.html" title="E.2.18. /proc/meminfo" /><link rel="next" href="s2-proc-modules.html" title="E.2.20. /proc/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-proc-meminfo.html"><strong>戻る</strong></a></li><li class="next"><a acce
sskey="n" href="s2-proc-modules.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-misc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.19. /proc/misc </h3></div></div></div><a id="idm50520016" class="indexterm"></a><div class="para">
+ This file lists miscellaneous drivers registered on the miscellaneous major device, which is device number 10:
+ </div><pre class="screen">
+63 device-mapper 175 agpgart 135 rtc 134 apm_bios
+</pre><div class="para">
+ The first column is the minor number of each device, while the second column shows the driver in use.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-meminfo.html"><strong>戻る</strong>E.2.18. /proc/meminfo </a></li><li class="up"><a accesskey="u" href="#"><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-proc-modules.html"><strong>次へ</strong>E.2.20. /proc/modules </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-modules.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-modules.html
new file mode 100644
index 0000000..0ace87e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-modules.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>E.2.20. /proc/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-misc.html" title="E.2.19. /proc/misc" /><link rel="next" href="s2-proc-mounts.html" title="E.2.21. /proc/mounts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-misc.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" h
ref="s2-proc-mounts.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.20. /proc/modules </h3></div></div></div><a id="idm69033696" class="indexterm"></a><div class="para">
+ This file displays a list of all modules loaded into the kernel. Its contents vary based on the configuration and use of your system, but it should be organized in a similar manner to this sample <code class="filename">/proc/modules</code> file output:
+ </div><div class="note"><div class="admonition_header"><h2>The content of /proc/modules</h2></div><div class="admonition"><div class="para">
+ This example has been reformatted into a readable format. Most of this information can also be viewed via the <code class="command">/sbin/lsmod</code> command.
+ </div></div></div><pre class="screen">
+nfs 170109 0 - Live 0x129b0000
+lockd 51593 1 nfs, Live 0x128b0000
+nls_utf8 1729 0 - Live 0x12830000
+vfat 12097 0 - Live 0x12823000
+fat 38881 1 vfat, Live 0x1287b000
+autofs4 20293 2 - Live 0x1284f000
+sunrpc 140453 3 nfs,lockd, Live 0x12954000
+3c59x 33257 0 - Live 0x12871000
+uhci_hcd 28377 0 - Live 0x12869000
+md5 3777 1 - Live 0x1282c000
+ipv6 211845 16 - Live 0x128de000
+ext3 92585 2 - Live 0x12886000
+jbd 65625 1 ext3, Live 0x12857000
+dm_mod 46677 3 - Live 0x12833000
+</pre><div class="para">
+ The first column contains the name of the module.
+ </div><div class="para">
+ The second column refers to the memory size of the module, in bytes.
+ </div><div class="para">
+ The third column lists how many instances of the module are currently loaded. A value of zero represents an unloaded module.
+ </div><div class="para">
+ The fourth column states if the module depends upon another module to be present in order to function, and lists those other modules.
+ </div><div class="para">
+ The fifth column lists what load state the module is in: <code class="command">Live</code>, <code class="command">Loading</code>, or <code class="command">Unloading</code> are the only possible values.
+ </div><div class="para">
+ The sixth column lists the current kernel memory offset for the loaded module. This information can be useful for debugging purposes, or for profiling tools such as <code class="filename">oprofile</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-misc.html"><strong>戻る</strong>E.2.19. /proc/misc </a></li><li class="up"><a accesskey="u" href="#"><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-proc-mounts.html"><strong>次へ</strong>E.2.21. /proc/mounts </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mounts.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mounts.html
new file mode 100644
index 0000000..6567591
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mounts.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>E.2.21. /proc/mounts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-modules.html" title="E.2.20. /proc/modules" /><link rel="next" href="s2-proc-mtrr.html" title="E.2.22. /proc/mtrr" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-modules.html"><strong>戻る</strong></a></li><li class="next"><a accesskey=
"n" href="s2-proc-mtrr.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.21. /proc/mounts </h3></div></div></div><a id="idm64735248" class="indexterm"></a><div class="para">
+ This file provides a list of all mounts in use by the system:
+ </div><pre class="screen">
+rootfs / rootfs rw 0 0
+/proc /proc proc rw,nodiratime 0 0 none
+/dev ramfs rw 0 0
+/dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0
+none /dev ramfs rw 0 0
+/proc /proc proc rw,nodiratime 0 0
+/sys /sys sysfs rw 0 0
+none /dev/pts devpts rw 0 0
+usbdevfs /proc/bus/usb usbdevfs rw 0 0
+/dev/hda1 /boot ext3 rw 0 0
+none /dev/shm tmpfs rw 0 0
+none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
+sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
+</pre><div class="para">
+ The output found here is similar to the contents of <code class="filename">/etc/mtab</code>, except that <code class="filename">/proc/mounts</code> is more up-to-date.
+ </div><div class="para">
+ The first column specifies the device that is mounted, the second column reveals the mount point, and the third column tells the file system type, and the fourth column tells you if it is mounted read-only (<code class="computeroutput">ro</code>) or read-write (<code class="computeroutput">rw</code>). The fifth and sixth columns are dummy values designed to match the format used in <code class="filename">/etc/mtab</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-modules.html"><strong>戻る</strong>E.2.20. /proc/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-proc-mtrr.html"><strong>次へ</strong>E.2.22. /proc/mtrr </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mtrr.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mtrr.html
new file mode 100644
index 0000000..fcc7362
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-mtrr.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>E.2.22. /proc/mtrr</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mounts.html" title="E.2.21. /proc/mounts" /><link rel="next" href="s2-proc-partitions.html" title="E.2.23. /proc/partitions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-mounts.html"><strong>戻る</strong></a></li><li class="next"><a a
ccesskey="n" href="s2-proc-partitions.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-mtrr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.22. /proc/mtrr </h3></div></div></div><a id="idm64726416" class="indexterm"></a><div class="para">
+ This file refers to the current Memory Type Range Registers (MTRRs) in use with the system. If the system architecture supports MTRRs, then the <code class="filename">/proc/mtrr</code> file may look similar to the following:
+ </div><pre class="screen">
+reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
+reg01: base=0xe8000000 (3712MB), size= 32MB: write-combining, count=1
+</pre><div class="para">
+ MTRRs are used with the Intel P6 family of processors (Pentium II and higher) and control processor access to memory ranges. When using a video card on a PCI or AGP bus, a properly configured <code class="filename">/proc/mtrr</code> file can increase performance more than 150%.
+ </div><div class="para">
+ Most of the time, this value is properly configured by default. More information on manually configuring this file can be found locally at the following location:
+ </div><pre class="screen">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/<em class="replaceable"><code><arch></code></em>/mtrr.txt</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mounts.html"><strong>戻る</strong>E.2.21. /proc/mounts </a></li><li class="up"><a accesskey="u" href="#"><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-proc-partitions.html"><strong>次へ</strong>E.2.23. /proc/partitions </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-partitions.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-partitions.html
new file mode 100644
index 0000000..6ead174
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-partitions.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>E.2.23. /proc/partitions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mtrr.html" title="E.2.22. /proc/mtrr" /><link rel="next" href="s2-proc-slabinfo.html" title="E.2.24. /proc/slabinfo" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-mtrr.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="
n" href="s2-proc-slabinfo.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-partitions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.23. /proc/partitions </h3></div></div></div><a id="idm61339264" class="indexterm"></a><div class="para">
+ This file contains partition block allocation information. A sampling of this file from a basic system looks similar to the following:
+ </div><pre class="screen">
+major minor #blocks name
+ 3 0 19531250 hda
+ 3 1 104391 hda1
+ 3 2 19422585 hda2
+253 0 22708224 dm-0
+253 1 524288 dm-1
+</pre><div class="para">
+ Most of the information here is of little importance to the user, except for the following columns:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">major</code> — The major number of the device with this partition. The major number in the <code class="filename">/proc/partitions</code>, (<code class="computeroutput">3</code>), corresponds with the block device <code class="computeroutput">ide0</code>, in <code class="filename">/proc/devices</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">minor</code> — The minor number of the device with this partition. This serves to separate the partitions into different physical devices and relates to the number at the end of the name of the partition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">#blocks</code> — Lists the number of physical disk blocks contained in a particular partition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">name</code> — The name of the partition.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mtrr.html"><strong>戻る</strong>E.2.22. /proc/mtrr </a></li><li class="up"><a accesskey="u" href="#"><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-proc-slabinfo.html"><strong>次へ</strong>E.2.24. /proc/slabinfo </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-pci.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-pci.html
new file mode 100644
index 0000000..ca40eed
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-pci.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>E.3.3. /proc/bus/pci</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-bus.html" title="E.3.2. /proc/bus/" /><link rel="next" href="s2-proc-dir-driver.html" title="E.3.4. /proc/driver/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-bus.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s
2-proc-dir-driver.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-pci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.3. /proc/bus/pci </h3></div></div></div><a id="idm64175696" class="indexterm"></a><a id="idm48329968" class="indexterm"></a><div class="para">
+ Later versions of the 2.6 Linux kernel have obsoleted the <code class="filename">/proc/pci</code> directory in favor of the <code class="filename">/proc/bus/pci</code> directory. Although you can get a list of all PCI devices present on the system using the command <code class="command">cat /proc/bus/pci/devices</code>, the output is difficult to read and interpret.
+ </div><div class="para">
+ For a human-readable list of PCI devices, run the following command:
+ </div><pre class="screen">~]# <code class="command">/sbin/lspci -vb</code>
+00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller
+ Subsystem: Hewlett-Packard Company Device 1308
+ Flags: bus master, fast devsel, latency 0
+ Capabilities: [e0] Vendor Specific Information <?>
+ Kernel driver in use: x38_edac
+ Kernel modules: x38_edac
+
+00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge (prog-if 00 [Normal decode])
+ Flags: bus master, fast devsel, latency 0
+ Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
+ I/O behind bridge: 00001000-00001fff
+ Memory behind bridge: f0000000-f2ffffff
+ Capabilities: [88] Subsystem: Hewlett-Packard Company Device 1308
+ Capabilities: [80] Power Management version 3
+ Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
+ Capabilities: [a0] Express Root Port (Slot+), MSI 00
+ Capabilities: [100] Virtual Channel <?>
+ Capabilities: [140] Root Complex Link <?>
+ Kernel driver in use: pcieport
+ Kernel modules: shpchp
+
+00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
+ Subsystem: Hewlett-Packard Company Device 1308
+ Flags: bus master, medium devsel, latency 0, IRQ 5
+ I/O ports at 2100
+ Capabilities: [50] PCI Advanced Features
+ Kernel driver in use: uhci_hcd
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em>
+</pre><div class="para">
+ The output is a sorted list of all IRQ numbers and addresses as seen by the cards on the PCI bus instead of as seen by the kernel. Beyond providing the name and version of the device, this list also gives detailed IRQ information so an administrator can quickly look for conflicts.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-bus.html"><strong>戻る</strong>E.3.2. /proc/bus/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-dir-driver.html"><strong>次へ</strong>E.3.4. /proc/driver/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-pid.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-pid.html
new file mode 100644
index 0000000..e5aaddd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-pid.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>E.3.12. /proc/PID/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-tty.html" title="E.3.11. /proc/tty/" /><link rel="next" href="s1-proc-sysctl.html" title="E.4. Using the sysctl 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-proc-tty.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-
proc-sysctl.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-pid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.12. /proc/<em class="replaceable"><code>PID</code></em>/ </h3></div></div></div><a id="idm35573104" class="indexterm"></a><div class="para">
+ Out of Memory (OOM) refers to a computing state where all available memory, including swap space, has been allocated. When this situation occurs, it will cause the system to panic and stop functioning as expected. There is a switch that controls OOM behavior in <code class="filename">/proc/sys/vm/panic_on_oom</code>. When set to <code class="filename">1</code> the kernel will panic on OOM. A setting of <code class="filename">0</code> instructs the kernel to call a function named <code class="filename">oom_killer</code> on an OOM. Usually, <code class="filename">oom_killer</code> can kill rogue processes and the system will survive.
+ </div><div class="para">
+ The easiest way to change this is to echo the new value to <code class="filename">/proc/sys/vm/panic_on_oom</code>.
+ </div><pre class="screen">
+# cat /proc/sys/vm/panic_on_oom
+1
+
+# echo 0 > /proc/sys/vm/panic_on_oom
+
+# cat /proc/sys/vm/panic_on_oom
+0
+</pre><div class="para">
+ It is also possible to prioritize which processes get killed by adjusting the <code class="filename">oom_killer</code> score. In <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> there are two tools labeled <code class="filename">oom_adj</code> and <code class="filename">oom_score</code>. Valid scores for <code class="filename">oom_adj</code> are in the range -16 to +15. To see the current <code class="filename">oom_killer</code> score, view the <code class="filename">oom_score</code> for the process. <code class="filename">oom_killer</code> will kill processes with the highest scores first.
+ </div><div class="para">
+ This example adjusts the oom_score of a process with a <em class="replaceable"><code>PID</code></em> of 12465 to make it less likely that <code class="filename">oom_killer</code> will kill it.
+ </div><pre class="screen">
+# cat /proc/12465/oom_score
+79872
+
+# echo -5 > /proc/12465/oom_adj
+
+# cat /proc/12465/oom_score
+78
+</pre><div class="para">
+ There is also a special value of -17, which disables <code class="filename">oom_killer</code> for that process. In the example below, <code class="filename">oom_score</code> returns a value of 0, indicating that this process would not be killed.
+ </div><pre class="screen">
+# cat /proc/12465/oom_score
+78
+
+# echo -17 > /proc/12465/oom_adj
+
+# cat /proc/12465/oom_score
+0
+</pre><div class="para">
+ A function called <code class="filename">badness()</code> is used to determine the actual score for each process. This is done by adding up 'points' for each examined process. The process scoring is done in the following way:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The basis of each process's score is its memory size.
+ </div></li><li class="listitem"><div class="para">
+ The memory size of any of the process's children (not including a kernel thread) is also added to the score
+ </div></li><li class="listitem"><div class="para">
+ The process's score is increased for 'niced' processes and decreased for long running processes.
+ </div></li><li class="listitem"><div class="para">
+ Processes with the <code class="filename">CAP_SYS_ADMIN</code> and <code class="filename">CAP_SYS_RAWIO</code> capabilities have their scores reduced.
+ </div></li><li class="listitem"><div class="para">
+ The final score is then bitshifted by the value saved in the <code class="filename">oom_adj</code> file.
+ </div></li></ol></div><div class="para">
+ Thus, a process with the highest <code class="filename">oom_score</code> value will most probably be a non-priviliged, recently started process that, along with its children, uses a large amount of memory, has been 'niced', and handles no raw I/O.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-tty.html"><strong>戻る</strong>E.3.11. /proc/tty/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-sysctl.html"><strong>次へ</strong>E.4. Using the sysctl Command</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-slabinfo.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-slabinfo.html
new file mode 100644
index 0000000..56e01f2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-slabinfo.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>E.2.24. /proc/slabinfo</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-partitions.html" title="E.2.23. /proc/partitions" /><link rel="next" href="s2-proc-stat.html" title="E.2.25. /proc/stat" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-partitions.html"><strong>戻る</strong></a></li><li class="next"><a a
ccesskey="n" href="s2-proc-stat.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-slabinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.24. /proc/slabinfo </h3></div></div></div><a id="idm24304336" class="indexterm"></a><a id="idm24301632" class="indexterm"></a><div class="para">
+ This file gives full information about memory usage on the <em class="firstterm">slab</em> level. Linux kernels greater than version 2.2 use <em class="firstterm">slab pools</em> to manage memory above the page level. Commonly used objects have their own slab pools.
+ </div><div class="para">
+ Instead of parsing the highly verbose <code class="filename">/proc/slabinfo</code> file manually, the <code class="filename">/usr/bin/slabtop</code> program displays kernel slab cache information in real time. This program allows for custom configurations, including column sorting and screen refreshing.
+ </div><div class="para">
+ A sample screen shot of <code class="filename">/usr/bin/slabtop</code> usually looks like the following example:
+ </div><pre class="screen">
+Active / Total Objects (% used) : 133629 / 147300 (90.7%)
+Active / Total Slabs (% used) : 11492 / 11493 (100.0%)
+Active / Total Caches (% used) : 77 / 121 (63.6%)
+Active / Total Size (% used) : 41739.83K / 44081.89K (94.7%)
+Minimum / Average / Maximum Object : 0.01K / 0.30K / 128.00K
+OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
+44814 43159 96% 0.62K 7469 6 29876K ext3_inode_cache
+36900 34614 93% 0.05K 492 75 1968K buffer_head
+35213 33124 94% 0.16K 1531 23 6124K dentry_cache
+7364 6463 87% 0.27K 526 14 2104K radix_tree_node
+2585 1781 68% 0.08K 55 47 220K vm_area_struct
+2263 2116 93% 0.12K 73 31 292K size-128
+1904 1125 59% 0.03K 16 119 64K size-32
+1666 768 46% 0.03K 14 119 56K anon_vma
+1512 1482 98% 0.44K 168 9 672K inode_cache
+1464 1040 71% 0.06K 24 61 96K size-64
+1320 820 62% 0.19K 66 20 264K filp
+678 587 86% 0.02K 3 226 12K dm_io
+678 587 86% 0.02K 3 226 12K dm_tio
+576 574 99% 0.47K 72 8 288K proc_inode_cache
+528 514 97% 0.50K 66 8 264K size-512
+492 372 75% 0.09K 12 41 48K bio
+465 314 67% 0.25K 31 15 124K size-256
+452 331 73% 0.02K 2 226 8K biovec-1
+420 420 100% 0.19K 21 20 84K skbuff_head_cache
+305 256 83% 0.06K 5 61 20K biovec-4
+290 4 1% 0.01K 1 290 4K revoke_table
+264 264 100% 4.00K 264 1 1056K size-4096
+260 256 98% 0.19K 13 20 52K biovec-16
+260 256 98% 0.75K 52 5 208K biovec-64
+</pre><div class="para">
+ Some of the more commonly used statistics in <code class="filename">/proc/slabinfo</code> that are included into <code class="filename">/usr/bin/slabtop</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJS</code> — The total number of objects (memory blocks), including those in use (allocated), and some spares not in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">ACTIVE</code> — The number of objects (memory blocks) that are in use (allocated).
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">USE</code> — Percentage of total objects that are active. ((ACTIVE/OBJS)(100))
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJ SIZE</code> — The size of the objects.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SLABS</code> — The total number of slabs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJ/SLAB</code> — The number of objects that fit into a slab.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">CACHE SIZE</code> — The cache size of the slab.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NAME</code> — The name of the slab.
+ </div></li></ul></div><div class="para">
+ For more information on the <code class="filename">/usr/bin/slabtop</code> program, refer to the <code class="filename">slabtop</code> man page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-partitions.html"><strong>戻る</strong>E.2.23. /proc/partitions </a></li><li class="up"><a accesskey="u" href="#"><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-proc-stat.html"><strong>次へ</strong>E.2.25. /proc/stat </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-stat.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-stat.html
new file mode 100644
index 0000000..35a9127
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-stat.html
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.2.25. /proc/stat</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-slabinfo.html" title="E.2.24. /proc/slabinfo" /><link rel="next" href="s2-proc-swaps.html" title="E.2.26. /proc/swaps" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-slabinfo.html"><strong>戻る</strong></a></li><li class="next"><a acces
skey="n" href="s2-proc-swaps.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-stat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.25. /proc/stat </h3></div></div></div><a id="idm49704336" class="indexterm"></a><a id="idm41045696" class="indexterm"></a><a id="idm41043952" class="indexterm"></a><div class="para">
+ This file keeps track of a variety of different statistics about the system since it was last restarted. The contents of <code class="filename">/proc/stat</code>, which can be quite long, usually begins like the following example:
+ </div><pre class="screen">
+cpu 259246 7001 60190 34250993 137517 772 0
+cpu0 259246 7001 60190 34250993 137517 772 0
+intr 354133732 347209999 2272 0 4 4 0 0 3 1 1249247 0 0 80143 0 422626 5169433
+ctxt 12547729
+btime 1093631447
+processes 130523
+procs_running 1
+procs_blocked 0
+preempt 5651840
+cpu 209841 1554 21720 118519346 72939 154 27168
+cpu0 42536 798 4841 14790880 14778 124 3117
+cpu1 24184 569 3875 14794524 30209 29 3130
+cpu2 28616 11 2182 14818198 4020 1 3493
+cpu3 35350 6 2942 14811519 3045 0 3659
+cpu4 18209 135 2263 14820076 12465 0 3373
+cpu5 20795 35 1866 14825701 4508 0 3615
+cpu6 21607 0 2201 14827053 2325 0 3334
+cpu7 18544 0 1550 14831395 1589 0 3447
+intr 15239682 14857833 6 0 6 6 0 5 0 1 0 0 0 29 0 2 0 0 0 0 0 0 0 94982 0 286812
+ctxt 4209609
+btime 1078711415
+processes 21905
+procs_running 1
+procs_blocked 0
+</pre><div class="para">
+ Some of the more commonly used statistics include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu</code> — Measures the number of <em class="firstterm">jiffies</em> (1/100 of a second for x86 systems) that the system has been in user mode, user mode with low priority (nice), system mode, idle task, I/O wait, IRQ (hardirq), and softirq respectively. The IRQ (hardirq) is the direct response to a hardware event. The IRQ takes minimal work for queuing the "heavy" work up for the softirq to execute. The softirq runs at a lower priority than the IRQ and therefore may be interrupted more frequently. The total for all CPUs is given at the top, while each individual CPU is listed below with its own statistics. The following example is a 4-way Intel Pentium Xeon configuration with multi-threading enabled, therefore showing four physical processors and four virtual processors totaling eight processors.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">page</code> — The number of memory pages the system has written in and out to disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">swap</code> — The number of swap pages the system has brought in and out.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">intr</code> — The number of interrupts the system has experienced.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">btime</code> — The boot time, measured in the number of seconds since January 1, 1970, otherwise known as the <em class="firstterm">epoch</em>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-slabinfo.html"><strong>戻る</strong>E.2.24. /proc/slabinfo </a></li><li class="up"><a accesskey="u" href="#"><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-proc-swaps.html"><strong>次へ</strong>E.2.26. /proc/swaps </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-swaps.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-swaps.html
new file mode 100644
index 0000000..d05fe0b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-swaps.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>E.2.26. /proc/swaps</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-stat.html" title="E.2.25. /proc/stat" /><link rel="next" href="s2-proc-sysrq-trigger.html" title="E.2.27. /proc/sysrq-trigger" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-stat.html"><strong>戻る</strong></a></li><li class="next"><a a
ccesskey="n" href="s2-proc-sysrq-trigger.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-swaps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.26. /proc/swaps </h3></div></div></div><a id="idm60964368" class="indexterm"></a><div class="para">
+ This file measures swap space and its utilization. For a system with only one swap partition, the output of <code class="filename">/proc/swaps</code> may look similar to the following:
+ </div><pre class="screen">
+Filename Type Size Used Priority
+/dev/mapper/VolGroup00-LogVol01 partition 524280 0 -1
+</pre><div class="para">
+ While some of this information can be found in other files in the <code class="filename">/proc/</code> directory, <code class="filename">/proc/swap</code> provides a snapshot of every swap file name, the type of swap space, the total size, and the amount of space in use (in kilobytes). The priority column is useful when multiple swap files are in use. The lower the priority, the more likely the swap file is to be used.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-stat.html"><strong>戻る</strong>E.2.25. /proc/stat </a></li><li class="up"><a accesskey="u" href="#"><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-proc-sysrq-trigger.html"><strong>次へ</strong>E.2.27. /proc/sysrq-trigger </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-sysrq-trigger.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-sysrq-trigger.html
new file mode 100644
index 0000000..3a5bf2c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-sysrq-trigger.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>E.2.27. /proc/sysrq-trigger</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-swaps.html" title="E.2.26. /proc/swaps" /><link rel="next" href="s2-proc-uptime.html" title="E.2.28. /proc/uptime" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-swaps.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n
" href="s2-proc-uptime.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-sysrq-trigger"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.27. /proc/sysrq-trigger </h3></div></div></div><a id="idm60957040" class="indexterm"></a><div class="para">
+ Using the <code class="command">echo</code> command to write to this file, a remote root user can execute most System Request Key commands remotely as if at the local terminal. To <code class="command">echo</code> values to this file, the <code class="filename">/proc/sys/kernel/sysrq</code> must be set to a value other than <code class="computeroutput">0</code>. For more information about the System Request Key, refer to <a class="xref" href="s2-proc-dir-sys.html#s3-proc-sys-kernel">「 /proc/sys/kernel/ 」</a>.
+ </div><div class="para">
+ Although it is possible to write to this file, it cannot be read, even by the root user.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-swaps.html"><strong>戻る</strong>E.2.26. /proc/swaps </a></li><li class="up"><a accesskey="u" href="#"><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-proc-uptime.html"><strong>次へ</strong>E.2.28. /proc/uptime </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-tty.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-tty.html
new file mode 100644
index 0000000..8b1c1ba
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-tty.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>E.3.11. /proc/tty/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-sysvipc.html" title="E.3.10. /proc/sysvipc/" /><link rel="next" href="s2-proc-pid.html" title="E.3.12. /proc/PID/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-sysvipc.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" hre
f="s2-proc-pid.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-tty"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.3.11. /proc/tty/ </h3></div></div></div><a id="idm45807408" class="indexterm"></a><div class="para">
+ This directory contains information about the available and currently used <em class="firstterm">tty devices</em> on the system. Originally called <em class="firstterm">teletype devices</em>, any character-based data terminals are called tty devices.
+ </div><div class="para">
+ In Linux, there are three different kinds of tty devices. <em class="firstterm">Serial devices</em> are used with serial connections, such as over a modem or using a serial cable. <em class="firstterm">Virtual terminals</em> create the common console connection, such as the virtual consoles available when pressing <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong><F-key></strong></span> at the system console. <em class="firstterm">Pseudo terminals</em> create a two-way communication that is used by some higher level applications, such as XFree86. The <code class="filename">drivers</code> file is a list of the current tty devices in use, as in the following example:
+ </div><pre class="screen">
+serial /dev/cua 5 64-127 serial:callout
+serial /dev/ttyS 4 64-127 serial
+pty_slave /dev/pts 136 0-255 pty:slave
+pty_master /dev/ptm 128 0-255 pty:master
+pty_slave /dev/ttyp 3 0-255 pty:slave
+pty_master /dev/pty 2 0-255 pty:master
+/dev/vc/0 /dev/vc/0 4 0 system:vtmaster
+/dev/ptmx /dev/ptmx 5 2 system
+/dev/console /dev/console 5 1 system:console
+/dev/tty /dev/tty 5 0 system:/dev/tty
+unknown /dev/vc/%d 4 1-63 console
+</pre><div class="para">
+ The <code class="filename">/proc/tty/driver/serial</code> file lists the usage statistics and status of each of the serial tty lines.
+ </div><div class="para">
+ In order for tty devices to be used as network devices, the Linux kernel enforces <em class="firstterm">line discipline</em> on the device. This allows the driver to place a specific type of header with every block of data transmitted over the device, making it possible for the remote end of the connection to a block of data as just one in a stream of data blocks. SLIP and PPP are common line disciplines, and each are commonly used to connect systems to one other over a serial link.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-sysvipc.html"><strong>戻る</strong>E.3.10. /proc/sysvipc/ </a></li><li class="up"><a accesskey="u" href="#"><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-proc-pid.html"><strong>次へ</strong>E.3.12. /proc/PID/ </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-uptime.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-uptime.html
new file mode 100644
index 0000000..0b2004c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-uptime.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>E.2.28. /proc/uptime</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-sysrq-trigger.html" title="E.2.27. /proc/sysrq-trigger" /><link rel="next" href="s2-proc-version.html" title="E.2.29. /proc/version" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-sysrq-trigger.html"><strong>戻る</strong></a></li><li cl
ass="next"><a accesskey="n" href="s2-proc-version.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-uptime"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.28. /proc/uptime </h3></div></div></div><a id="idm58020720" class="indexterm"></a><div class="para">
+ This file contains information detailing how long the system has been on since its last restart. The output of <code class="filename">/proc/uptime</code> is quite minimal:
+ </div><pre class="screen">
+350735.47 234388.90
+</pre><div class="para">
+ The first number is the total number of seconds the system has been up. The second number is how much of that time the machine has spent idle, in seconds.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-sysrq-trigger.html"><strong>戻る</strong>E.2.27. /proc/sysrq-trigger </a></li><li class="up"><a accesskey="u" href="#"><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-proc-version.html"><strong>次へ</strong>E.2.29. /proc/version </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-version.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-version.html
new file mode 100644
index 0000000..fd6756e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-proc-version.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>E.2.29. /proc/version</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-proc-topfiles.html" title="E.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-uptime.html" title="E.2.28. /proc/uptime" /><link rel="next" href="s1-proc-directories.html" title="E.3. Directories within /proc/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-uptime.html"><strong>戻る</strong></a></li><li class="nex
t"><a accesskey="n" href="s1-proc-directories.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-proc-version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.2.29. /proc/version </h3></div></div></div><a id="idm58014528" class="indexterm"></a><div class="para">
+ This file specifies the version of the Linux kernel, the version of <code class="command">gcc</code> used to compile the kernel, and the time of kernel compilation. It also contains the kernel compiler's user name (in parentheses).
+ </div><pre class="screen">
+Linux version 2.6.8-1.523 (user at foo.redhat.com) (gcc version 3.4.1 20040714 \ (Red Hat Enterprise Linux 3.4.1-7)) #1 Mon Aug 16 13:27:03 EDT 2004
+</pre><div class="para">
+ This information is used for a variety of purposes, including the version data presented when a user logs in.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-uptime.html"><strong>戻る</strong>E.2.28. /proc/uptime </a></li><li class="up"><a accesskey="u" href="#"><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-proc-directories.html"><strong>次へ</strong>E.3. Directories within /proc/</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-group-new.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-group-new.html
new file mode 100644
index 0000000..b3d5696
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-group-new.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>3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-users-configui.html" title="3.3. ユーザー管理のツールを使う" /><link rel="prev" href="s2-redhat-config-users-user-new.html" title="3.3.2. 新規ユーザーを追加する" /><link rel="next" href="s2-redhat-config-users-user-properties.html" title="3.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-redhat-config-users-user-new.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-redhat-config-users-user-properties.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-redhat-config-users-group-new"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.3. 新規グループを追加する</h3></div></div></div><a id="idm69814976" class="indexterm"></a><div class="para">
+ 新規ユーザーグループを追加するには、ツールバーから<span class="guibutton"><strong>グループの追加</strong></span>を選択します。<a class="xref" href="s2-redhat-config-users-group-new.html#group-new-fig">図3.7「新規グループ」</a>のようなウィンドウが表示されます。新規グループの名前を入力します。<span class="guilabel"><strong>グループ ID を手動で指定</strong></span>を選択して、GID を選択します。Fedora は1000未満のグループ ID をシステムグループのために予約していることにも注意してください。
+ </div><div class="figure" id="group-new-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager-add-group.png" alt="新規グループ" /><div class="longdesc"><div class="para">
+ Creating a new group
+ </div></div></div></div><h6>図3.7 新規グループ</h6></div><br class="figure-break" /><div class="para">
+ グループを作成するには <span class="guibutton"><strong>OK</strong></span> をクリックします。新規グループがグループ一覧に表示されます。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-redhat-config-users-user-new.html"><strong>戻る</strong>3.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-redhat-config-users-user-properties.html"><strong>次へ</strong>3.3.4. ユーザーのプロパティを変更する</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-group-properties.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-group-properties.html
new file mode 100644
index 0000000..e3fb2cd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-group-properties.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>3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-users-configui.html" title="3.3. ユーザー管理のツールを使う" /><link rel="prev" href="s2-redhat-config-users-user-properties.html" title="3.3.4. ユーザーのプロパティを変更する" /><link rel="next" href="s1-users-tools.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="s2
-redhat-config-users-user-properties.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="s2-redhat-config-users-group-properties"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.5. グループのプロパティを変更する</h3></div></div></div><a id="idm54975904" class="indexterm"></a><div class="para">
+ 既存のグループのプロパティを表示するには、グループの一覧からグループを選択して、メニューから<span class="guimenuitem"><strong>プロパティ</strong></span>をクリックします（または、プルダウンメニューから<span class="guimenu"><strong>ファイル</strong></span> → <span class="guimenuitem"><strong>プロパティ</strong></span>を選びます）。<a class="xref" href="s2-redhat-config-users-group-properties.html#group-properties-fig">図3.9「グループのプロパティ」</a>のようなウィンドウが表示されます。
+ </div><div class="figure" id="group-properties-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager-edit-group.png" alt="グループのプロパティ" /><div class="longdesc"><div class="para">
+ Modifying group properties
+ </div></div></div></div><h6>図3.9 グループのプロパティ</h6></div><br class="figure-break" /><a id="idm66170000" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>グループユーザー</strong></span>タブは、どのユーザーがグループのメンバーであるかを表示します。グループのユーザーを追加または削除するには、このタブを使用します。変更を保存するには <span class="guibutton"><strong>OK</strong></span> をクリックします。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-redhat-config-users-user-properties.html"><strong>戻る</strong>3.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-tools.html"><strong>次へ</strong>3.4. コマンドラインのツールを使う</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-user-new.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-user-new.html
new file mode 100644
index 0000000..b646261
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-user-new.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>3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-users-configui.html" title="3.3. ユーザー管理のツールを使う" /><link rel="prev" href="s1-users-configui.html" title="3.3. ユーザー管理のツールを使う" /><link rel="next" href="s2-redhat-config-users-group-new.html" title="3.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-configui.ht
ml"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-redhat-config-users-group-new.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-redhat-config-users-user-new"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.2. 新規ユーザーを追加する</h3></div></div></div><a id="idm28638368" class="indexterm"></a><div class="para">
+ 新しいユーザーを追加するには、<span class="guibutton"><strong>ユーザーの追加</strong></span>ボタンをクリックします。<a class="xref" href="s2-redhat-config-users-user-new.html#user-new-fig">図3.6「新しいユーザーを追加する」</a>にあるようなウィンドウが表示されます。
+ </div><div class="figure" id="user-new-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager-add-user.png" alt="新しいユーザーを追加する" /><div class="longdesc"><div class="para">
+ 新しいユーザーを追加する
+ </div></div></div></div><h6>図3.6 新しいユーザーを追加する</h6></div><br class="figure-break" /><div class="para">
+ <span class="guilabel"><strong>新規ユーザーの追加</strong></span>ダイアログボックスにより、新しく作成するユーザーに関する情報を提供できます。ユーザーを作成するために、適切なフィールドにユーザー名とフルネームを、<span class="guilabel"><strong>パスワード</strong></span>と<span class="guilabel"><strong>パスワードの確認</strong></span>フィールドにユーザーのパスワードを入力します。パスワードは少なくても6文字でなければいけません。
+ </div><div class="note"><div class="admonition_header"><h2>パスワードのセキュリティのアドバイス</h2></div><div class="admonition"><div class="para">
+ 非常に長いパスワードを使用することをお勧めします。これにより、侵入者がパスワードを推測して、権限なくアカウントにアクセスすることを難しくなるからです。また、パスワードは辞書に載っている単語を基にしないことをお勧めします。文字、数字と特殊文字の組み合わせを使用します。
+ </div></div></div><div class="para">
+ <span class="guilabel"><strong>ログインシェル</strong></span>プルダウンリストにより、ユーザーのログインシェルを選択できます。選択するシェルが確かではなければ、デフォルトの <span class="guimenuitem"><strong>/bin/bash</strong></span> を受け入れてください。
+ </div><div class="para">
+ デフォルトで、<span class="application"><strong>ユーザー管理</strong></span>アプリケーションは <code class="filename">/home/<em class="replaceable"><code>username</code></em>/</code> に新しいユーザーのためのホームディレクトリを作成します。<span class="guilabel"><strong>ホームディレクトリの作成</strong></span>チェックボックスを外してホームディレクトリを作成しないことを選択できます。または<span class="guilabel"><strong>ホームディレクトリ</strong></span>テキストボックスの内容を編集することにより、このディレクトリを変更できます。ホームディレクトリを作成するときに、デフォルトの設定ファイルが <code class="filename">/etc/skel/</code> ディレクトリの中からコピーされることに注意してください。
+ </div><div class="para">
+ Fedora はユーザープライベートグループ (UPG) スキーマを使用します。新規ユーザーを作成すると必ず、ユーザーと同じ名前を持つ一意なグループがデフォルトで作成されます。このグループを作成したくなければ、<span class="guilabel"><strong>ユーザーのプライベートグループを作成する</strong></span>チェックボックスを外します。
+ </div><div class="para">
+ ユーザーのユーザー ID を指定するには、<span class="guilabel"><strong>ユーザー ID を手動で指定する</strong></span>を選択します。このオプションが選択されなければ、1000以上で次に利用可能なユーザー ID が新規ユーザーに割り当てられます。Fedora は1000未満のユーザー ID をシステムユーザーのために予約しているので、ユーザー ID を手動で 1-999 に割り当てることはお勧めできません。
+ </div><div class="para">
+ <span class="guibutton"><strong>OK</strong></span> ボタンをクリックして新規ユーザーを作成します。パスワード有効期限のようなさらに高度なユーザーのプロパティを設定するには、ユーザーの追加後にユーザーのプロパティを修正します。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-configui.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="s2-redhat-config-users-group-new.html"><strong>次へ</strong>3.3.3. 新規グループを追加する</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-user-properties.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-user-properties.html
new file mode 100644
index 0000000..f7e08bc
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-redhat-config-users-user-properties.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>3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-users-configui.html" title="3.3. ユーザー管理のツールを使う" /><link rel="prev" href="s2-redhat-config-users-group-new.html" title="3.3.3. 新規グループを追加する" /><link rel="next" href="s2-redhat-config-users-group-properties.html" title="3.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-redhat-config-users-group-new.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-redhat-config-users-group-properties.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-redhat-config-users-user-properties"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.3.4. ユーザーのプロパティを変更する</h3></div></div></div><a id="idm35554944" class="indexterm"></a><a id="idm35553504" class="indexterm"></a><div class="para">
+ 既存のユーザーのプロパティを表示するには、<span class="guilabel"><strong>ユーザー</strong></span>タブをクリックして、ユーザーの一覧からユーザーを選択します。そして、メニューから<span class="guimenuitem"><strong>プロパティ</strong></span>をクリックします（またはプルダウンメニューから<span class="guimenu"><strong>ファイル</strong></span> → <span class="guimenuitem"><strong>プロパティProperties</strong></span>を選びます）。<a class="xref" href="s2-redhat-config-users-user-properties.html#user-properties-fig">図3.8「ユーザーのプロパティ」</a>のようなウィンドウが表示されます。
+ </div><div class="figure" id="user-properties-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-manager-edit-user.png" alt="ユーザーのプロパティ" /><div class="longdesc"><div class="para">
+ Modifying user properties
+ </div></div></div></div><h6>図3.8 ユーザーのプロパティ</h6></div><br class="figure-break" /><div class="para">
+ <span class="guilabel"><strong>ユーザーのプロパティ</strong></span>ウィンドウは複数のタブページに分割されています:
+ </div><a id="idm63220240" class="indexterm"></a><a id="idm63218832" class="indexterm"></a><a id="idm63217424" class="indexterm"></a><a id="idm43512928" class="indexterm"></a><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>アカウント情報</strong></span> — アカウントを特定の日付に失効されたければ、<span class="guilabel"><strong>アカウント失効を有効にする</strong></span>を選択します。ユーザーアカウントをロックして、ユーザーがシステムにログインできないようにするには、<span class="guilabel"><strong>ローカルパスワードがロックされています</strong></span>を選択します。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>パスワード情報</strong></span> — ユーザーのパスワードが最後に変更された日付を表示します。特定の日数経過後にパスワードの変更を強制するには、<span class="guilabel"><strong>パスワード失効を有効にする</strong></span>を選択して、<span class="guilabel"><strong>変更が要求されるまでの日数:</strong></span>フィールドに希望する値を入力します。ユーザーのパスワードが失効するまでの日数、パスワードの変更を警告されるまでの日数、アカウントが無効になるまでの日数も変更できます。
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>グループ</strong></span> — ユーザーのプライマリーグループ、およびユーザーをメンバーにしたいグループを表示および設定することができます。
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-redhat-config-users-group-new.html"><strong>戻る</strong>3.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-redhat-config-users-group-properties.html"><strong>次へ</strong>3.3.5. グループのプロパティを変更する</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-freshening.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-freshening.html
new file mode 100644
index 0000000..41dd7ec
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-freshening.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>B.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-rpm-using.html" title="B.2. RPMの使用法" /><link rel="prev" href="s2-rpm-uninstalling.html" title="B.2.4. アンインストール" /><link rel="next" href="s2-rpm-querying.html" title="B.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-rpm-uninstalling.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" hre
f="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">B.2.5. インストール済みのアップグレードの実行</h3></div></div></div><a id="idm64716656" class="indexterm"></a><a id="idm35793360" class="indexterm"></a><div class="para">
+ Freshening is similar to upgrading, except that only existent packages are upgraded. Type the following command at a shell prompt:
+ </div><pre class="screen">
+<code class="command">rpm -Fvh foo-2.0-1.fc17.x86_64.rpm</code>
+</pre><div class="para">
+ RPM's freshen option checks the versions of the packages specified on the command line against the versions of packages that have already been installed on your system. When a newer version of an already-installed package is processed by RPM's freshen option, it is upgraded to the newer version. However, RPM's freshen option does not install a package if no previously-installed package of the same name exists. This differs from RPM's upgrade option, as an upgrade <span class="emphasis"><em>does</em></span> install packages whether or not an older version of the package was already installed.
+ </div><div class="para">
+ Freshening works for single packages or package groups. If you have just downloaded a large number of different packages, and you only want to upgrade those packages that are already installed on your system, freshening does the job. Thus, you do not have to delete any unwanted packages from the group that you downloaded before using RPM.
+ </div><div class="para">
+ In this case, issue the following with the <code class="filename">*.rpm</code> glob:
+ </div><pre class="screen">
+<code class="command">rpm -Fvh *.rpm</code>
+</pre><div class="para">
+ RPM 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>B.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-rpm-querying.html"><strong>次へ</strong>B.2.6. 問い合わせ</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-querying.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-querying.html
new file mode 100644
index 0000000..06df8b2
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-querying.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>B.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-rpm-using.html" title="B.2. RPMの使用法" /><link rel="prev" href="s2-rpm-freshening.html" title="B.2.5. インストール済みのアップグレードの実行" /><link rel="next" href="s2-rpm-verifying.html" title="B.2.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="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">B.2.6. 問い合わせ</h3></div></div></div><a id="idm58027328" class="indexterm"></a><a id="idm58025888" class="indexterm"></a><div class="para">
+ The RPM database stores information about all RPM packages installed in your system. It is stored in the directory <code class="filename">/var/lib/rpm/</code>, and is used to query what packages are installed, what versions each package is, and to calculate any changes to any files in the package since installation, among other use cases.
+ </div><div class="para">
+ To query this database, use the <code class="command">-q</code> option. The <code class="command">rpm -q <em class="replaceable"><code>package name</code></em> </code> command displays the package name, version, and release number of the installed package <em class="replaceable"><code><package_name></code></em>. For example, using <code class="command">rpm -q tree</code> to query installed package <code class="filename">tree</code> might generate the following output:
+ </div><pre class="screen">tree-1.5.2.2-4.fc17.x86_64</pre><div class="para">
+ You can also use the following <span class="emphasis"><em>Package Selection Options</em></span> (which is a subheading in the RPM man page: see <code class="command">man rpm</code> for details) to further refine or qualify your query:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-a</code> — 現在の全インストール済みパッケージの問い合わせです。
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f <code class="filename"><em class="replaceable"><code><file_name></code></em> </code> </code> — queries the RPM database for which package owns <code class="filename"><em class="replaceable"><code><file_name></code></em> </code>. Specify the absolute path of the file (for example, <code class="command">rpm -qf <code class="filename">/bin/ls</code> </code> instead of <code class="command">rpm -qf ls</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-p <code class="filename"><em class="replaceable"><code><package_file></code></em> </code> </code> — queries the uninstalled package <code class="filename"><em class="replaceable"><code><package_file></code></em> </code>.
+ </div></li></ul></div><div class="para">
+ There are a number of ways to specify what information to display about queried packages. The following options are used to select the type of information for which you are searching. These are called the <span class="emphasis"><em>Package Query Options</em></span>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-i</code> displays package information including name, description, release, size, build date, install date, vendor, and other miscellaneous information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-l</code> displays the list of files that the package contains.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-s</code> displays the state of all the files in the package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> displays a list of files marked as documentation (man pages, info pages, READMEs, etc.) in the package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-c</code> displays a list of files marked as configuration files. These are the files you edit after installation to adapt and customize the package to your system (for example, <code class="filename">sendmail.cf</code>, <code class="filename">passwd</code>, <code class="filename">inittab</code>, etc.).
+ </div></li></ul></div><div class="para">
+ For options that display lists of files, add <code class="command">-v</code> to the command to display the lists in a familiar <code class="command">ls -l</code> format.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-freshening.html"><strong>戻る</strong>B.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-rpm-verifying.html"><strong>次へ</strong>B.2.7. 検証</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-related-books.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-related-books.html
new file mode 100644
index 0000000..2d2ed47
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-related-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>B.5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-rpm-additional-resources.html" title="B.5. その他のリソース" /><link rel="prev" href="s2-rpm-useful-websites.html" title="B.5.2. 役に立つ Web サイト" /><link rel="next" href="ch-The_X_Window_System.html" title="付録C X Window 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="previous"><a accesskey="p" href="s2-rpm-useful-websites.html"><strong>戻る</strong></a></
li><li class="next"><a accesskey="n" href="ch-The_X_Window_System.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-rpm-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.5.3. 関連書籍</h3></div></div></div><a id="idm26503680" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <em class="citetitle">Maximum RPM</em> — <a href="http://www.rpm.org/max-rpm/">http://www.rpm.org/max-rpm/</a> </span></dt><dd><div class="para">
+ The <em class="citetitle">Maximum RPM</em> book, which you can read online, covers everything from general RPM usage to building your own RPMs to programming with rpmlib.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-useful-websites.html"><strong>戻る</strong>B.5.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-The_X_Window_System.html"><strong>次へ</strong>付録C X Window System</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-uninstalling.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-uninstalling.html
new file mode 100644
index 0000000..3a9323f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-uninstalling.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>B.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-rpm-using.html" title="B.2. RPMの使用法" /><link rel="prev" href="sec-Configuration_File_Changes.html" title="B.2.3. 設定ファイルの変更" /><link rel="next" href="s2-rpm-freshening.html" title="B.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="sec-Configuration_File_Changes.html">
<strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-freshening.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">B.2.4. アンインストール</h3></div></div></div><a id="idm35466528" class="indexterm"></a><a id="idm68475664" class="indexterm"></a><a id="idm68474224" class="indexterm"></a><a id="idm62945088" class="indexterm"></a><div class="para">
+ パッケージのアンインストールは、インストールと 同様、簡単に実行できます。シェルプロンプトで以下の コマンドを入力します。
+ </div><pre class="screen">rpm -e foo</pre><div class="note"><div class="admonition_header"><h2>rpm -e and package name errors</h2></div><div class="admonition"><div class="para">
+ Notice that we used the package <span class="emphasis"><em>name</em></span> <code class="filename">foo</code>, not the name of the original package <span class="emphasis"><em>file</em></span>, <code class="filename">foo-1.0-1.fc17.x86_64</code>. If you attempt to uninstall a package using the <code class="command">rpm -e</code> command and the original full file name, you will 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:
+ libgs.so.8()(64bit) is needed by (installed) libspectre-0.2.2-3.fc17.x86_64
+ libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc17.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc17.x86_64
+ ghostscript is needed by (installed) printer-filters-1.1-4.fc17.noarch</pre><div class="para">
+ Similar to how we searched for a shared object library (i.e. a <code class="filename"><em class="replaceable"><code><library_name></code></em>.so.<em class="replaceable"><code><number></code></em> </code> file) in <a class="xref" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">「未解決の依存性」</a>, we can search for a 64-bit shared object library using this exact syntax (and making sure to quote the file name):
+ </div><pre class="screen">~]# <code class="command">rpm -q --whatprovides "libgs.so.8()(64bit)"</code>
+ghostscript-8.70-1.fc17.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 we can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to remove a package that gives us a <code class="computeroutput">Failed dependencies</code> error (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended, and may cause harm to other installed applications. Installing or removing packages with <code class="command">rpm --nodeps</code> can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager—whether <span class="application"><strong>RPM</strong></span>, <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>—shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The <span class="application"><strong>Yum</strong><
/span> package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing <code class="command">rpm</code> to carry out actions without regard to resolving dependencies.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuration_File_Changes.html"><strong>戻る</strong>B.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-rpm-freshening.html"><strong>次へ</strong>B.2.5. インストール済みのアップグレードの実行</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-useful-websites.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-useful-websites.html
new file mode 100644
index 0000000..9516e49
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-useful-websites.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>B.5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-rpm-additional-resources.html" title="B.5. その他のリソース" /><link rel="prev" href="s1-rpm-additional-resources.html" title="B.5. その他のリソース" /><link rel="next" href="s2-rpm-related-books.html" title="B.5.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-rpm-additional-resources.html"><strong>戻る</strong></a></
li><li class="next"><a accesskey="n" href="s2-rpm-related-books.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-rpm-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.5.2. 役に立つ Web サイト</h3></div></div></div><div class="itemizedlist"><a id="idm68250512" class="indexterm"></a><ul><li class="listitem"><div class="para">
+ The RPM website — <a href="http://www.rpm.org/">http://www.rpm.org/</a>
+ </div></li><li class="listitem"><div class="para">
+ The RPM mailing list can be subscribed to, and its archives read from, here — <a href="http://www.redhat.com/mailman/listinfo/rpm-list/">https://lists.rpm.org/mailman/listinfo/rpm-list</a>
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-additional-resources.html"><strong>戻る</strong>B.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-rpm-related-books.html"><strong>次へ</strong>B.5.3. 関連書籍</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-verifying.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-verifying.html
new file mode 100644
index 0000000..925d3a7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-rpm-verifying.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>B.2.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-rpm-using.html" title="B.2. RPMの使用法" /><link rel="prev" href="s2-rpm-querying.html" title="B.2.6. 問い合わせ" /><link rel="next" href="s1-check-rpm-sig.html" title="B.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-rpm-querying.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="
n" href="s1-check-rpm-sig.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">B.2.7. 検証</h3></div></div></div><a id="idm33295520" class="indexterm"></a><a id="idm49575216" class="indexterm"></a><div class="para">
+ Verifying a package compares information about files installed from a package with the same information from the original package. Among other things, verifying compares the file size, MD5 sum, permissions, type, owner, and group of each file.
+ </div><div class="para">
+ The command <code class="command">rpm -V</code> verifies a package. You can use any of the <span class="emphasis"><em>Verify Options</em></span> listed for querying to specify the packages you wish to verify. A simple use of verifying is <code class="command">rpm -V tree</code>, which verifies that all the files in the <code class="command">tree</code> package are as they were when they were originally installed. For example:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 特定のファイルを含むパッケージを検証するには、
+ </div><pre class="screen">
+<code class="command">rpm -Vf /usr/bin/tree</code>
+</pre><div class="para">
+ In this example, <code class="filename">/usr/bin/tree</code> is the absolute path to the file used to query a package.
+ </div></li><li class="listitem"><div class="para">
+ To verify ALL installed packages throughout the system (which will take some time):
+ </div><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre></li><li class="listitem"><div class="para">
+ インストールされているパッケージと、 RPM パッケージファイルとを検証するには、
+ </div><pre class="screen">
+<code class="command">rpm -Vp tree-1.5.2.2-4.fc17.x86_64.rpm</code>
+</pre><div class="para">
+ This command can be useful if you suspect that your RPM database is corrupt.
+ </div></li></ul></div><div class="para">
+ If everything verified properly, there is no output. If there are any discrepancies, they are displayed. The format of the output is a string of eight characters (a "<code class="computeroutput">c</code>" denotes a configuration file) and then the file name. Each of the eight characters denotes the result of a comparison of one attribute of the file to the value of that attribute recorded in the RPM database. A single period (<code class="computeroutput">.</code>) means the test passed. The following characters denote specific discrepancies:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">5</code> — MD5 チェックサム
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">S</code> — ファイル サイズ
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">L</code> — シンボリック リンク
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">T</code> — ファイルの修正日時
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">D</code> — デバイス
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">U</code> — ユーザー
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">G</code> — グループ
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">M</code> — モード (パーミッションとファイルの種類を含む)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">?</code> — 読み込み不可ファイル (たとえばファイルのパーミッションエラー)
+ </div></li></ul></div><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>B.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-check-rpm-sig.html"><strong>次へ</strong>B.3. パッケージの署名を確認する</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-services-additional-resources-books.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-services-additional-resources-books.html
new file mode 100644
index 0000000..316b7e1
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>8.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-services-additional-resources.html" title="8.3. その他のリソース" /><link rel="prev" href="s1-services-additional-resources.html" title="8.3. その他のリソース" /><link rel="next" href="ch-Configuring_Authentication.html" title="第9章 認証の設定" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Configuring_Authentication.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">8.3.2. 関連書籍</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="citetitle">Fedora 17 セキュリティガイド</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>8.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-Configuring_Authentication.html"><strong>次へ</strong>第9章 認証の設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html
new file mode 100644
index 0000000..a5d75c9
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>10.4.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-ssh-beyondshell.html" title="10.4. 安全なシェル以上のもの" /><link rel="prev" href="s1-ssh-beyondshell.html" title="10.4. 安全なシェル以上のもの" /><link rel="next" href="s1-openssh-additional-resources.html" title="10.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-ssh-beyondshell.html"><strong>戻る</s
trong></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">10.4.2. ポート転送</h3></div></div></div><a id="idm54824144" 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">
+ 1024 以下のポートをリスンする為のポート転送をセットするには、 root レベルのアクセスが必要です。
+ </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>10.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-openssh-additional-resources.html"><strong>次へ</strong>10.5. 追加のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-clients-scp.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-clients-scp.html
new file mode 100644
index 0000000..3c9acf4
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>10.3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-ssh-clients.html" title="10.3. OpenSSH クライアント" /><link rel="prev" href="s1-ssh-clients.html" title="10.3. OpenSSH クライアント" /><link rel="next" href="s2-ssh-clients-sftp.html" title="10.3.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">10.3.2. <code class="command">scp</code> ユーティリティの使用方法</h3></div></div></div><a id="idm42568352" class="indexterm"></a><a id="idm50960656" class="indexterm"></a><a id="idm50958256" 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 john at penguin.example.com:.vim/plugin/taglist.vim</code>
+john at 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/* john at penguin.example.com:.vim/plugin/</code>
+john at 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 john at penguin.example.com:.vimrc .vimrc</code>
+john at 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>10.3. 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>10.3.3. sftp ユーティリティの使用方法</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-clients-sftp.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-clients-sftp.html
new file mode 100644
index 0000000..e7f82dd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>10.3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-ssh-clients.html" title="10.3. OpenSSH クライアント" /><link rel="prev" href="s2-ssh-clients-scp.html" title="10.3.2. scp ユーティリティの使用方法" /><link rel="next" href="s1-ssh-beyondshell.html" title="10.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-ssh-clients-scp.html"><strong>戻る</stro
ng></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">10.3.3. <code class="command">sftp</code> ユーティリティの使用方法</h3></div></div></div><a id="idm33999424" class="indexterm"></a><a id="idm39687424" 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">
+ たとえば、ユーザー名に <code class="systemitem">john</code> を用いて、<code class="systemitem">penguin.example.com</code> という名前のリモートマシンにログインするには、次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">sftp john at penguin.example.com</code>
+john at 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">表10.3「利用可能な sftp コマンドの選定品」</a>を参照してください）。
+ </div><div class="table" id="table-ssh-clients-sftp"><h6>表10.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">
+ 利用可能なコマンドの完全な一覧は <code class="command">sftp</code> のマニュアルページを参照してください。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-clients-scp.html"><strong>戻る</strong>10.3.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>10.4. 安全なシェル以上のもの</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html
new file mode 100644
index 0000000..3218054
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html
@@ -0,0 +1,127 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-ssh-configuration.html" title="10.2. OpenSSH の設定" /><link rel="prev" href="s2-ssh-configuration-requiring.html" title="10.2.3. リモート接続に対する SSH の要求" /><link rel="next" href="s1-ssh-clients.html" title="10.3. 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-ssh-configuration-requiring.html"><stron
g>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-ssh-clients.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">10.2.4. キー認証の使用</h3></div></div></div><a id="idm56904992" class="indexterm"></a><div class="para">
+ システムのセキュリティをさらに向上させるために、標準的なパスワード認証を無効にすることにより、キーによる認証を強制できます。そうするために、テキストエディターで <code class="filename">/etc/ssh/sshd_config</code> ファイルを開いて、<code class="option">PasswordAuthentication</code> オプションを以下のように変更します:
+ </div><pre class="programlisting">PasswordAuthentication no</pre><div class="para">
+ サーバーにクライアントから接続するために <code class="command">ssh</code>, <code class="command">scp</code>, や <code class="command">sftp</code> を使用できるようにするには、以下の手順に従って認可キーペアを生成します。キーは各ユーザーがそれぞれ生成しなければいけないことに注意してください。
+ </div><div class="para">
+ Fedora 17 はデフォルトで 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">
+ システムを再インストールして、前に生成したキーペアを維持したいならば、<code class="filename">~/.ssh/</code> ディレクトリをバックアップします。再インストール後、それをホームディレクトリにコピーして戻します。このプロセスは <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">10.2.4.1. 鍵ペアの生成</h4></div></div></div><a id="idm53357920" class="indexterm"></a><a id="idm56378864" class="indexterm"></a><div class="para">
+ SSH プロトコルバージョン 2 用の RSA キーペアを生成するには、これらの手順に従います:
+ </div><a id="idm56376352" 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/john/.ssh/id_rsa):</pre></li><li class="step"><div class="para">
+ 新しく作成するキーに対するデフォルトの位置（つまり、<code class="filename">~/.ssh/id_rsa</code>）を確認するために <span class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div class="para">
+ パスフレーズを入力して、プロンプトが出たとき再び入力することにより確認します。セキュリティの理由により、アカウントにログインするために使用するパスワードと同じものを使用することは避けます。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/id_rsa.
+Your public key has been saved in /home/john/.ssh/id_rsa.pub.
+The key fingerprint is:
+e7:97:c7:e2:0e:f9:0e:fc:c4:d7:cb:e5:31:11:92:14 john at 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">
+ <code class="filename">~/.ssh/</code> ディレクトリのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 755 ~/.ssh</code></pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/id_rsa.pub</code> の内容を接続したいサーバーの <code class="filename">~/.ssh/authorized_keys</code> の中にコピーします。もしファイルがすでに存在すれば、その最後に追加します。
+ </div></li><li class="step"><div class="para">
+ 以下のコマンドを用いて <code class="filename">~/.ssh/authorized_keys</code> ファイルのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><a id="idm65632816" class="indexterm"></a><a id="idm65631376" class="indexterm"></a><div class="para">
+ SSH プロトコルバージョン 2 用の DSA キーペアを生成するには、これらの手順に従います:
+ </div><a id="idm65628864" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ シェルプロンプトにおいて以下のとおり入力することにより DSA キーペアを生成します:
+ </div><pre class="screen">~]$ <code class="command">ssh-keygen -t dsa</code>
+Generating public/private dsa key pair.
+Enter file in which to save the key (/home/john/.ssh/id_dsa):</pre></li><li class="step"><div class="para">
+ 新しく作成するキーに対するデフォルトの位置（つまり、<code class="filename">~/.ssh/id_dsa</code>）を確認するために <span class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div class="para">
+ パスフレーズを入力して、プロンプトが出たとき再び入力することにより確認します。セキュリティの理由により、アカウントにログインするために使用するパスワードと同じものを使用することは避けます。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/id_dsa.
+Your public key has been saved in /home/john/.ssh/id_dsa.pub.
+The key fingerprint is:
+81:a1:91:a8:9f:e8:c5:66:0d:54:f5:90:cc:bc:cc:27 john at penguin.example.com
+The key's randomart image is:
++--[ DSA 1024]----+
+| .oo*o. |
+| ...o Bo |
+| .. . + o. |
+|. . E o |
+| o..o S |
+|. o= . |
+|. + |
+| . |
+| |
++-----------------+</pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/</code> ディレクトリのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 775 ~/.ssh</code></pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/id_dsa.pub</code> の内容を接続したいサーバーの <code class="filename">~/.ssh/authorized_keys</code> の中にコピーします。もしファイルがすでに存在すれば、その最後に追加します。
+ </div></li><li class="step"><div class="para">
+ 以下のコマンドを用いて <code class="filename">~/.ssh/authorized_keys</code> ファイルのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><a id="idm56130672" class="indexterm"></a><a id="idm56129264" class="indexterm"></a><div class="para">
+ SSH プロトコルバージョン 1 用の R\nSA キーペアを生成するには、これらの手順に従います:
+ </div><a id="idm51430160" 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 rsa1</code>
+Generating public/private rsa1 key pair.
+Enter file in which to save the key (/home/john/.ssh/identity):</pre></li><li class="step"><div class="para">
+ 新しく作成するキーに対するデフォルトの位置（つまり、<code class="filename">~/.ssh/identity</code>）を確認するために <span class="keycap"><strong>Enter</strong></span> を押します。
+ </div></li><li class="step"><div class="para">
+ パスフレーズを入力して、そうするようプロンプトが表示されたとき、入力することによりそれを確認します。セキュリティの理由のため、あたなのアカウントにログインするために使用するものと同じパスワードを使用することは避けてください。
+ </div><div class="para">
+ この後、これと同じようなメッセージが表示されます:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/identity.
+Your public key has been saved in /home/john/.ssh/identity.pub.
+The key fingerprint is:
+cb:f6:d5:cb:6e:5f:2b:28:ac:17:0c:e4:62:e4:6f:59 john at penguin.example.com
+The key's randomart image is:
++--[RSA1 2048]----+
+| |
+| . . |
+| o o |
+| + o E |
+| . o S |
+| = + . |
+| . = . o . .|
+| . = o o..o|
+| .o o o=o.|
++-----------------+</pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/</code> ディレクトリのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 755 ~/.ssh</code></pre></li><li class="step"><div class="para">
+ <code class="filename">~/.ssh/identity.pub</code> の内容を接続したいサーバーの <code class="filename">~/.ssh/authorized_keys</code> の中にコピーします。もしファイルがすでに存在すれば、その最後に追加します。
+ </div></li><li class="step"><div class="para">
+ 以下のコマンドを用いて <code class="filename">~/.ssh/authorized_keys</code> ファイルのパーミッションを変更します:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><div class="para">
+ システムにパスフレーズを記憶させる方法については<a class="xref" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">「ssh-agent の設定」</a>を参照してください。
+ </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">10.2.4.2. ssh-agent の設定</h4></div></div></div><a id="idm31374160" class="indexterm"></a><a id="idm31372240" class="indexterm"></a><a id="idm48168128" class="indexterm"></a><a id="idm48166208" 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/john/.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>10.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="s1-ssh-clients.html"><strong>次へ</strong>10.3. OpenSSH クライアント</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html
new file mode 100644
index 0000000..efc4445
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>10.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-ssh-configuration.html" title="10.2. OpenSSH の設定" /><link rel="prev" href="s2-ssh-configuration-sshd.html" title="10.2.2. OpenSSH サーバーの起動" /><link rel="next" href="s2-ssh-configuration-keypairs.html" title="10.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-ssh-configuration-sshd.html"><strong>戻る</str
ong></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">10.2.3. リモート接続に対する SSH の要求</h3></div></div></div><a id="idm43701792" class="indexterm"></a><a id="idm43700384" 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">
+ これらのサービスが実行していないことを確実にするには、シェルプロンプトにおいて以下のコマンドを入力します:
+ </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">
+ Fedora において、サービスを設定する方法の詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-sshd.html"><strong>戻る</strong>10.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>10.2.4. キー認証の使用</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html
new file mode 100644
index 0000000..c052b1f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-ssh-configuration-sshd.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>10.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-ssh-configuration.html" title="10.2. OpenSSH の設定" /><link rel="prev" href="s1-ssh-configuration.html" title="10.2. OpenSSH の設定" /><link rel="next" href="s2-ssh-configuration-requiring.html" title="10.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>戻る</str
ong></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">10.2.2. OpenSSH サーバーの起動</h3></div></div></div><a id="idm61716624" class="indexterm"></a><div class="note"><div class="admonition_header"><h2>関連パッケージがインストールされていることを確実にします。</h2></div><div class="admonition"><div class="para">
+ OpenSSH サーバーを実行するには、<span class="package">openssh-server</span> および <span class="package">openssh</span> パッケージがインストールされていなければいけません。Fedora において新しいパッケージをインストールする方法の詳細は<a class="xref" href="sec-Installing.html">「パッケージのインストール」</a>を参照してください。
+ </div></div></div><a id="idm57133488" class="indexterm"></a><div class="para">
+ <code class="command">sshd</code> デーモンを起動するには、シェルプロンプトにおいて以下のとおり入力します。
+ </div><pre class="screen"><code class="command">systemctl start sshd.service</code></pre><a id="idm57129904" class="indexterm"></a><div class="para">
+ 実行中の <code class="command">sshd</code> デーモンを停止するには、以下のコマンドを使用します:
+ </div><pre class="screen"><code class="command">systemctl stop sshd.service</code></pre><div class="para">
+ ブート時にデーモンが自動的に起動するようにしたいならば、以下を入力します:
+ </div><pre class="screen"><code class="command">systemctl enable sshd.service</code></pre><div class="para">
+ Fedora において、サービスを設定する方法の詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </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">
+ これを防ぐには、<code class="filename">/etc/ssh/</code> ディレクトリから関連するファイルをバックアップできます (完全な一覧は <a class="xref" href="s1-ssh-configuration.html#table-ssh-configuration-configs-system">表10.1「システム全体の設定ファイル」</a> を参照してください)、そうするとシステムを再インストールしたときはそれらをリストアできます。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ssh-configuration.html"><strong>戻る</strong>10.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-requiring.html"><strong>次へ</strong>10.2.3. リモート接続に対する SSH の要求</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html
new file mode 100644
index 0000000..03f6e2f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm55515152" 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/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html
new file mode 100644
index 0000000..fd918f4
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm25934688" 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="idm65571024" class="indexterm"></a><a id="idm62180640" class="indexterm"></a><a id="idm62179520" class="indexterm"></a><a id="idm62177472" class="indexterm"></a><a id="idm54705760" class="indexterm"></a><a id="idm54703712" 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/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html
new file mode 100644
index 0000000..4120044
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm32711472" 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/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html
new file mode 100644
index 0000000..243a133
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm66814784" 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/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html
new file mode 100644
index 0000000..06b4940
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm16698608" 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/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html
new file mode 100644
index 0000000..1d730d9
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm69807664" class="indexterm"></a><a id="idm69806544" 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/17/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html
new file mode 100644
index 0000000..b6fde57
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm48124992" 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/17/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html
new file mode 100644
index 0000000..ef62835
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm28048464" 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/17/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html
new file mode 100644
index 0000000..994795a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm53959520" 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/17/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html
new file mode 100644
index 0000000..1a43c18
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="idm43487824" class="indexterm"></a><a id="idm49741200" 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/17/html/System_Administrators_Guide/s2-users-tools-groups-add.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-users-tools-groups-add.html
new file mode 100644
index 0000000..c093864
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>3.4.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-users-tools.html" title="3.4. コマンドラインのツールを使う" /><link rel="prev" href="s1-users-tools.html" title="3.4. コマンドラインのツールを使う" /><link rel="next" href="s2-users-tools-password-aging.html" title="3.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="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">3.4.2. 新規グループを追加する</h3></div></div></div><a id="idm74858080" class="indexterm"></a><a id="idm69168416" 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">
+ …ここで <em class="replaceable"><code>options</code></em> は<a class="xref" href="s2-users-tools-groups-add.html#table-groupadd-options">表3.3「groupadd のコマンドライン オプション」</a>に説明されているコマンドラインオプションです。
+ </div><div class="table" id="table-groupadd-options"><h6>表3.3 groupadd のコマンドライン オプション</h6><div class="table-contents"><table summary="groupadd のコマンドライン オプション" 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="">
+ 重複したグループの作成を許可します。
+ </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>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="s2-users-tools-password-aging.html"><strong>次へ</strong>3.4.3. パスワードエージングの有効化</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-users-tools-groups-directories.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-users-tools-groups-directories.html
new file mode 100644
index 0000000..f80a69a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-users-tools-groups-directories.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.4.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-users-tools.html" title="3.4. コマンドラインのツールを使う" /><link rel="prev" href="s2-users-tools-users-logout.html" title="3.4.4. 自動ログアウトの有効化" /><link rel="next" href="s1-users-groups-additional-resources.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="s2-users-tools-users-
logout.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-users-groups-additional-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">3.4.5. グループ用ディレクトリーの作成</h3></div></div></div><a id="idm69870000" class="indexterm"></a><a id="idm25732160" class="indexterm"></a><div class="para">
+ システム管ç†è€…ã¯é€šå¸¸ã€ä¸»è¦ãªå„プãƒã‚¸ã‚§ã‚¯ãƒˆã«å¯¾ã™ã‚‹ã‚°ãƒ«ãƒ¼ãƒ—を作æˆã—ã¦ã€ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚¢ã‚¯ã‚»ã‚¹ãŒå¿…è¦ãªã¨ãã«ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’グループã«å‰²ã‚Šå½“ã¦ãŸã„ã¨è€ƒãˆã¾ã™ã€‚ã“ã®ä¼çµ±çš„ãªã‚¹ã‚ーマを用ã„ã‚‹ã¨ã€ãƒ•ã‚¡ã‚¤ãƒ«ç®¡ç†ã¯é›£ã—ã„ã§ã™ã€‚誰ã‹ãŒãƒ•ã‚¡ã‚¤ãƒ«ã‚’作æˆã™ã‚‹ã¨ãã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒå±žã—ã¦ã„るプライマリグループã¨é–¢é€£ã¥ã‘られã¾ã™ã€‚一人ãŒè¤‡æ•°ã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã«ãŠã„ã¦ä»•äº‹ã‚’ã—ã¦ã„ã‚‹ã¨ãã€æ£ã—ã„ファイルã¨æ£ã—ã„グループを関連ã¥ã‘ã‚‹ã“ã¨ã¯é›£ã—ã„ã§ã™ã€‚ã—ã‹ã—ãªãŒã‚‰ã€UPG スã‚ーマを用ã„ã‚‹ã¨ã€ã‚°ãƒ«ãƒ¼ãƒ—ã¯è‡ªå‹•çš„ã« <em class="firstterm">setgid</em> ビットãŒè¨å®šã•ã‚ŒãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã®ä¸ã«ä½œæˆã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã«å‰²ã‚Šå½“ã¦ã‚‰ã‚Œã¾ã™ã€‚ãã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã®ä¸ã«ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒä½œæˆã™ã‚‹ã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¤ãƒ«ã¯ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã‚’所有ã—ã¦ã„ã‚‹ã‚°ã
ƒ«ãƒ¼ãƒ—ã«ã‚ˆã‚Šæ‰€æœ‰ã•ã‚Œã‚‹ã®ã§ã€setgid ビットã¯å…±é€šã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã‚’共有ã™ã‚‹ã‚°ãƒ«ãƒ¼ãƒ—プãƒã‚¸ã‚§ã‚¯ãƒˆã®ç®¡ç†ã‚’éžå¸¸ã«ã‚·ãƒ³ãƒ—ルã«ã—ã¾ã™ã€‚
+ </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">
+ ユーザーがディレクトリの中にファイルを作成できるようして、setgid ビットを設定します:
+ </div><pre class="screen"><code class="command">chmod 2775 /opt/myproject</code></pre></li></ol></div><div class="para">
+ ここで、<code class="systemitem">myproject</code> グループのすべてのメンバーは、ユーザーが新しいファイルを作成するときはいつでも管理者がファイルのパーミッションを変更する必要がなく、<code class="filename">/opt/myproject/</code> ディレクトリにファイルを作成および編集できます。パーミッションが正しく設定されていることを確認するには、以下のコマンドを実行してください:
+ </div><pre class="screen">~]# <code class="command">ls -l /opt</code>
+total 4
+drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 myproject</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-users-tools-users-logout.html"><strong>戻る</strong>3.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="s1-users-groups-additional-resources.html"><strong>次へ</strong>3.5. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-users-tools-password-aging.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-users-tools-password-aging.html
new file mode 100644
index 0000000..6f7a3f3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-users-tools.html" title="3.4. コマンドラインのツールを使う" /><link rel="prev" href="s2-users-tools-groups-add.html" title="3.4.2. 新規グループを追加する" /><link rel="next" href="s2-users-tools-users-logout.html" title="3.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-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">3.4.3. パスワードエージングの有効化</h3></div></div></div><a id="idm52591216" class="indexterm"></a><a id="idm52589776" class="indexterm"></a><a id="idm52588336" class="indexterm"></a><a id="idm49984448" class="indexterm"></a><a id="idm49982720" class="indexterm"></a><div class="para">
+ セキュリティの理由から、ユーザーがパスワードを定期的に変更するよう要求することをお勧めします。<span class="application"><strong>ユーザーの管理</strong></span>アプリケーションの<span class="guilabel"><strong>パスワード情報</strong></span>タブにおいてユーザーを追加または編集するときに、または <code class="command">chage</code> コマンドを使用することにより、これを実行できます。
+ </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="idm33255648" 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">表3.4「chhage のコマンドライン オプション」</a>において説明されているコマンドラインオプションです。<code class="command">chage</code> コマンドが直接ユーザー名を引数としているとき (つまり、コマンドラインオプションを何も指定していないとき)、現在のパスワードエージング値が表示され、対話的に変更することができます。
+ </div><div class="table" id="table-chage-options"><h6>表3.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>3.4.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>3.4.4. 自動ログアウトの有効化</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-users-tools-users-logout.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-users-tools-users-logout.html
new file mode 100644
index 0000000..6462153
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-users-tools.html" title="3.4. コマンドラインのツールを使う" /><link rel="prev" href="s2-users-tools-password-aging.html" title="3.4.3. パスワードエージングの有効化" /><link rel="next" href="s2-users-tools-groups-directories.html" title="3.4.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">3.4.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">yum</code> <code class="option">install</code> <code class="option">screen</code></pre><div class="para">
+ Fedora にパッケージをインストールする方法の詳細は、<a class="xref" href="sec-Installing.html">「パッケージのインストール」</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>3.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-groups-directories.html"><strong>次へ</strong>3.4.5. グループ用ディレクトリーの作成</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-clients-winmanagers.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-clients-winmanagers.html
new file mode 100644
index 0000000..c31f73a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-clients-winmanagers.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>C.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-x-clients.html" title="C.2. デスクトップ環境とウィンドウマネージャ" /><link rel="prev" href="s1-x-clients.html" title="C.2. デスクトップ環境とウィンドウマネージャ" /><link rel="next" href="s1-x-server-configuration.html" title="C.3. X サーバー設定ファイル" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x
-clients.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-x-server-configuration.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-x-clients-winmanagers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.2.2. ウィンドウマネージャ</h3></div></div></div><a id="idm42403408" class="indexterm"></a><a id="idm42401776" class="indexterm"></a><a id="idm51803616" class="indexterm"></a><a id="idm51801024" class="indexterm"></a><a id="idm51798432" class="indexterm"></a><a id="idm39414240" class="indexterm"></a><a id="idm39411648" class="indexterm"></a><a id="idm39409536" class="indexterm"></a><a id="idm18676176" class="indexterm"></a><a id="idm18674064" class="indexterm"></a><div class="para">
+ <em class="firstterm">ウィンドウマネージャ</em> は、 X クライアントプログラムであり、デスクトップ環境の一部、または場合によってはスタンドアローンのこともあります。その主要目的はグラフィカルウィンドウの配置、サイズ変更、移動などを制御することです。ウィンドウマネージャは、タイトルバー、ウィンドウの焦点調節、ユーザー設定のキーやマウスボタンの連携なども制御します。
+ </div><div class="para">
+ The Fedora repositories provide five different window managers:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="command">metacity</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Metacity</em> window manager is the default window manager for GNOME. It is a simple and efficient window manager which supports custom themes. This window manager is automatically pulled in as a dependency when the GNOME desktop is installed.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">kwin</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">KWin</em> window manager is the default window manager for KDE. It is an efficient window manager which supports custom themes. This window manager is automatically pulled in as a dependency when the KDE desktop is installed.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">compiz</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Compiz</em> compositing window manager is based on OpenGL and can use 3D graphics hardware to create fast compositing desktop effects for window management. Advanced features, such as a cube workspace, are implemented as loadable plug-ins. To run this window manager, you need to install the <code class="filename">compiz</code> package.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">mwm</code></span></dt><dd><div class="para">
+ The <em class="firstterm">Motif Window Manager</em> (<code class="command">mwm</code>) is a basic, stand-alone window manager. Since it is designed to be stand-alone, it should not be used in conjunction with GNOME or KDE. To run this window manager, you need to install the <code class="filename">openmotif</code> package.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">twm</code></span></dt><dd><div class="para">
+ The minimalist <em class="firstterm">Tab Window Manager</em> (<code class="command">twm</code>), which provides the most basic tool set among the available window managers, can be used either as a stand-alone or with a desktop environment. To run this window manager, you need to install the <code class="filename">xorg-x11-twm</code> package.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-clients.html"><strong>戻る</strong>C.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-x-server-configuration.html"><strong>次へ</strong>C.3. X サーバー設定ファイル</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-server-config-xorg.conf.d.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-server-config-xorg.conf.d.html
new file mode 100644
index 0000000..8533ddf
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-server-config-xorg.conf.d.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>C.3.2. The xorg.conf.d 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-x-server-configuration.html" title="C.3. X サーバー設定ファイル" /><link rel="prev" href="s1-x-server-configuration.html" title="C.3. X サーバー設定ファイル" /><link rel="next" href="s2-x-server-config-xorg.conf.html" title="C.3.3. The xorg.conf 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-x-server-configuration.html"><stro
ng>戻る</strong></a></li><li class="next"><a accesskey="n" href="s2-x-server-config-xorg.conf.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-x-server-config-xorg.conf.d"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.3.2. The <code class="filename">xorg.conf.d</code> Directory</h3></div></div></div><a id="idm47411744" class="indexterm"></a><a id="idm47409152" class="indexterm"></a><a id="idm47407040" class="indexterm"></a><div class="para">
+ The X server supports two configuration directories. The <code class="filename">/usr/share/X11/xorg.conf.d/</code> provides separate configuration files from vendors or third-party packages; changes to files in this directory may be overwritten by settings specified in the <code class="filename">/etc/X11/xorg.conf</code> file. The <code class="filename">/etc/X11/xorg.conf.d/</code> directory stores user-specific configuration.
+ </div><div class="para">
+ Files with the suffix <code class="filename">.conf</code> in configuration directories are parsed by the X server upon startup and are treated like part of the traditional <code class="filename">xorg.conf</code> configuration file. These files may contain one or more sections; for a description of the options in a section and the general layout of the configuration file, refer to <a class="xref" href="s2-x-server-config-xorg.conf.html">「The <code class="filename">xorg.conf</code> File」</a> or to the <code class="systemitem">xorg.conf(5)</code> man page. The X server essentially treats the collection of configuration files as one big file with entries from <code class="filename">xorg.conf</code> at the end. Users are encouraged to put custom configuration into <code class="filename">/etc/xorg.conf</code> and leave the directory for configuration snippets provided by the distribution.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-server-configuration.html"><strong>戻る</strong>C.3. X サーバー設定ファイル</a></li><li class="up"><a accesskey="u" href="#"><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-x-server-config-xorg.conf.html"><strong>次へ</strong>C.3.3. The xorg.conf File</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-server-config-xorg.conf.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-server-config-xorg.conf.html
new file mode 100644
index 0000000..363f7ee
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-server-config-xorg.conf.html
@@ -0,0 +1,242 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.3.3. The xorg.conf 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-x-server-configuration.html" title="C.3. X サーバー設定ファイル" /><link rel="prev" href="s2-x-server-config-xorg.conf.d.html" title="C.3.2. The xorg.conf.d Directory" /><link rel="next" href="s1-x-fonts.html" title="C.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-x-server-config-xorg.conf.d.html"><strong>戻る</strong></a
></li><li class="next"><a accesskey="n" href="s1-x-fonts.html"><strong>次へ</strong></a></li></ul><div class="section" id="s2-x-server-config-xorg.conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.3.3. The <code class="filename">xorg.conf</code> File</h3></div></div></div><a id="idm68478032" class="indexterm"></a><a id="idm50984448" class="indexterm"></a><a id="idm50982336" class="indexterm"></a><div class="para">
+ In previous releases of the X Window System, <code class="filename">/etc/X11/xorg.conf</code> file was used to store initial setup for X. When a change occurred with the monitor, video card or other device managed by the X server, the file needed to be edited manually. In Fedora, there is rarely a need to manually create and edit the <code class="filename">/etc/X11/xorg.conf</code> file. Nevertheless, it is still useful to understand various sections and optional parameters available, especially when troubleshooting or setting up unusual hardware configuration.
+ </div><div class="para">
+ In the following, some important sections are described in the order in which they appear in a typical <code class="filename">/etc/X11/xorg.conf</code> file. More detailed information about the X server configuration file can be found in the <code class="filename">xorg.conf(5)</code> man page. This section is mostly intended for advanced users as most configuration options described below are not needed in typical configuration scenarios.
+ </div><div class="section" id="s3-x-server-config-xorg.conf.d-inputclass"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.1. The <code class="option">InputClass</code> section</h4></div></div></div><div class="para">
+ <code class="option">InputClass</code> is a new type of configuration section that does not apply to a single device but rather to a class of devices, including hot-plugged devices. An <code class="option">InputClass</code> section's scope is limited by the matches specified; in order to apply to an input device, all matches must apply to the device as seen in the example below:
+ </div><pre class="screen">Section "InputClass"
+ Identifier "touchpad catchall"
+ MatchIsTouchpad "on"
+ Driver "synaptics"
+EndSection</pre><div class="para">
+ If this snippet is present in an <code class="filename">xorg.conf</code> file or an <code class="filename">xorg.conf.d</code> directory, any touchpad present in the system is assigned the <code class="systemitem">synaptics</code> driver.
+ </div><div class="note"><div class="admonition_header"><h2>Alphanumeric sorting in <code class="filename">xorg.conf.d</code></h2></div><div class="admonition"><div class="para">
+ Note that due to alphanumeric sorting of configuration files in the <code class="filename">xorg.conf.d</code> directory, the <code class="option">Driver</code> setting in the example above overwrites previously set driver options. The more generic the class, the earlier it should be listed.
+ </div></div></div><div class="para">
+ The match options specify which devices a section may apply to. To match a device, all match options must correspond. The following options are commonly used in the <code class="option">InputClass</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">MatchIsPointer</code>, <code class="option">MatchIsKeyboard</code>, <code class="option">MatchIsTouchpad</code>, <code class="option">MatchIsTouchscreen</code>, <code class="option">MatchIsJoystick</code> — boolean options to specify a type of a device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">MatchProduct "<em class="replaceable"><code>product_name</code></em>"</code> — this option matches if the <em class="replaceable"><code>product_name</code></em> substring occurs in the product name of the device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">MatchVendor "<em class="replaceable"><code>vendor_name</code></em>"</code> — this option matches if the <em class="replaceable"><code>vendor_name</code></em> substring occurs in the vendor name of the device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">MatchDevicePath "<em class="replaceable"><code>/path/to/device</code></em>"</code> — this option matches any device if its device path corresponds to the patterns given in the "<em class="replaceable"><code>/path/to/device</code></em>" template, for example <code class="literal">/dev/input/event*</code>. Refer to the <code class="command">fnmatch(3)</code> man page for further details.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">MatchTag "<em class="replaceable"><code>tag_pattern</code></em>"</code> — this option matches if at least one tag assigned by the HAL configuration back end matches the <em class="replaceable"><code>tag_pattern</code></em> pattern.
+ </div></li></ul></div><div class="para">
+ A configuration file may have multiple <code class="option">InputClass</code> sections. These sections are optional and are used to configure a class of input devices as they are automatically added. An input device can match more than one <code class="option">InputClass</code> section. When arranging these sections, it is recommended to put generic matches above specific ones because each input class can override settings from a previous one if an overlap occurs.
+ </div></div><div class="section" id="s3-x-server-config-xorg.conf-inputd"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.2. The <code class="option">InputDevice</code> section</h4></div></div></div><a id="idm69016496" class="indexterm"></a><div class="para">
+ Each <code class="option">InputDevice</code> section configures one input device for the X server. Previously, systems typically had at least one <code class="option">InputDevice</code> section for the keyboard, and most mouse settings were automatically detected.
+ </div><div class="para">
+ With Fedora 17, no <code class="option">InputDevice</code> configuration is needed for most setups, and the <span class="package">xorg-x11-drv-*</span> input driver packages provide the automatic configuration through HAL. The default driver for both keyboards and mice is <code class="literal">evdev</code>.
+ </div><div class="para">
+ The following example shows a typical <code class="option">InputDevice</code> section for a keyboard:
+ </div><pre class="screen">Section "InputDevice"
+ Identifier "Keyboard0"
+ Driver "kbd"
+ Option "XkbModel" "pc105"
+ Option "XkbLayout" "us"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">InputDevice</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">InputDevice</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Driver</code> — Specifies the name of the device driver X must load for the device. If the <code class="option">AutoAddDevices</code> option is enabled (which is the default setting), any input device section with <code class="option">Driver "mouse"</code> or <code class="option">Driver "kbd"</code> will be ignored. This is necessary due to conflicts between the legacy mouse and keyboard drivers and the new <code class="literal">evdev</code> generic driver. Instead, the server will use the information from the back end for any input devices. Any custom input device configuration in the <code class="filename">xorg.conf</code> should be moved to the back end. In most cases, the back end will be HAL and the configuration location will be the <code class="filename">/etc/X11/xorg.conf.d</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option</code> — Specifies necessary options pertaining to the device.
+ </div><div class="para">
+ A mouse may also be specified to override any auto-detected values for the device. The following options are typically included when adding a mouse in the <code class="filename">xorg.conf</code> file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Protocol</code> — Specifies the protocol used by the mouse, such as <code class="literal">IMPS/2</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Device</code> — Specifies the location of the physical device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Emulate3Buttons</code> — Specifies whether to allow a two-button mouse to act like a three-button mouse when both mouse buttons are pressed simultaneously.
+ </div></li></ul></div><div class="para">
+ Consult the <code class="filename">xorg.conf(5)</code> man page for a complete list of valid options for this section.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-serverf"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.3. The <code class="option">ServerFlags</code> section</h4></div></div></div><a id="idm32673792" class="indexterm"></a><div class="para">
+ The optional <code class="option">ServerFlags</code> section contains miscellaneous global X server settings. Any settings in this section may be overridden by options placed in the <code class="option">ServerLayout</code> section (refer to <a class="xref" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-serverl">「<code class="option">ServerLayout</code>」</a> for details).
+ </div><div class="para">
+ Each entry within the <code class="option">ServerFlags</code> section occupies a single line and begins with the term <code class="option">Option</code> followed by an option enclosed in double quotation marks (<code class="literal">"</code>).
+ </div><div class="para">
+ The following is a sample <code class="option">ServerFlags</code> section:
+ </div><pre class="screen">Section "ServerFlags"
+ Option "DontZap" "true"
+EndSection</pre><div class="para">
+ 特に役立つオプションの幾つかを以下に一覧表示します：
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">"DontZap" "<em class="replaceable"><code>boolean</code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to <code class="literal">true</code>, this setting prevents the use of the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Backspace</strong></span> key combination to immediately terminate the X server.
+ </div><div class="note"><div class="admonition_header"><h2>X keyboard extension</h2></div><div class="admonition"><div class="para">
+ Even if this option is enabled, the key combination still must be configured in the X Keyboard Extension (XKB) map before it can be used. One way how to add the key combination to the map is to run the following command:
+<pre class="screen"><code class="command">setxkbmap -option "terminate:ctrl_alt_bksp"</code></pre>
+
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">"DontZoom" "<em class="replaceable"><code>boolean</code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to <code class="literal">true</code>, this setting prevents cycling through configured video resolutions using the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Keypad-Plus</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Keypad-Minus</strong></span> key combinations.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">"AutoAddDevices" "<em class="replaceable"><code>boolean</code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to <code class="literal">false</code>, the server will not hot plug input devices and instead rely solely on devices configured in the <code class="filename">xorg.conf</code> file. Refer to <a class="xref" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-inputd">「The <code class="option">InputDevice</code> section」</a> for more information concerning input devices. This option is enabled by default and HAL (hardware abstraction layer) is used as a back end for device discovery.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-serverl"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.4. <code class="option">ServerLayout</code></h4></div></div></div><a id="idm57069440" class="indexterm"></a><div class="para">
+ The <code class="option">ServerLayout</code> section binds together the input and output devices controlled by the X server. At a minimum, this section must specify one input device and one output device. By default, a monitor (output device) and a keyboard (input device) are specified.
+ </div><div class="para">
+ The following example shows a typical <code class="option">ServerLayout</code> section:
+ </div><pre class="screen">Section "ServerLayout"
+ Identifier "Default Layout"
+ Screen 0 "Screen0" 0 0
+ InputDevice "Mouse0" "CorePointer"
+ InputDevice "Keyboard0" "CoreKeyboard"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">ServerLayout</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">ServerLayout</code> section.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Screen</code> — Specifies the name of a <code class="option">Screen</code> section to be used with the X server. More than one <code class="option">Screen</code> option may be present.
+ </div><div class="para">
+ The following is an example of a typical <code class="option">Screen</code> entry:
+ </div><pre class="screen">Screen 0 "Screen0" 0 0</pre><div class="para">
+ The first number in this example <code class="option">Screen</code> entry (<code class="literal">0</code>) indicates that the first monitor connector, or <em class="firstterm">head</em> on the video card, uses the configuration specified in the <code class="option">Screen</code> section with the identifier <code class="option">"Screen0"</code>.
+ </div><div class="para">
+ An example of a <code class="option">Screen</code> section with the identifier <code class="option">"Screen0"</code> can be found in <a class="xref" href="s2-x-server-config-xorg.conf.html#s3-x-server-config-xorg.conf-screen">「The <code class="option">Screen</code> section」</a>.
+ </div><div class="para">
+ If the video card has more than one head, another <code class="option">Screen</code> entry with a different number and a different <code class="option">Screen</code> section identifier is necessary.
+ </div><div class="para">
+ The numbers to the right of <code class="option">"Screen0"</code> give the absolute X and Y coordinates for the upper left corner of the screen (<code class="literal">0 0</code> by default).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">InputDevice</code> — Specifies the name of an <code class="option">InputDevice</code> section to be used with the X server.
+ </div><div class="para">
+ It is advisable that there be at least two <code class="option">InputDevice</code> entries: one for the default mouse and one for the default keyboard. The options <code class="option">CorePointer</code> and <code class="option">CoreKeyboard</code> indicate that these are the primary mouse and keyboard. If the <code class="option">AutoAddDevices</code> option is enabled, this entry needs not to be specified in the <code class="option">ServerLayout</code> section. If the <code class="option">AutoAddDevices</code> option is disabled, both mouse and keyboard are auto-detected with the default values.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option "<em class="replaceable"><code>option-name</code></em>"</code> — An optional entry which specifies extra parameters for the section. Any options listed here override those listed in the <code class="option">ServerFlags</code> section.
+ </div><div class="para">
+ Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf(5)</code> man page.
+ </div></li></ul></div><div class="para">
+ It is possible to put more than one <code class="option">ServerLayout</code> section in the <code class="filename">/etc/X11/xorg.conf</code> file. By default, the server only reads the first one it encounters, however. If there is an alternative <code class="option">ServerLayout</code> section, it can be specified as a command line argument when starting an X session; as in the <code class="command">Xorg -layout <layoutname></code> command.
+ </div></div><div class="section" id="s3-x-server-config-xorg.conf-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.5. The <code class="option">Files</code> section</h4></div></div></div><a id="idm61812800" class="indexterm"></a><div class="para">
+ The <code class="option">Files</code> section sets paths for services vital to the X server, such as the font path. This is an optional section, as these paths are normally detected automatically. This section can be used to override automatically detected values.
+ </div><div class="para">
+ The following example shows a typical <code class="option">Files</code> section:
+ </div><pre class="screen">Section "Files"
+ RgbPath "/usr/share/X11/rgb.txt"
+ FontPath "unix/:7100"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">Files</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">ModulePath</code> — An optional parameter which specifies alternate directories which store X server modules.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.6. The <code class="option">Monitor</code> section</h4></div></div></div><a id="idm35489136" class="indexterm"></a><div class="para">
+ Each <code class="option">Monitor</code> section configures one type of monitor used by the system. This is an optional entry as most monitors are now detected automatically.
+ </div><div class="para">
+ This example shows a typical <code class="option">Monitor</code> section for a monitor:
+ </div><pre class="screen">Section "Monitor"
+ Identifier "Monitor0"
+ VendorName "Monitor Vendor"
+ ModelName "DDC Probed Monitor - ViewSonic G773-2"
+ DisplaySize 320 240
+ HorizSync 30.0 - 70.0
+ VertRefresh 50.0 - 180.0
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">Monitor</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">Monitor</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">VendorName</code> — An optional parameter which specifies the vendor of the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ModelName</code> — An optional parameter which specifies the monitor's model name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">DisplaySize</code> — An optional parameter which specifies, in millimeters, the physical size of the monitor's picture area.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">HorizSync</code> — Specifies the range of horizontal sync frequencies compatible with the monitor, in kHz. These values help the X server determine the validity of built-in or specified <code class="option">Modeline</code> entries for the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">VertRefresh</code> — Specifies the range of vertical refresh frequencies supported by the monitor, in kHz. These values help the X server determine the validity of built-in or specified <code class="option">Modeline</code> entries for the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Modeline</code> — An optional parameter which specifies additional video modes for the monitor at particular resolutions, with certain horizontal sync and vertical refresh resolutions. Refer to the <code class="filename">xorg.conf(5)</code> man page for a more detailed explanation of <code class="option">Modeline</code> entries.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option "<em class="replaceable"><code>option-name</code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf(5)</code> man page.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-device"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.7. The <code class="option">Device</code> section</h4></div></div></div><a id="idm66932112" class="indexterm"></a><div class="para">
+ Each <code class="option">Device</code> section configures one video card on the system. While one <code class="option">Device</code> section is the minimum, additional instances may occur for each video card installed on the machine.
+ </div><div class="para">
+ The following example shows a typical <code class="option">Device</code> section for a video card:
+ </div><pre class="screen">Section "Device"
+ Identifier "Videocard0"
+ Driver "mga"
+ VendorName "Videocard vendor"
+ BoardName "Matrox Millennium G200"
+ VideoRam 8192
+ Option "dpms"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">Device</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">Device</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Driver</code> — Specifies which driver the X server must load to utilize the video card. A list of drivers can be found in <code class="filename">/usr/share/hwdata/videodrivers</code>, which is installed with the <span class="package">hwdata</span> package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">VendorName</code> — An optional parameter which specifies the vendor of the video card.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">BoardName</code> — An optional parameter which specifies the name of the video card.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">VideoRam</code> — An optional parameter which specifies the amount of RAM available on the video card, in kilobytes. This setting is only necessary for video cards the X server cannot probe to detect the amount of video RAM.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">BusID</code> — An entry which specifies the bus location of the video card. On systems with only one video card a <code class="option">BusID</code> entry is optional and may not even be present in the default <code class="filename">/etc/X11/xorg.conf</code> file. On systems with more than one video card, however, a <code class="option">BusID</code> entry is required.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Screen</code> — An optional entry which specifies which monitor connector or head on the video card the <code class="option">Device</code> section configures. This option is only useful for video cards with multiple heads.
+ </div><div class="para">
+ If multiple monitors are connected to different heads on the same video card, separate <code class="option">Device</code> sections must exist and each of these sections must have a different <code class="option">Screen</code> value.
+ </div><div class="para">
+ Values for the <code class="option">Screen</code> entry must be an integer. The first head on the video card has a value of <code class="literal">0</code>. The value for each additional head increments this value by one.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option "<em class="replaceable"><code>option-name</code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf(5)</code> man page.
+ </div><div class="para">
+ One of the more common options is <code class="literal">"dpms"</code> (for Display Power Management Signaling, a VESA standard), which activates the Service Star energy compliance setting for the monitor.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-screen"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.8. The <code class="option">Screen</code> section</h4></div></div></div><a id="idm27731168" class="indexterm"></a><div class="para">
+ Each <code class="option">Screen</code> section binds one video card (or video card head) to one monitor by referencing the <code class="option">Device</code> section and the <code class="option">Monitor</code> section for each. While one <code class="option">Screen</code> section is the minimum, additional instances may occur for each video card and monitor combination present on the machine.
+ </div><div class="para">
+ The following example shows a typical <code class="option">Screen</code> section:
+ </div><pre class="screen">Section "Screen"
+ Identifier "Screen0"
+ Device "Videocard0"
+ Monitor "Monitor0"
+ DefaultDepth 16
+
+ SubSection "Display"
+ Depth 24
+ Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
+ EndSubSection
+
+ SubSection "Display"
+ Depth 16
+ Modes "1152x864" "1024x768" "800x600" "640x480"
+ EndSubSection
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="option">Screen</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">Identifier</code> — Specifies a unique name for this <code class="option">Screen</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Device</code> — Specifies the unique name of a <code class="option">Device</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Monitor</code> — Specifies the unique name of a <code class="option">Monitor</code> section. This is only required if a specific <code class="option">Monitor</code> section is defined in the <code class="filename">xorg.conf</code> file. Normally, monitors are detected automatically.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">DefaultDepth</code> — Specifies the default color depth in bits. In the previous example, <code class="literal">16</code> (which provides thousands of colors) is the default. Only one <code class="option">DefaultDepth</code> entry is permitted, although this can be overridden with the Xorg command line option <code class="command">-depth <em class="replaceable"><code><n></code></em></code>, where <code class="command"><em class="replaceable"><code><n></code></em></code> is any additional depth specified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">SubSection "Display"</code> — Specifies the screen modes available at a particular color depth. The <code class="option">Screen</code> section can have multiple <code class="option">Display</code> subsections, which are entirely optional since screen modes are detected automatically.
+ </div><div class="para">
+ This subsection is normally used to override auto-detected modes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">Option "<em class="replaceable"><code>option-name</code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf(5)</code> man page.
+ </div></li></ul></div></div><div class="section" id="s3-x-server-config-xorg.conf-dri"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">C.3.3.9. The <code class="option">DRI</code> section</h4></div></div></div><a id="idm43864624" class="indexterm"></a><div class="para">
+ The optional <code class="option">DRI</code> section specifies parameters for the <em class="firstterm">Direct Rendering Infrastructure</em> (<em class="firstterm">DRI</em>). DRI is an interface which allows 3D software applications to take advantage of 3D hardware acceleration capabilities built into most modern video hardware. In addition, DRI can improve 2D performance via hardware acceleration, if supported by the video card driver.
+ </div><div class="para">
+ This section is rarely used, as the DRI Group and Mode are automatically initialized to default values. If a different Group or Mode is needed, then adding this section to the <code class="filename">xorg.conf</code> file will override the default values.
+ </div><div class="para">
+ The following example shows a typical <code class="option">DRI</code> section:
+ </div><pre class="screen">Section "DRI"
+ Group 0
+ Mode 0666
+EndSection</pre><div class="para">
+ Since different video cards use DRI in different ways, do not add to this section without first referring to <a href="http://dri.freedesktop.org/wiki/">http://dri.freedesktop.org/wiki/</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x-server-config-xorg.conf.d.html"><strong>戻る</strong>C.3.2. The xorg.conf.d 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-x-fonts.html"><strong>次へ</strong>C.4. フォント</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-useful-websites.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-useful-websites.html
new file mode 100644
index 0000000..c9062c3
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s2-x-useful-websites.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>C.5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-x-additional-resources.html" title="C.5. その他のリソース" /><link rel="prev" href="s1-x-additional-resources.html" title="C.5. その他のリソース" /><link rel="next" href="ch-The_sysconfig_Directory.html" title="付録D sysconfig ディレクトリー" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-additional-resources.html"><strong>æ
ˆ»ã‚‹</strong></a></li><li class="next"><a accesskey="n" href="ch-The_sysconfig_Directory.html"><strong>次ã¸</strong></a></li></ul><div class="section" id="s2-x-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">C.5.2. å½¹ã«ç«‹ã¤ Web サイト</h3></div></div></div><a id="idm48592384" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.X.org/">http://www.X.org/</a> — Home page of the X.Org Foundation, which produces major releases of the X Window System bundled with Fedora to control the necessary hardware and provide a GUI environment.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://dri.sourceforge.net/">http://dri.sourceforge.net/</a> — Home page of the DRI (Direct Rendering Infrastructure) project. The DRI is the core hardware 3D acceleration component of X.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.gnome.org">http://www.gnome.org/</a> — Home of the GNOME project.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.kde.org">http://www.kde.org/</a> — Home of the KDE desktop environment.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-additional-resources.html"><strong>戻る</strong>C.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="ch-The_sysconfig_Directory.html"><strong>次へ</strong>付録D sysconfig ディレクトリー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html
new file mode 100644
index 0000000..00b32fb
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-FTP.html" title="16.2. FTP" /><link rel="prev" href="s2-ftp-servers.html" title="16.2.2. FTP サーバー" /><link rel="next" href="s2-ftp-vsftpd-start.html" title="16.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">16.2.3. Files Installed with <code class="command">vsftpd</code> </h3></div></div></div><a id="idm32418368" 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>. Refer to <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 17 <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>. Refer to <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>16.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>16.2.4. vsftpd の開始と停止</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s3-services-running-restarting.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s3-services-running-restarting.html
new file mode 100644
index 0000000..9f5795c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>8.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-services-running.html" title="8.2. サービスの実行" /><link rel="prev" href="s3-services-running-stopping.html" title="8.2.3. サービスの停止" /><link rel="next" href="s1-services-additional-resources.html" title="8.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">8.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>例8.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 httpd.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>8.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>8.3. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s3-services-running-running.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s3-services-running-running.html
new file mode 100644
index 0000000..13cd1cb
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>8.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-services-running.html" title="8.2. サービスの実行" /><link rel="prev" href="s1-services-running.html" title="8.2. サービスの実行" /><link rel="next" href="s3-services-running-stopping.html" title="8.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">8.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>例8.5 httpd サービスの実行</h6><div class="example-contents"><div class="para">
+ <a class="xref" href="ch-Services_and_Daemons.html#exam-services-configuration-enabling">例8.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>8.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>8.2.3. サービスの停止</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s3-services-running-stopping.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/s3-services-running-stopping.html
new file mode 100644
index 0000000..459bd2f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>8.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-services-running.html" title="8.2. サービスの実行" /><link rel="prev" href="s3-services-running-running.html" title="8.2.2. サービスの実行" /><link rel="next" href="s3-services-running-restarting.html" title="8.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">8.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>例8.6 telnet サービスの停止</h6><div class="example-contents"><div class="para">
+ <a class="xref" href="ch-Services_and_Daemons.html#exam-services-configuration-disabling">例8.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>8.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>8.2.4. サービスの再起動</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Adding_Other_Printer.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Adding_Other_Printer.html
new file mode 100644
index 0000000..037b710
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="sec-Setting_Printer.html" title="16.3.2. Starting Printer Setup" /><link rel="next" href="s1-printing-jetdirect-printer.html" title="16.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">16.3.3. ãƒãƒ¼ã‚«ãƒ«ãƒ—リンタã®è¿½åŠ </h3></div></div></div><a id="idm21748960" 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">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>図16.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. Refer to <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>16.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>16.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/17/html/System_Administrators_Guide/sec-Additional_Resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Additional_Resources.html
new file mode 100644
index 0000000..50a5b02
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-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>4.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-yum.html" title="第4章 Yum" /><link rel="prev" href="sec-Plugin_Descriptions.html" title="4.4.3. プラグインの説明" /><link rel="next" href="ch-PackageKit.html" title="第5章 PackageKit" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Plugin_Descriptions.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ch-Package
Kit.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">4.5. その他のリソース</h2></div></div></div><a id="idm69887616" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl.org/wiki/Guides</a></span></dt><dd><div class="para">
+ Yum wiki の <code class="literal">Yum Guides</code> セクションはさらなるドキュメントが含まれます。
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Plugin_Descriptions.html"><strong>戻る</strong>4.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="ch-PackageKit.html"><strong>次へ</strong>第5章 PackageKit</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuration_File_Changes.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuration_File_Changes.html
new file mode 100644
index 0000000..94f5505
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuration_File_Changes.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>B.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-rpm-using.html" title="B.2. RPMの使用法" /><link rel="prev" href="sec-Installing_and_Upgrading.html" title="B.2.2. インストールとアップグレード" /><link rel="next" href="s2-rpm-uninstalling.html" title="B.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="sec-Installing_and_Upgrading.html"><strong>戻る</stro
ng></a></li><li class="next"><a accesskey="n" href="s2-rpm-uninstalling.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.3. 設定ファイルの変更</h3></div></div></div><a id="idm20446352" class="indexterm"></a><a id="idm20444944" class="indexterm"></a><div class="para">
+ Because RPM performs intelligent upgrading of packages with configuration files
+ <a id="idm46429264" class="indexterm"></a>
+ , you may see one or the other of the following messages:
+ </div><pre class="screen">saving /etc/foo.conf as /etc/foo.conf.rpmsave</pre><div class="para">
+ This message means that 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 RPM 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, RPM may save the package's <span class="emphasis"><em>new</em></span> configuration file as, for example, <code class="filename">foo.conf.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 with a <code class="command">diff</code> program.
+ </div><div class="para">
+ If you attempt to upgrade to a package with an <span class="emphasis"><em>older</em></span> version number (that is, if a higher version of the package is already installed), the output is similar to the following:
+ </div><pre class="screen">package foo-2.0-1.fc17.x86_64.rpm (which is newer than foo-1.0-1) is already installed</pre><div class="para">
+ To force RPM to upgrade anyway, use the <code class="command">--oldpackage</code> option:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --oldpackage foo-1.0-1.fc17.x86_64.rpm</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Upgrading.html"><strong>戻る</strong>B.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-rpm-uninstalling.html"><strong>次へ</strong>B.2.4. アンインストール</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Connection_Settings.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Connection_Settings.html
new file mode 100644
index 0000000..16040ea
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Connection_Settings.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>6.4. Configuring Connection Settings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-NetworkManager.html" title="第6章 NetworkManager" /><link rel="prev" href="sec-Establishing_Routes.html" title="6.3.6. Establishing Routes" /><link rel="next" href="sec-Configuring_Wireless_Security.html" title="6.4.2. Configuring Wireless Security" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_Routes.html"><strong>戻る</strong></a>
</li><li class="next"><a accesskey="n" href="sec-Configuring_Wireless_Security.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Configuring_Connection_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Configuring Connection Settings</h2></div></div></div><div class="section" id="sec-Configuring_802.1x_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.1. Configuring 802.1x Security</h3></div></div></div><div class="para">
+ 802.1x security is the name of the IEEE standard for port-based Network Access Control (PNAC). Simply put, 802.1x security is a way of defining a <em class="firstterm">logical network</em> out of a physical one. All clients who want to join the logical network must authenticate with the server (a router, for example) using the correct 802.1x authentication method.
+ </div><div class="para">
+ 802.1x security is most often associated with securing wireless networks (WLANs), but can also be used to prevent intruders with physical access to the network (LAN) from gaining entry. In the past, DHCP servers were configured not to lease IP addresses to unauthorized users, but for various reasons this practice is both impractical and insecure, and thus is no longer recommended. Instead, 802.1x security is used to ensure a logically-secure network through port-based authentication.
+ </div><div class="para">
+ 802.1x provides a framework for WLAN and LAN access control and serves as an envelope for carrying one of the Extensible Authentication Protocol (EAP) types. An EAP type is a protocol that defines how WLAN security is achieved on the network.
+ </div><div class="para">
+ You can configure 802.1x security for a wired or wireless connection type by opening the <span class="guilabel"><strong>Network Connections</strong></span> window (refer to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html">「Configuring New and Editing Existing Connections」</a>) and following the applicable procedure:
+ </div><div class="procedure" id="procedure-For_a_wired_connection..."><h6>手順6.6 For a wired connection...</h6><ol class="1"><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Wired</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Either click on <span class="guibutton"><strong>Add</strong></span> to add a new network connection for which you want to configure 802.1x security, or select an existing connection and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Then select the <span class="guilabel"><strong>802.1x Security</strong></span> tab and check the <span class="guilabel"><strong>Use 802.1x security for this connection</strong></span> checkbox to enable settings configuration.
+ </div></li><li class="step"><div class="para">
+ Proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_TLS_Transport_Layer_Security_Settings">「Configuring TLS (Transport Layer Security) Settings」</a>
+ </div></li></ol></div><div class="procedure" id="procedure-For_a_wireless_connection..."><h6>手順6.7 For a wireless connection...</h6><ol class="1"><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Wireless</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Either click on <span class="guibutton"><strong>Add</strong></span> to add a new network connection for which you want to configure 802.1x security, or select an existing connection and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Then click the <span class="guilabel"><strong>Security</strong></span> dropdown and choose one of the following security methods: <span class="guimenuitem"><strong>LEAP</strong></span>, <span class="guimenuitem"><strong>Dynamic WEP (802.1x)</strong></span>, or <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Refer to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_TLS_Transport_Layer_Security_Settings">「Configuring TLS (Transport Layer Security) Settings」</a> for descriptions of which EAP types correspond to your selection in the <span class="guilabel"><strong>Security</strong></span> dropdown.
+ </div></li></ol></div><div class="section" id="sec-Configuring_TLS_Transport_Layer_Security_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">6.4.1.1. Configuring TLS (Transport Layer Security) Settings</h4></div></div></div><div class="para">
+ With Transport Layer Security, the client and server mutually authenticate using the TLS protocol. The server demonstrates that it holds a digital certificate, the client proves its own identity using its client-side certificate, and key information is exchanged. Once authentication is complete, the TLS tunnel is no longer used. Instead, the client and server use the exchanged keys to encrypt data using AES, TKIP or WEP.
+ </div><div class="para">
+ The fact that certificates must be distributed to all clients who want to authenticate means that the EAP-TLS authentication method is very strong, but also more complicated to set up. Using TLS security requires the overhead of a public key infrastructure (PKI) to manage certificates. The benefit of using TLS security is that a compromised password does not allow access to the (W)LAN: an intruder must also have access to the authenticating client's private key.
+ </div><div class="para">
+ Network Manger does not determine the version of TLS supported. Network Manager gathers the parameters entered by the user and passes them to the daemon, wpa_supplicant, that handles the procedure. It, in turn, uses OpenSSL to establish the TLS tunnel. OpenSSL itself negotiates the SSL/TLS protocol version. It uses the highest version both ends support.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Identity</strong></span> </span></dt><dd><div class="para">
+ Identity string for EAP authentication methods, such as a username or login name.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a user's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Private key</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a user's private key file.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Private key password</strong></span> </span></dt><dd><div class="para">
+ Enter the user password corresponding to the user's private key.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_Tunneled_TLS_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">6.4.1.2. Configuring Tunneled TLS Settings</h4></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous identity</strong></span> </span></dt><dd><div class="para">
+ This value is used as the unencrypted identity.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>PAP</strong></span> — Password Authentication Protocol.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAP</strong></span> — Challenge Handshake Authentication Protocol.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>CHAP</strong></span> — Challenge Handshake Authentication Protocol.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_Protected_EAP_PEAP_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">6.4.1.3. Configuring Protected EAP (PEAP) Settings</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous Identity</strong></span> </span></dt><dd><div class="para">
+ This value is used as the unencrypted identity.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PEAP version</strong></span> </span></dt><dd><div class="para">
+ The version of Protected EAP to use. Automatic, 0 or 1.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MD5</strong></span> — Message Digest 5, a cryptographic hash function.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>GTC</strong></span> — Generic Token Card.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_Routes.html"><strong>戻る</strong>6.3.6. Establishing Routes</a></li><li class="up"><a accesskey="u" href="#"><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_Wireless_Security.html"><strong>次へ</strong>6.4.2. Configuring Wireless Security</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_IPv4_Settings.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_IPv4_Settings.html
new file mode 100644
index 0000000..688395e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_IPv4_Settings.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>6.4.4. Configuring IPv4 Settings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Connection_Settings.html" title="6.4. Configuring Connection Settings" /><link rel="prev" href="sec-Configuring_PPP_Point-to-Point_Settings.html" title="6.4.3. Configuring PPP (Point-to-Point) Settings" /><link rel="next" href="sec-Configuring_IPv6_Settings.html" title="6.4.5. Configuring IPv6 Settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_PPP_Point-to-Point_Settings.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_IPv6_Settings.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Configuring_IPv4_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.4. Configuring IPv4 Settings</h3></div></div></div><div class="figure" id="exam-Configuring_IPv4_Settings"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-IPv4_Settings"><img src="images/Network_Configuration-NM-IPv4_Settings_Gnome3.png" alt="Editing the IPv4 Settings Tab" /><div class="longdesc"><div class="para">
+ A screen shot of NetworkManager's IPv4 Settings Tab
+ </div></div></div></div><h6>図6.11 Editing the IPv4 Settings Tab</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab allows you to configure the method by which you connect to the Internet and enter IP address, route, and DNS information as required. The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab is available when you create and modify one of the following connection types: wired, wireless, mobile broadband, VPN or DSL.
+ </div><div class="para">
+ If you are using DHCP to obtain a dynamic IP address from a DHCP server, you can simply set <span class="guilabel"><strong>Method</strong></span> to <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span>.
+ </div><h4 id="bh-Setting_the_Method">Setting the Method</h4><div class="variablelist" id="varlist-Available_IPv4_Methods_by_Connection_Type"><h6>Available IPv4 Methods by Connection Type</h6><div class="para">
+ When you click the <span class="guilabel"><strong>Method</strong></span> dropdown menu, depending on the type of connection you are configuring, you are able to select one of the following IPv4 connection methods. All of the methods are listed here according to which connection type or types they are associated with.
+ </div><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses. You do not need to fill in the <span class="guilabel"><strong>DHCP client ID</strong></span> field.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP) addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> — Choose this option if the network you are connecting to does not have a DHCP server and you do not want to assign IP addresses manually. Random addresses will be selected as per RFC 3927.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> — Choose this option if the interface you are configuring is for sharing an Internet or WAN connection.
+ </div></dd><dt class="varlistentry"><span class="term">Wired, Wireless and DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> — Choose this option if the network you are connecting to does not have a DHCP server and you want to assign IP addresses manually.
+ </div></dd><dt class="varlistentry"><span class="term">Mobile Broadband Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP) addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div></dd><dt class="varlistentry"><span class="term">VPN Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN) addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div></dd><dt class="varlistentry"><span class="term">DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE) addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_PPP_Point-to-Point_Settings.html"><strong>戻る</strong>6.4.3. Configuring PPP (Point-to-Point) Settings</a></li><li class="up"><a accesskey="u" href="#"><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_IPv6_Settings.html"><strong>次へ</strong>6.4.5. Configuring IPv6 Settings</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_IPv6_Settings.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_IPv6_Settings.html
new file mode 100644
index 0000000..fc8b613
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_IPv6_Settings.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>6.4.5. Configuring IPv6 Settings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Connection_Settings.html" title="6.4. Configuring Connection Settings" /><link rel="prev" href="sec-Configuring_IPv4_Settings.html" title="6.4.4. Configuring IPv4 Settings" /><link rel="next" href="sec-NetworkManager_Architecture.html" title="6.5. NetworkManager Architecture" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_IPv
4_Settings.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-NetworkManager_Architecture.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Configuring_IPv6_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.5. Configuring IPv6 Settings</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Ignore</strong></span> — Choose this option if you want to disable IPv6 settings.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic, addresses only</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses but you want to assign DNS servers manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> — Choose this option if the network you are connecting to does not have a DHCP server and you want to assign IP addresses manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> — Choose this option if the network you are connecting to does not have a DHCP server and you do not want to assign IP addresses manually. Random addresses will be selected as per RFC 4862.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> — Choose this option if the interface you are configuring is for sharing an Internet or WAN connection.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>DNS servers</strong></span> — Enter a comma separated list of DNS servers.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Search domains</strong></span> — Enter a comma separated list of domain controllers.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_IPv4_Settings.html"><strong>戻る</strong>6.4.4. Configuring IPv4 Settings</a></li><li class="up"><a accesskey="u" href="#"><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-NetworkManager_Architecture.html"><strong>次へ</strong>6.5. NetworkManager Architecture</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html
new file mode 100644
index 0000000..4024e69
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_New_and_Editing_Existing_Connections.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>6.2.2. Configuring New and Editing Existing Connections</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Interacting_with_NetworkManager.html" title="6.2. Interacting with NetworkManager" /><link rel="prev" href="sec-Interacting_with_NetworkManager.html" title="6.2. Interacting with NetworkManager" /><link rel="next" href="sec-Connecting_to_a_Network_Automatically.html" title="6.2.3. Connecting to a Network Automatically" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accessk
ey="p" href="sec-Interacting_with_NetworkManager.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Connecting_to_a_Network_Automatically.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Configuring_New_and_Editing_Existing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.2. Configuring New and Editing Existing Connections</h3></div></div></div><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet to open the drop-down menu, this is the main point of entry for interacting with <span class="application"><strong>NetworkManager</strong></span> to configure connections.
+ </div><div class="para">
+ If the system has detected a wired connection, the <span class="guilabel"><strong>Wired</strong></span> menu entry will appear. If the system has detected a wireless card, then you will also see a <span class="guilabel"><strong>Wireless</strong></span> menu entry. Clicking the <span class="guilabel"><strong>Wired</strong></span> and <span class="guilabel"><strong>Wireless</strong></span> labels or the associated ON OFF indicator to the right will toggle the status between ON and OFF.
+ </div><div class="para">
+ Finally, clicking on the <span class="guilabel"><strong>Network Settings</strong></span> menu entry opens the <span class="guilabel"><strong>Network</strong></span> window, from where you can view some basic network configuration information and initiate configuration tasks.
+ </div><div class="figure" id="exam-Network_Configuration_NM_Network_Wired_Gnome3"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_Network_Wired_Gnome3_Fed17"><img src="images/Network_Configuration_NM_Network_Wired_Gnome3_Fed17.png" alt="Configure networks using the Network window" /><div class="longdesc"><div class="para">
+ A screen shot of NetworkManager's Network window.
+ </div></div></div></div><h6>図6.3 Configure networks using the Network window</h6></div><br class="figure-break" /><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ wired Ethernet connections, click on <span class="guilabel"><strong>Wired</strong></span> followed by <span class="guilabel"><strong>Options</strong></span> and proceed to <a class="xref" href="sec-Establishing_Connections.html#sec-Establishing_a_Wired_Ethernet_Connection">「Establishing a Wired (Ethernet) Connection」</a>;
+ </div></li><li class="listitem"><div class="para">
+ wireless connections, click on <span class="guilabel"><strong>Wireless</strong></span> followed by <span class="guilabel"><strong>Options</strong></span> and proceed to <a class="xref" href="sec-Establishing_a_Wireless_Connection.html">「Establishing a Wireless Connection」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ mobile broadband connections, proceed to <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html">「Establishing a Mobile Broadband Connection」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ VPN connections, click on the <span class="guilabel"><strong>VPN</strong></span> menu entry followed by <span class="guilabel"><strong>Options</strong></span> and proceed to <a class="xref" href="sec-Establishing_a_VPN_Connection.html">「Establishing a VPN Connection」</a>. If there is no VPN menu entry click on the plus sign at the bottom. A dialog box appears. Ensure the interface is set to VPN. Click the <span class="guibutton"><strong>Create</strong></span> button to open the <span class="guilabel"><strong>Choose a VPN Connection Type</strong></span> assistant. Proceed to <a class="xref" href="sec-Establishing_a_VPN_Connection.html#Network_Configuration-VPN-step2">ステップ 5</a>
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Interacting_with_NetworkManager.html"><strong>戻る</strong>6.2. Interacting with NetworkManager</a></li><li class="up"><a accesskey="u" href="#"><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-Connecting_to_a_Network_Automatically.html"><strong>次へ</strong>6.2.3. Connecting to a Network Automatically</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_PPP_Point-to-Point_Settings.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_PPP_Point-to-Point_Settings.html
new file mode 100644
index 0000000..c7c0301
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_PPP_Point-to-Point_Settings.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.3. Configuring PPP (Point-to-Point) Settings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Connection_Settings.html" title="6.4. Configuring Connection Settings" /><link rel="prev" href="sec-Configuring_Wireless_Security.html" title="6.4.2. Configuring Wireless Security" /><link rel="next" href="sec-Configuring_IPv4_Settings.html" title="6.4.4. Configuring IPv4 Settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Configuri
ng_Wireless_Security.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_IPv4_Settings.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Configuring_PPP_Point-to-Point_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.3. Configuring PPP (Point-to-Point) Settings</h3></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Configure Methods</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use point-to-point encryption (MPPE)</strong></span> </span></dt><dd><div class="para">
+ Microsoft Point-To-Point Encryption protocol (RFC 3078).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow BSD data compression</strong></span> </span></dt><dd><div class="para">
+ PPP BSD Compression Protocol (RFC 1977).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow Deflate data compression</strong></span> </span></dt><dd><div class="para">
+ PPP Deflate Protocol (RFC 1979).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use TCP header compression</strong></span> </span></dt><dd><div class="para">
+ Compressing TCP/IP Headers for Low-Speed Serial Links (RFC 1144).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Send PPP echo packets</strong></span> </span></dt><dd><div class="para">
+ LCP Echo-Request and Echo-Reply Codes for loopback tests (RFC 1661).
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Wireless_Security.html"><strong>戻る</strong>6.4.2. Configuring Wireless Security</a></li><li class="up"><a accesskey="u" href="#"><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_IPv4_Settings.html"><strong>次へ</strong>6.4.4. Configuring IPv4 Settings</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Wireless_Security.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Wireless_Security.html
new file mode 100644
index 0000000..dfddc5b
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Wireless_Security.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>6.4.2. Configuring Wireless Security</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Connection_Settings.html" title="6.4. Configuring Connection Settings" /><link rel="prev" href="sec-Configuring_Connection_Settings.html" title="6.4. Configuring Connection Settings" /><link rel="next" href="sec-Configuring_PPP_Point-to-Point_Settings.html" title="6.4.3. Configuring PPP (Point-to-Point) Settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="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="sec-Configuring_Connection_Settings.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_PPP_Point-to-Point_Settings.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Configuring_Wireless_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.2. Configuring Wireless Security</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Security</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>None</strong></span> — Do not encrypt the Wi-Fi connection.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 40/128-bit Key</strong></span> — Wired Equivalent Privacy (WEP), from the IEEE 802.11 standard. Uses a single pre-shared key (PSK).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 128-bit Passphrase</strong></span> — An MD5 hash of the passphrase will be used to derive a WEP key.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>LEAP</strong></span> — Lightweight Extensible Authentication Protocol, from Cisco Systems.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Dynamic WEP (802.1x)</strong></span> — WEP keys are changed dynamically.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Personal</strong></span> — Wi-Fi Protected Access (WPA), from the draft IEEE 802.11i standard. A replacement for WEP. Wi-Fi Protected Access II (WPA2), from the 802.11i-2004 standard. Personal mode uses a pre-shared key (WPA-PSK).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span> — WPA for use with a RADUIS authentication server to provide IEEE 802.1x network access control.
+ </div></dd><dt class="varlistentry"><span class="term">Password</span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Connection_Settings.html"><strong>戻る</strong>6.4. Configuring Connection Settings</a></li><li class="up"><a accesskey="u" href="#"><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_PPP_Point-to-Point_Settings.html"><strong>次へ</strong>6.4.3. Configuring PPP (Point-to-Point) Settings</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Yum_and_Yum_Repositories.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
new file mode 100644
index 0000000..cb58f09
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
@@ -0,0 +1,125 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Yum と Yum リポジトリーの設定</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-yum.html" title="第4章 Yum" /><link rel="prev" href="sec-Yum-Transaction_History.html" title="4.2.6. 処理とトランザクションの履歴" /><link rel="next" href="sec-Setting_repository_Options.html" title="4.3.2. [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-Yum-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_Yum_and_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Yum 㨠Yum リãƒã‚¸ãƒˆãƒªãƒ¼ã®è¨å®š</h2></div></div></div><a id="idm54292992" class="indexterm"></a><a id="idm54291584" class="indexterm"></a><div class="para">
+ <code class="command">yum</code> と関連ユーティリティの設定ファイルは <code class="filename">/etc/yum.conf</code> にあります。このファイルは、必須の <code class="literal">[main]</code> セクション（全体に影響を持つ Yum オプションを設定できます）を含みます。また1つ以上の <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクション（リポジトリ固有のオプションを設定できます）を含むかもしれません。しかしながら、ベストプラクティスは <code class="filename">/etc/yum.repos.d/</code> ディレクトリに新規または既存の <code class="filename">.repo</code> ファイルにおいてそれぞれのリポジトリを定義することです。<code class="filename">/etc/yum.conf</code> ファイルの <code class="literal">[main]</code> セクションにおいて定義した値は、それぞれの <code class="liter
al">[<em class="replaceable"><code>repository</code></em>]</code> セクションにおいて設定した値をオーバーライドするかもしれません。
+ </div><div class="para">
+ このセクションは以下の方法を説明します:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/yum.conf</code> 設定ファイルの <code class="literal">[main]</code> セクションを編集することにより、Yum の全体オプションを設定します;
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/yum.conf</code> および <code class="filename">/etc/yum.repos.d/</code> ディレクトリの <code class="filename">.repo</code> にある <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションを編集することにより各リポジトリに対するオプションを設定します;
+ </div></li><li class="listitem"><div class="para">
+ バージョンとアーキテクチャーを動的に正しく取り扱えるように <code class="filename">/etc/yum.conf</code> および <code class="filename">/etc/yum.repos.d/</code> ディレクトリにあるファイルに Yum 変数を使用します;
+ </div></li><li class="listitem"><div class="para">
+ コマンドラインで Yum リポジトリの追加、有効化および無効化をします、また、
+ </div></li><li class="listitem"><div class="para">
+ 独自 Yum リポジトリを導入します。
+ </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">4.3.1. [main] オプションの設定</h3></div></div></div><a id="idm55658480" class="indexterm"></a><div class="para">
+ <code class="filename">/etc/yum.conf</code> 設定ファイルはちょうど一つの <code class="literal">[main]</code> セクションを含みます。このセクションにあるキー・バリューの組のいくつかは、<code class="command">yum</code> がどのように動作するかに影響します。その他は Yum がリポジトリをどのように取り扱うかに影響します。<code class="filename">/etc/yum.conf</code> の先頭にある <code class="literal">[main]</code> セクションの下に数多くの追加のオプションを追加できます。
+ </div><div class="para">
+ サンプル <code class="filename">/etc/yum.conf</code> 設定ファイルはこのようなものです:
+ </div><pre class="programlisting">[main]
+cachedir=/var/cache/yum/$basearch/$releasever
+keepcache=0
+debuglevel=2
+logfile=/var/log/yum.log
+exactarch=1
+obsoletes=1
+gpgcheck=1
+plugins=1
+installonly_limit=3
+
+<em class="lineannotation"><span class="lineannotation">[コメントの省略]</span></em>
+
+# PUT YOUR REPOS HERE OR IN separate files named file.repo
+# in /etc/yum.repos.d</pre><div class="para">
+ 以下は <code class="literal">[main]</code> セクションにおいて最も一般的に使用されるオプションです:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">assumeyes</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — <code class="command">yum</code> はクリティカルなアクションの実行について確認のプロンプトを表示します。これがデフォルトです。
+ </div><div class="para">
+ <code class="literal">1</code> — クリティカルな <code class="command">yum</code> アクションについて確認のプロンプトを表示します。もし <code class="option">assumeyes=1</code> が設定されていると、<code class="command">yum</code> はコマンドラインにおいて <code class="option">-y</code> オプションをつけたときと同じ方法の動作をします。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">cachedir</code>=<em class="replaceable"><code>directory</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>directory</code></em> は、Yum がキャッシュとデータベースファイルを保存するディレクトリの絶対パスです。Yum のキャッシュディレクトリはデフォルトで <code class="filename">/var/cache/yum/$basearch/$releasever</code> です。
+ </div><div class="para">
+ <code class="varname">$basearch</code> および <code class="varname">$releasever</code> Yum 変数の記述については<a class="xref" href="sec-Using_Yum_Variables.html">「Yum 変数の使い方」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">debuglevel</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は <code class="literal">1</code> から <code class="literal">10</code> の間の整数です。<code class="option">debuglevel</code> 値により大きな値を設定することにより、<code class="command">yum</code> がより詳細なデバッグ情報を表示します。<code class="option">debuglevel=0</code> はデバッグ出力を無効にします。<code class="option">debuglevel=2</code> がデフォルトです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">exactarch</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — パッケージを更新するときに、厳密なアーキテクチャーを考慮しません。
+ </div><div class="para">
+ <code class="literal">1</code> — パッケージを更新するときに、厳密なアーキテクチャーを考慮します。この設定をすると、<code class="command">yum</code> は、システムにすでにインストールされている i386 パッケージを更新するために、i686 パッケージをインストールすることはしません。これがデフォルトです。
+ </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">
+ このオプションはインストール/更新中にキーワードによりパッケージを除外できます。スペース区切りでパッケージの一覧をクオートすることにより、除外する複数のパッケージを一覧にできます。ワイルドカード (たとえば、<code class="literal">*</code> および <code class="literal">?</code>) を使用するシェルのグロブ表現が許可されます。
+ </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">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — ローカルパッケージのインストールを含め、すべてのリポジトリーにおいてパッケージの GPG 署名検証を無効にします。
+ </div><div class="para">
+ <code class="literal">1</code> — ローカルパッケージのインストールを含め、すべてのリポジトリーにおいてすべてのパッケージの GPG 署名検証を有効にします。<code class="option">gpgcheck=1</code> がデフォルトで、すべてのパッケージの署名がチェックされます。
+ </div><div class="para">
+ このオプションが <code class="filename">/etc/yum.conf</code> の <code class="literal">[main]</code> セクションにおいて設定されていると、すべてのリポジトリに対して GPG チェックのルールを設定します。しかしながら、代わりに各リポジトリに対して <code class="option">gpgcheck=<em class="replaceable"><code>value</code></em></code> を設定することもできます。つまり、あるリポジトリにおいて GPG チェックを有効にしながら、他において無効にすることができます。もし <code class="filename">/etc/yum.conf</code> にあるならば、各リポジトリに対して対応する <code class="filename">.repo</code> ファイルにおいて <code class="option">gpgcheck=<em class="replaceable"><code>value</code></em></code> を設定することによりデフォルトをオーバーライドします。
+ </div><div class="para">
+ GPG 署名チェックに関する詳細は<a class="xref" href="s1-check-rpm-sig.html">「パッケージの署名を確認する」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">groupremove_leaf_only</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — <code class="command">yum</code> はパッケージグループを削除するとき各パッケージの依存物を確認<span class="emphasis"><em>しません</em></span>。この設定を用いると、<code class="command">yum</code> は、他のパッケージやグループにより必要とされるパッケージかどうかによらず、パッケージグループにあるすべてのパッケージを削除します。<code class="option">groupremove_leaf_only=0</code> はデフォルトです。
+ </div><div class="para">
+ <code class="literal">1</code> — <code class="command">yum</code> は、パッケージグループを削除するとき各パッケージの依存性を確認して、あらゆる他のパッケージやグループにより必要とされないパッケージのみを削除します。
+ </div><div class="para">
+ パッケージの削除に関する詳細は<a class="xref" href="sec-Removing.html#important-Package_Group_Removal">インテリジェントなパッケージグループの削除</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">
+ ここに <code class="command">yum</code> が<span class="emphasis"><em>インストール</em></span>できるが、<span class="emphasis"><em>更新</em></span>しないパッケージの一覧を空白区切りで提供できます。デフォルトでインストールのみとなっているパッケージの一覧は <span class="bold bold"><strong>yum.conf</strong></span>(5) マニュアルページを参照してください。
+ </div><div class="para">
+ <code class="option">installonlypkgs</code> ディレクティブを <code class="filename">/etc/yum.conf</code> に追加したければ、<span class="bold bold"><strong>yum.conf</strong></span>(5) の <code class="literal">installonlypkgs</code> の中に一覧化されているものすべてを含めて、インストールのみにする<span class="emphasis"><em>すべて</em></span>のパッケージを一覧にすることを確認します。とくに、kernel パッケージは必ず <code class="option">installonlypkgs</code> (デフォルトであります) に一覧化すべきです。また、デフォルトのカーネルが起動に失敗した場合に、バックアップのカーネルが必ず利用可能であるよう、\n<code class="option">installonly_limit</code> は必ず <code class="literal">2</code> よりも大きな値に設定すべきです。
+ </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">
+ …ここで <em class="replaceable"><code>value</code></em> は <code class="option">installonlypkgs</code> ディレクティブに一覧されている単一パッケージすべてに対して同時にインストールできるバージョンの最大数を表す整数です。
+ </div><div class="para">
+ <code class="option">installonlypkgs</code> ディレクティブのデフォルトはそれぞれの異なる kernel パッケージを含みます。そのため、<code class="option">installonly_limit</code> の値を変更することにより、あらゆる単一の kernel パッケージについてインストールされたバージョンの最大数にも影響します。<code class="filename">/etc/yum.conf</code> に記載されたデフォルト値は <code class="option">installonly_limit=3</code> です。そして、この値を減らすこと、特に <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">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — 正常にインストールされた後、ヘッダーとパッケージのキャッシュを保持しません。これがデフォルトです。
+ </div><div class="para">
+ <code class="literal">1</code> — 正常にインストールした後、キャッシュを保持します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">logfile</code>=<em class="replaceable"><code>file_name</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>file_name</code></em> は <code class="command">yum</code> がログ出力を書き込むファイルの絶対パスです。デフォルトで <code class="command">yum</code> は <code class="filename">/var/log/yum.log</code> にログをとります。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">multilib_policy</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">best</code> — このシステムに最適なアーキテクチャーをインストールします。たとえば、AMD64 システムにおいて <code class="option">multilib_policy=best</code> を設定することにより、<code class="command">yum</code> はすべてのパッケージの 64 ビットバージョンをインストールします。
+ </div><div class="para">
+ <code class="literal">all</code> — 常にすべてのパッケージについてすべての利用可能なアーキテクチャーをインストールします。たとえば、AMD64 システムにおいて <code class="option">multilib_policy</code> を <code class="literal">all</code> に設定すると、<code class="command">yum</code> は、i586 と AMD64 の両方が利用可能ならば、パッケージの両方のバージョンをインストールします。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">obsoletes</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — 更新を実行するとき <code class="command">yum</code> の推奨されない処理ロジックを無効にします。
+ </div><div class="para">
+ <code class="literal">1</code> — 更新を実行するときに <code class="command">yum</code> の推奨されない処理ロジックを有効にします。あるパッケージが他のパッケージを<em class="firstterm">推奨しない</em>よう SPEC ファイルにおいて宣言するとき、後者のパッケージは前者のパッケージがインストールされるときに前者のパッケージにより置き換えられます。たとえば、パッケージが名前変更されるとき、推奨しないことが宣言されます。<code class="option">obsoletes=1</code> がデフォルトです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">plugins</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — Yum プラグイン全体を無効にします。
+ </div><div class="important" id="important-Disabling_all_plugins_is_not_advised-main_options"><div class="admonition_header"><h2>すべてのプラグインを無効にすることは推奨されません</h2></div><div class="admonition"><div class="para">
+ あるプラグインは重要な <code class="command">Yum</code> サービスを提供するので、すべてのプラグインを無効にすることは推奨されません。プラグインを全体的に無効にすることは、便利なオプションとして提供され、一般的に <code class="command">Yum</code> に関する潜在的な問題を診断するときにのみ推奨されます。
+ </div></div></div><div class="para">
+ <code class="literal">1</code> — すべての Yum プラグインを有効にします。<code class="option">plugins=1</code> を用いても、プラグインの設定ファイルにおいて <code class="option">enabled=0</code> と設定されている特定の Yum プラグインを無効にすることもできます。
+ </div><div class="para">
+ さまざまな Yum プラグインの詳細は<a class="xref" href="sec-Yum_Plugins.html">「Yum プラグイン」</a>を参照してください。プラグインの制御に関する詳細は<a class="xref" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">「Yum プラグインの無効化、有効化、設定」</a>を参照してください。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">reposdir</code>=<em class="replaceable"><code>directory</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>directory</code></em> は <code class="filename">.repo</code> ファイルが置かれる場所の絶対パスです。すべての <code class="filename">.repo</code> ファイルはリポジトリの情報（<code class="filename">/etc/yum.conf</code> の <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションと似ています）を含みます。<code class="command">yum</code> はトランザクションのために使用するリポジトリのマスター一覧を作成するために、<code class="filename">.repo</code> ファイルと <code class="filename">/etc/yum.conf</code> ファイルの <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションからすべてのリポジトリの情報を収集します。<code class="literal">reposdir</code> が設定されていなければ、<code class="command">yum</code> はデフォル
トの <code class="filename">/etc/yum.repos.d/</code> ディレクトリを使用します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">retries</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>value</code></em> は <code class="literal">0</code> 以上の整数です。この値は <code class="command">yum</code> がエラーを返す前にファイルの取得を試みる回数を設定します。これを <code class="literal">0</code> に設定することにより、<code class="command">yum</code> が無限に再試行します。デフォルト値は <code class="literal">10</code> です。
+ </div></dd></dl></div><div class="para">
+ 利用可能な <code class="literal">[main]</code> オプションの完全な一覧は、<span class="bold bold"><strong>yum.conf</strong></span>(5) マニュアルページの <code class="literal">[main] OPTIONS</code> セクションを参照してください。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Yum-Transaction_History.html"><strong>戻る</strong>4.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_repository_Options.html"><strong>次へ</strong>4.3.2. [repository] オプションの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Connecting_to_a_Network_Automatically.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Connecting_to_a_Network_Automatically.html
new file mode 100644
index 0000000..2049fa0
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Connecting_to_a_Network_Automatically.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>6.2.3. Connecting to a Network Automatically</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Interacting_with_NetworkManager.html" title="6.2. Interacting with NetworkManager" /><link rel="prev" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="6.2.2. Configuring New and Editing Existing Connections" /><link rel="next" href="sec-User_and_System_Connections.html" title="6.2.4. User and System Connections" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="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="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-User_and_System_Connections.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Connecting_to_a_Network_Automatically"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.3. Connecting to a Network Automatically</h3></div></div></div><div class="para">
+ For any connection type you add or configure, you can choose whether you want <span class="application"><strong>NetworkManager</strong></span> to try to connect to that network automatically when it is available.
+ </div><div class="procedure" id="procedure-Configuring_NetworkManager_to_Connect_to_a_Network_Automatically_When_Detected"><h6>手順6.1 Configuring NetworkManager to Connect to a Network Automatically When Detected</h6><ol class="1"><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guilabel"><strong>Network Settings</strong></span>.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Network </strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the type of connection from the left-hand-side menu.
+ </div></li><li class="step"><div class="para">
+ Click on <span class="guilabel"><strong>Configure</strong></span>
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Connect automatically</strong></span> to cause <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the connection whenever <span class="application"><strong>NetworkManager</strong></span> detects that it is available. Unselect the checkbox if you do not want <span class="application"><strong>NetworkManager</strong></span> to connect automatically. If the box is unchecked, you will have to select that connection manually in the <span class="application"><strong>NetworkManager</strong></span> applet's initial menu to cause it to connect.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>戻る</strong>6.2.2. Configuring New and Editing Existing Conne...</a></li><li class="up"><a accesskey="u" href="#"><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-User_and_System_Connections.html"><strong>次へ</strong>6.2.4. User and System Connections</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Creating_a_Yum_Repository.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Creating_a_Yum_Repository.html
new file mode 100644
index 0000000..36dc99c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Creating_a_Yum_Repository.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.3.6. Yum リポジトリーの作成</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="4.3. Yum と Yum リポジトリーの設定" /><link rel="prev" href="sec-Managing_Yum_Repositories.html" title="4.3.5. Yum リポジトリの追加・有効化および無効化" /><link rel="next" href="sec-Yum_Plugins.html" title="4.4. Yum プラグイン" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hre
f="sec-Managing_Yum_Repositories.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Yum_Plugins.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Creating_a_Yum_Repository"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.6. Yum リポジトリーの作成</h3></div></div></div><a id="idm65199488" class="indexterm"></a><div class="para">
+ Yum リポジトリーを構築するには、これらの手順に従ってください:
+ </div><div class="procedure" id="procedure-Setting_Up_a_Yum_repository"><ol class="1"><li class="step"><div class="para">
+ <span class="package">createrepo</span> パッケージのインストール:
+ </div><pre class="screen">~]# <code class="command">yum install createrepo</code></pre></li><li class="step"><div class="para">
+ <code class="filename">/mnt/local_repo/</code> のような 1 つのディレクトリーに全パッケージをコピーします。
+ </div></li><li class="step"><div class="para">
+ そのディレクトリーで <code class="command">createrepo --database</code> を実行します:
+ </div><pre class="screen">~]# <code class="command">createrepo --database /mnt/local_repo</code></pre></li></ol></div><div class="para">
+ This creates the necessary metadata for your Yum repository, as well as the <span class="application"><strong>sqlite</strong></span> database for speeding up <code class="command">yum</code> operations.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Managing_Yum_Repositories.html"><strong>戻る</strong>4.3.5. Yum リポジトリの追加・有効化および無効化</a></li><li class="up"><a accesskey="u" href="#"><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-Yum_Plugins.html"><strong>次へ</strong>4.4. Yum プラグイン</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html
new file mode 100644
index 0000000..f1fcb17
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="第22章 Working with Kernel Modules" /><link rel="prev" href="ch-Working_with_Kernel_Modules.html" title="第22章 Working with Kernel Modules" /><link rel="next" href="sec-Loading_a_Module.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-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">22.2. Displaying Information About a Module</h2></div></div></div><a id="idm72555232" class="indexterm"></a><a id="idm72553312" class="indexterm"></a><a id="idm72550912" 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="package">module-init-tools</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>例22.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/2.6.32-71.el6.x86_64/kernel/drivers/net/e1000e/e1000e.ko
+version: 1.2.7-k2
+license: GPL
+description: Intel(R) PRO/1000 Network Driver
+author: Intel Corporation, <linux.nics at intel.com>
+srcversion: 93CB73D3995B501872B2982
+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:
+vermagic: 2.6.32-71.el6.x86_64 SMP mod_unload modversions
+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)
+parm: EEE:Enable/disable on parts that support the feature (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>例22.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: EEE:Enable/disable on parts that support the feature (array of 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>第22章 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>22.3. モジュールの読み込み方法</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Displaying_Package_Information.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Displaying_Package_Information.html
new file mode 100644
index 0000000..71e1f07
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Displaying_Package_Information.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>4.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="4.2. パッケージとパッケージ グループ" /><link rel="prev" href="sec-Listing_Packages.html" title="4.2.2. パッケージの一覧" /><link rel="next" href="sec-Installing.html" title="4.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="sec-Listing_Packages.htm
l"><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">4.2.3. パッケージ情報の表示</h3></div></div></div><a id="idm72901392" class="indexterm"></a><a id="idm72899504" class="indexterm"></a><div class="para">
+ 複数のパッケージに関する情報を表示するには（ここでもグロブ表現が有効です）、以下のコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">info</code> <em class="replaceable"><code>package_name</code></em>…</pre><div class="para">
+ たとえば、 <span class="package">abrt</span> パッケージに関する情報を表示するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum info abrt</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+Name : abrt
+Arch : x86_64
+Version : 2.0.1
+Release : 2.fc15
+Size : 806 k
+Repo : installed
+From repo : fedora
+Summary : Automatic bug detection and reporting tool
+URL : https://fedorahosted.org/abrt/
+License : GPLv2+
+Description : abrt is a tool to help users to detect defects in applications and
+ : to create a bug report with all informations needed by maintainer
+ : to fix it. It uses plugin system to extend its functionality.</pre><a id="idm69496736" class="indexterm"></a><a id="idm69494848" class="indexterm"></a><div class="para">
+ <code class="command">yum info <em class="replaceable"><code>package_name</code></em></code> コマンドは <code class="command">rpm -q --info <em class="replaceable"><code>package_name</code></em></code> コマンドに似ていますが、RPM パッケージが見つけられた Yum リポジトリの ID を追加情報として提供します。（出力において <code class="computeroutput">From repo:</code> 行を探してください）。
+ </div><div class="para">
+ 以下のコマンドを使用することにより、代替物とパッケージに関する有用な情報を Yum データベースに問い合わせすることもできます:
+ </div><pre class="synopsis"><code class="command">yumdb</code> <code class="option">info</code> <em class="replaceable"><code>package_name</code></em></pre><div class="para">
+ このコマンドは、パッケージのチェックサム（および、それを生成するために使用された SHA-256 のようなアルゴリズム）、パッケージをインストールするために呼び出されたコマンドラインに与えられたコマンド（もしあれば）、パッケージがシステムにインストールされた理由（ここで <code class="computeroutput">user</code> はユーザーによりインストールされたことを意味します、<code class="computeroutput">dep</code> は依存性のためもたらされたことを意味します。）を含め、パッケージに関するさらなる情報を提供します。たとえば、<span class="package">yum</span> パッケージに関するさらなる情報を表示するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yumdb info yum</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+yum-3.2.29-4.fc15.noarch
+ checksum_data = 249f21fb43c41381c8c9b0cd98d2ea5fa0aa165e81ed2009cfda74c05af67246
+ checksum_type = sha256
+ from_repo = fedora
+ from_repo_revision = 1304429533
+ from_repo_timestamp = 1304442346
+ installed_by = 0
+ reason = user
+ releasever = $releasever</pre><div class="para">
+ <code class="command">yumdb</code> コマンドの詳細は <span class="bold bold"><strong>yumdb</strong></span>(8) マニュアルページを参照してください。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Listing_Packages.html"><strong>戻る</strong>4.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="sec-Installing.html"><strong>次へ</strong>4.2.4. パッケージのインストール</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_Connections.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_Connections.html
new file mode 100644
index 0000000..644284f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_Connections.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>6.3. Establishing Connections</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-NetworkManager.html" title="第6章 NetworkManager" /><link rel="prev" href="sec-User_and_System_Connections.html" title="6.2.4. User and System Connections" /><link rel="next" href="sec-Establishing_a_Wireless_Connection.html" title="6.3.2. Establishing a Wireless Connection" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-User_and_System_Connections
.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_Wireless_Connection.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Establishing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Establishing Connections</h2></div></div></div><div class="section" id="sec-Establishing_a_Wired_Ethernet_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.1. Establishing a Wired (Ethernet) Connection</h3></div></div></div><div class="para">
+ To establish a wired network connection, click on the <span class="application"><strong>NetworkManager</strong></span> applet to open its menu, then click on <span class="guilabel"><strong>Network Settings</strong></span>. This opens the <span class="guilabel"><strong>Network</strong></span> window.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Wired</strong></span> menu entry and then click <span class="guilabel"><strong>Configure</strong></span>.
+ </div><div class="figure" id="exam-Establishing_a_Wired_Ethernet_Connection"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-Editing_Wired_Connection_Gnome3"><img src="images/Network_Configuration-NM-Editing_Wired_Connection_Gnome3.png" alt="Editing the newly-created Wired connection 1" /><div class="longdesc"><div class="para">
+ A screen shot of Network Manager's Wired tab
+ </div></div></div></div><h6>図6.5 Editing the newly-created Wired connection 1</h6></div><br class="figure-break" /><div class="para">
+ The system startup scripts create and configure a single wired connection called <span class="guilabel"><strong>System eth0</strong></span> by default on all systems. Although you can edit <span class="guilabel"><strong>System eth0</strong></span>, creating a new wired connection for your custom settings is recommended. You can create a new wired connection by selecting the <span class="guilabel"><strong>Wired</strong></span> tab and clicking the <span class="guibutton"><strong>Add</strong></span> button.
+ </div><div class="note" id="note-The_dialog_for_adding_and_editing_connections_is_the_same"><div class="admonition_header"><h2>The dialog for adding and editing connections is the same</h2></div><div class="admonition"><div class="para">
+ When you add a new connection by clicking the <span class="guibutton"><strong>Add</strong></span> button, <span class="application"><strong>NetworkManager</strong></span> creates a new configuration file for that connection and then opens the same dialog that is used for editing an existing connection. There is no difference between these dialogs. In effect, you are always editing a connection; the difference only lies in whether that connection previously existed or was just created by <span class="application"><strong>NetworkManager</strong></span> when you clicked <span class="guibutton"><strong>Add</strong></span>.
+ </div></div></div><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wired">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>Wired</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">「Connecting to a Network Automatically」</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-User_and_System_Connections.html">「User and System Connections」</a> for details.
+ </div></li></ul></div><h4 id="bh-Configuring_the_Wired_Tab">Configuring the Wired Tab</h4><div class="para">
+ The final two configurable settings are located within the <span class="guilabel"><strong>Wired</strong></span> tab itself: the first is a text-entry field where you can specify a MAC (Media Access Control) address, and the second allows you to specify the MTU (Maximum Transmission Unit) value. Normally, you can leave the <span class="guilabel"><strong>MAC address</strong></span> field blank and the <span class="guilabel"><strong>MTU</strong></span> set to <strong class="userinput"><code>automatic</code></strong>. These defaults will suffice unless you are associating a wired connection with a second or specific NIC, or performing advanced networking. In such cases, refer to the following descriptions:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MAC Address</strong></span> </span></dt><dd><div class="para">
+ Network hardware such as a Network Interface Card (NIC) has a unique MAC address (Media Access Control; also known as a <em class="firstterm">hardware address</em>) that identifies it to the system. Running the <code class="command">ip addr</code> command will show the MAC address associated with each interface. For example, in the following <code class="command">ip addr</code> output, the MAC address for the <span class="guilabel"><strong>eth0</strong></span> interface (which is <code class="computeroutput"> 52:54:00:26:9e:f1</code>) immediately follows the <code class="computeroutput">link/ether</code> keyword:
+ </div><pre class="screen">~]# <code class="command">ip addr</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+ link/ether <span class="emphasis"><em>52:54:00:26:9e:f1</em></span> brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.251/24 brd 192.168.122.255 scope global eth0
+ inet6 fe80::5054:ff:fe26:9ef1/64 scope link
+ valid_lft forever preferred_lft forever</pre><div class="para">
+ A single system can have one or more NICs installed on it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific NIC with a specific connection (or connections). As mentioned, you can determine the MAC address using the <code class="command">ip addr</code> command, and then copy and paste that value into the <span class="guilabel"><strong>MAC address</strong></span> text-entry field.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ The MTU (Maximum Transmission Unit) value represents the size in bytes of the largest packet that the connection will use to transmit. This value defaults to <code class="constant">1500</code> when using IPv4, or a variable number <code class="constant">1280</code> or higher for IPv6, and does not generally need to be specified or changed.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-Wired">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your wired connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">「Connecting to a Network」</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port-based Network Access Control (PNAC), click the <span class="guilabel"><strong>802.1x Security</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_802.1x_Security">「Configuring 802.1x Security」</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv4_Settings.html">「Configuring IPv4 Settings」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv6_Settings.html">「Configuring IPv6 Settings」</a>.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-User_and_System_Connections.html"><strong>戻る</strong>6.2.4. User and System Connections</a></li><li class="up"><a accesskey="u" href="#"><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-Establishing_a_Wireless_Connection.html"><strong>次へ</strong>6.3.2. Establishing a Wireless Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_Routes.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_Routes.html
new file mode 100644
index 0000000..7390187
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_Routes.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>6.3.6. Establishing Routes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Establishing_Connections.html" title="6.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_a_DSL_Connection.html" title="6.3.5. Establishing a DSL Connection" /><link rel="next" href="sec-Configuring_Connection_Settings.html" title="6.4. Configuring Connection Settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_
a_DSL_Connection.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Connection_Settings.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Establishing_Routes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.6. Establishing Routes</h3></div></div></div><div class="figure" id="exam-User_and_System_Connections_Static-Routes"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-System_eth0-Routes"><img src="images/Network_Configuration-NM-System_eth0-Routes_Gnome3.png" alt="Configuring static network routes" /><div class="longdesc"><div class="para">
+ A screen shot of the static routes window
+ </div></div></div></div><h6>図6.10 Configuring static network routes</h6></div><br class="figure-break" /><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Address</strong></span> — The IP address of a network, sub-net or host.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Netmask</strong></span> — The netmask or prefix length of the IP address just entered.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Gateway</strong></span> — The IP address of the gateway leading to the network, sub-net or host.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Metric</strong></span> — A network cost, that is to say a preference value to give to this route. Lower values will be preferred over higher values.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Ignore automatically obtained routes</strong></span> </span></dt><dd><div class="para">
+ Select this check box to only use manually entered routes for the VPN tunnel.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use this connection only for resources on its network</strong></span> </span></dt><dd><div class="para">
+ Select this checkbox to prevent the VPN from becoming the default route. Then only the specific routes sent by the VPN server (or routes entered here manually) will be routed over the VPN tunnel.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_DSL_Connection.html"><strong>戻る</strong>6.3.5. Establishing a DSL Connection</a></li><li class="up"><a accesskey="u" href="#"><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_Connection_Settings.html"><strong>次へ</strong>6.4. Configuring Connection Settings</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_DSL_Connection.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_DSL_Connection.html
new file mode 100644
index 0000000..18ec39d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_DSL_Connection.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>6.3.5. Establishing a DSL Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Establishing_Connections.html" title="6.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_a_VPN_Connection.html" title="6.3.4. Establishing a VPN Connection" /><link rel="next" href="sec-Establishing_Routes.html" title="6.3.6. Establishing Routes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_a_VPN_Connection.html"
><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_Routes.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Establishing_a_DSL_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.5. Establishing a DSL Connection</h3></div></div></div><div class="para">
+ Open the Network Connections window by running, as a normal user:
+ </div><pre class="screen">~]$ <code class="command">nm-connection-editor &</code>
+</pre><div class="para">
+ Select the DSL tab and click <span class="guibutton"><strong>Add</strong></span>.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username used to authenticate with the service provider.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Service</strong></span> </span></dt><dd><div class="para">
+ Leave blank unless otherwise directed.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password supplied by the service provider.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_VPN_Connection.html"><strong>戻る</strong>6.3.4. Establishing a VPN Connection</a></li><li class="up"><a accesskey="u" href="#"><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-Establishing_Routes.html"><strong>次へ</strong>6.3.6. Establishing Routes</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_Mobile_Broadband_Connection.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_Mobile_Broadband_Connection.html
new file mode 100644
index 0000000..47f3c02
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_Mobile_Broadband_Connection.html
@@ -0,0 +1,105 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Establishing a Mobile Broadband Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Establishing_Connections.html" title="6.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_a_Wireless_Connection.html" title="6.3.2. Establishing a Wireless Connection" /><link rel="next" href="sec-Establishing_a_VPN_Connection.html" title="6.3.4. Establishing a VPN Connection" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Estab
lishing_a_Wireless_Connection.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_VPN_Connection.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Establishing_a_Mobile_Broadband_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.3. Establishing a Mobile Broadband Connection</h3></div></div></div><div class="para">
+ You can use <span class="application"><strong>NetworkManager</strong></span>'s mobile broadband connection abilities to connect to the following <em class="firstterm">2G</em> and <em class="firstterm">3G</em> services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 2G — <em class="firstterm">GPRS</em> (<em class="firstterm">General Packet Radio Service</em>) or <em class="firstterm">EDGE</em> (<em class="firstterm">Enhanced Data Rates for GSM Evolution</em>)
+ </div></li><li class="listitem"><div class="para">
+ 3G — <em class="firstterm">UMTS</em> (<em class="firstterm">Universal Mobile Telecommunications System</em>) or <em class="firstterm">HSPA</em> (<em class="firstterm">High Speed Packet Access</em>)
+ </div></li></ul></div><div class="para">
+ Your computer must have a mobile broadband device (modem), which the system has discovered and recognized, in order to create the connection. Such a device may be built into your computer (as is the case on many notebooks and netbooks), or may be provided separately as internal or external hardware. Examples include PC card, USB Modem or Dongle, mobile or cellular telephone capable of acting as a modem.
+ </div><div class="procedure" id="procedure-Adding_a_New_Mobile_Broadband_Connection"><h6>手順6.3 Adding a New Mobile Broadband Connection</h6><div class="para">
+ You can configure a mobile broadband connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div><ol class="1"><li class="step"><div class="para">
+ Open the Network Connections window by running, as a normal user:
+ </div><pre class="screen">~]$ <code class="command">nm-connection-editor &</code>
+</pre><div class="para">
+ The <span class="guilabel"><strong>Network Connections</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button to open the <span class="guilabel"><strong>Set up a Mobile Broadband Connection</strong></span> assistant.
+ </div></li><li class="step"><div class="para">
+ Under <span class="guilabel"><strong>Create a connection for this mobile broadband device</strong></span>, choose the 2G- or 3G-capable device you want to use with the connection. If the dropdown menu is inactive, this indicates that the system was unable to detect a device capable of mobile broadband. In this case, click <span class="guilabel"><strong>Cancel</strong></span>, ensure that you do have a mobile broadband-capable device attached and recognized by the computer and then retry this procedure. Click the <span class="guilabel"><strong>Forward</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the country where your service provider is located from the list and click the <span class="guilabel"><strong>Forward</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select your provider from the list or enter it manually. Click the <span class="guilabel"><strong>Forward</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select your payment plan from the dropdown menu and confirm the <em class="firstterm">Access Point Name</em> (<acronym class="acronym">APN</acronym>) is correct. Click the <span class="guilabel"><strong>Forward</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Apply</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Edit the mobile broadband-specific settings by referring to the <span class="emphasis"><em>Configuring the Mobile Broadband Tab</em></span> description below .
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Mobile_Broadband_Connection"><h6>手順6.4 Editing an Existing Mobile Broadband Connection</h6><div class="para">
+ Follow these steps to edit an existing mobile broadband connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Open the Network Connections window by running, as a normal user:
+ </div><pre class="screen">~]$ <code class="command">nm-connection-editor &</code>
+</pre><div class="para">
+ The <span class="guilabel"><strong>Network Connections</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Select the connection you wish to edit and click the <span class="guilabel"><strong>Edit</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">「Connecting to a Network Automatically」</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-User_and_System_Connections.html">「User and System Connections」</a> for details.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Edit the mobile broadband-specific settings by referring to the <span class="emphasis"><em>Configuring the Mobile Broadband Tab</em></span> description below .
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-mobile_broadband">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your mobile broadband connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">「Connecting to a Network」</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Point-to-point settings for the connection, click the <span class="guilabel"><strong>PPP Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_PPP_Point-to-Point_Settings.html">「Configuring PPP (Point-to-Point) Settings」</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv4_Settings.html">「Configuring IPv4 Settings」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv6_Settings.html">「Configuring IPv6 Settings」</a>.
+ </div></li></ul></div><h4 id="bh-Configuring_the_Mobile_Broadband_Tab">Configuring the Mobile Broadband Tab</h4><div class="para">
+ If you have already added a new mobile broadband connection using the assistant (refer to <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html#procedure-Adding_a_New_Mobile_Broadband_Connection">手順6.3「Adding a New Mobile Broadband Connection」</a> for instructions), you can edit the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab to disable roaming if home network is not available, assign a network ID, or instruct <span class="application"><strong>NetworkManager</strong></span> to prefer a certain technology (such as 3G or 2G) when using the connection.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Number</strong></span> </span></dt><dd><div class="para">
+ The number that is dialed to establish a PPP connection with the GSM-based mobile broadband network. This field may be automatically populated during the initial installation of the broadband device. You can usually leave this field blank and enter the <span class="guilabel"><strong>APN</strong></span> instead.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username used to authenticate with the network. Some providers do not provide a username, or accept any username when connecting to the network.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password used to authenticate with the network. Some providers do not provide a password, or accept any password.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>APN</strong></span> </span></dt><dd><div class="para">
+ Enter the <em class="firstterm">Access Point Name</em> (<acronym class="acronym">APN</acronym>) used to establish a connection with the GSM-based network. Entering the correct APN for a connection is important because it often determines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ how the user is billed for their network usage; and/or
+ </div></li><li class="listitem"><div class="para">
+ whether the user has access to the Internet, an intranet, or a subnetwork.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Network ID</strong></span> </span></dt><dd><div class="para">
+ Entering a <span class="guilabel"><strong>Network ID</strong></span> causes <span class="application"><strong>NetworkManager</strong></span> to force the device to register only to a specific network. This can be used to ensure the connection does not roam when it is not possible to control roaming directly.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Type</strong></span> </span></dt><dd><div class="para">
+ <span class="guilabel"><strong>Any</strong></span> — The default value of <span class="guilabel"><strong>Any</strong></span> leaves the modem to select the fastest network.
+ </div><div class="para">
+ <span class="guilabel"><strong>3G (UMTS/HSPA)</strong></span> — Force the connection to use only 3G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>2G (GPRS/EDGE)</strong></span> — Force the connection to use only 2G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 3G (UMTS/HSPA)</strong></span> — First attempt to connect using a 3G technology such as HSPA or UMTS, and fall back to GPRS or EDGE only upon failure.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 2G (GPRS/EDGE)</strong></span> — First attempt to connect using a 2G technology such as GPRS or EDGE, and fall back to HSPA or UMTS only upon failure.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow roaming if home network is not available</strong></span> </span></dt><dd><div class="para">
+ Uncheck this box if you want <span class="application"><strong>NetworkManager</strong></span> to terminate the connection rather than transition from the home network to a roaming one, thereby avoiding possible roaming charges. If the box is checked, <span class="application"><strong>NetworkManager</strong></span> will attempt to maintain a good connection by transitioning from the home network to a roaming one, and vice versa.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PIN</strong></span> </span></dt><dd><div class="para">
+ If your device's <em class="firstterm">SIM</em> (<em class="firstterm">Subscriber Identity Module</em>) is locked with a <em class="firstterm">PIN</em> (<em class="firstterm">Personal Identification Number</em>), enter the PIN so that <span class="application"><strong>NetworkManager</strong></span> can unlock the device. <span class="application"><strong>NetworkManager</strong></span> must unlock the SIM if a PIN is required in order to use the device for any purpose.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_Wireless_Connection.html"><strong>戻る</strong>6.3.2. Establishing a Wireless Connection</a></li><li class="up"><a accesskey="u" href="#"><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-Establishing_a_VPN_Connection.html"><strong>次へ</strong>6.3.4. Establishing a VPN Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_VPN_Connection.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_VPN_Connection.html
new file mode 100644
index 0000000..74547b0
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_VPN_Connection.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>6.3.4. Establishing a VPN Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Establishing_Connections.html" title="6.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_a_Mobile_Broadband_Connection.html" title="6.3.3. Establishing a Mobile Broadband Connection" /><link rel="next" href="sec-Establishing_a_DSL_Connection.html" title="6.3.5. Establishing a DSL Connection" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_a_Mobile_Broadband_Connection.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_DSL_Connection.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Establishing_a_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.4. Establishing a VPN Connection</h3></div></div></div><div class="para">
+ Establishing an encrypted Virtual Private Network (VPN) enables you to communicate securely between your Local Area Network (LAN), and another, remote LAN. After successfully establishing a VPN connection, a VPN router or gateway performs the following actions upon the packets you transmit:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ it adds an <em class="firstterm">Authentication Header</em> for routing and authentication purposes;
+ </div></li><li class="listitem"><div class="para">
+ it encrypts the packet data; and,
+ </div></li><li class="listitem"><div class="para">
+ it encloses the data with an Encapsulating Security Payload (ESP), which constitutes the decryption and handling instructions.
+ </div></li></ol></div><div class="para">
+ The receiving VPN router strips the header information, decrypts the data, and routes it to its intended destination (either a workstation or other node on a network). Using a network-to-network connection, the receiving node on the local network receives the packets already decrypted and ready for processing. The encryption/decryption process in a network-to-network VPN connection is therefore transparent to clients.
+ </div><div class="para">
+ Because they employ several layers of authentication and encryption, VPNs are a secure and effective means of connecting multiple remote nodes to act as a unified intranet.
+ </div><div class="procedure" id="procedure-Adding_a_New_VPN_Connection"><h6>手順6.5 Adding a New VPN Connection</h6><ol class="1"><li class="step"><div class="para">
+ You can configure a new VPN connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the <span class="guilabel"><strong>VPN</strong></span> menu entry.
+ </div></li><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area. Clicking on the <span class="guilabel"><strong>Network Settings</strong></span> menu entry opens the <span class="guilabel"><strong>Network</strong></span> window, from where you can view some basic network configuration information and initiate configuration tasks.
+ </div></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>VPN</strong></span> menu entry followed by <span class="guilabel"><strong>Configure</strong></span> and proceed to <a class="xref" href="sec-Establishing_a_VPN_Connection.html">「Establishing a VPN Connection」</a>. If there is no VPN menu entry click on the plus sign at the bottom. A dialog box appears. Ensure the interface is set to VPN.
+ </div><div class="note" id="note-VPN-plug-in-is-required"><div class="admonition_header"><h2>A VPN plug-in is required</h2></div><div class="admonition"><div class="para">
+ The appropriate NetworkManager VPN plug-in for the VPN type you want to configure must be installed. (refer to <a class="xref" href="sec-Installing.html">「パッケージのインストール」</a> for more information on how to install new packages in Fedora 17).
+ </div></div></div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Create</strong></span> button to open the <span class="guilabel"><strong>Choose a VPN Connection Type</strong></span> assistant.
+ </div></li><li class="step" id="Network_Configuration-VPN-step2"><div class="para">
+ Select the VPN protocol for the gateway you are connecting to from the dropdown menu. The VPN protocols available for selection in the dropdown menu corresponds to the NetworkManager VPN plug-ins installed. For example, if the <span class="package">NetworkManager VPN plug-in for openswan</span>is installed then the IPsec based VPN will be selectable from the dropdown menu.
+ </div><div class="para">
+ After selecting the correct one, press the <span class="guibutton"><strong>Create...</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Editing VPN Connection <em class="replaceable"><code>1</code></em> </strong></span> window then appears. This window presents settings customized for the type of VPN connection you selected in <a class="xref" href="sec-Establishing_a_VPN_Connection.html#Network_Configuration-VPN-step2">ステップ 5</a>.
+ </div></li></ol></div><div class="procedure"><div class="para">
+ You can configure an existing VPN connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the <span class="guilabel"><strong>VPN</strong></span> menu entry.
+ </div><ol class="1"><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Network Settings</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>VPN</strong></span> menu entry.
+ </div></li><li class="step"><div class="para">
+ Select the connection you wish to edit and click the <span class="guilabel"><strong>Configure</strong></span> button.
+ </div></li></ol></div><div class="figure" id="exam-Editing-VPN-connection"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_Editing-VPN-connection-1_Gnome3"><img src="images/Network_Configuration_NM_Editing-VPN-connection-1_Gnome3.png" alt="Editing the newly-created VPN connection 1." /><div class="longdesc"><div class="para">
+ A screenshot of the Editing VPN connection 1 window. The VPN tab is on the left and in the foreground
+ </div></div></div></div><h6>図6.9 Editing the newly-created VPN connection 1.</h6></div><br class="figure-break" /><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-vpn">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>VPN</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">「Connecting to a Network Automatically」</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-User_and_System_Connections.html">「User and System Connections」</a> for details.
+ </div></li></ul></div><h4 id="bh-Configuring_the_VPN_Tab">Configuring the VPN Tab</h4><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Gateway</strong></span> </span></dt><dd><div class="para">
+ The name or IP address of the remote VPN gateway.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Group name</strong></span> </span></dt><dd><div class="para">
+ The name of a VPN group configured on the remote gateway.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User password</strong></span> </span></dt><dd><div class="para">
+ If required, enter the password used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Group password</strong></span> </span></dt><dd><div class="para">
+ If required, enter the password used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User name</strong></span> </span></dt><dd><div class="para">
+ If required, enter the username used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Phase1 Algorithms</strong></span> </span></dt><dd><div class="para">
+ If required, enter the algorithms to be used to authenticate and set up an encrypted channel.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Phase2 Algorithms</strong></span> </span></dt><dd><div class="para">
+ If required, enter the algorithms to be used for the IPsec negotiations.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Domain</strong></span> </span></dt><dd><div class="para">
+ If required, enter the Domain Name.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>NAT traversal</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Cisco UDP (default)</strong></span> — IPsec over UDP.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>NAT-T</strong></span> — ESP encapsulation and IKE extensions are used to handle NAT Traversal.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Disabled</strong></span> — No special NAT measures required.
+ </div><div class="para">
+ <span class="guilabel"><strong>Disable Dead Peer Detection</strong></span> — Disable the sending of probes to the remote gateway or endpoint.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-vpn">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your new VPN connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">「Connecting to a Network」</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv4_Settings.html">「Configuring IPv4 Settings」</a>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>戻る</strong>6.3.3. Establishing a Mobile Broadband Connection</a></li><li class="up"><a accesskey="u" href="#"><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-Establishing_a_DSL_Connection.html"><strong>次へ</strong>6.3.5. Establishing a DSL Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_Wireless_Connection.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_Wireless_Connection.html
new file mode 100644
index 0000000..3c02f91
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Establishing_a_Wireless_Connection.html
@@ -0,0 +1,98 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Establishing a Wireless Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Establishing_Connections.html" title="6.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_Connections.html" title="6.3. Establishing Connections" /><link rel="next" href="sec-Establishing_a_Mobile_Broadband_Connection.html" title="6.3.3. Establishing a Mobile Broadband Connection" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-E
stablishing_Connections.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Establishing_a_Wireless_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.3.2. Establishing a Wireless Connection</h3></div></div></div><div class="para">
+ This section explains how to use <span class="application"><strong>NetworkManager</strong></span> to configure a wireless (also known as Wi-Fi or 802.1<em class="replaceable"><code>a/b/g/n</code></em>) connection to an Access Point.
+ </div><div class="para">
+ To configure a mobile broadband (such as 3G) connection, refer to <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html">「Establishing a Mobile Broadband Connection」</a>.
+ </div><h4 id="bh-Quickly_Connecting_to_an_Available_Access_Point">Quickly Connecting to an Available Access Point</h4><div class="para">
+ The easiest way to connect to an available access point is to click on the <span class="application"><strong>NetworkManager</strong></span> applet, locate the <em class="firstterm">Service Set Identifier</em> (SSID) of the access point in the list of available networks, and click on it. If the access point is secured, a dialog prompts you for authentication.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> tries to auto-detect the type of security used by the access point. If there are multiple possibilities, <span class="application"><strong>NetworkManager</strong></span> guesses the security type and presents it in the <span class="guilabel"><strong>Wireless security</strong></span> dropdown menu. To see if there are multiple choices, click the <span class="guilabel"><strong>Wireless security</strong></span> dropdown menu and select the type of security the access point is using. If you are unsure, try connecting to each type in turn. Finally, enter the key or passphrase in the <span class="guilabel"><strong>Password</strong></span> field. Certain password types, such as a 40-bit WEP or 128-bit WPA key, are invalid unless they are of a requisite length. The <span class="guilabel"><strong>Connect</strong></span> button will remain inactive until you enter a key of the length required for the selected securit
y type. To learn more about wireless security, refer to <a class="xref" href="sec-Configuring_Wireless_Security.html">「Configuring Wireless Security」</a>.
+ </div><div class="para">
+ If <span class="application"><strong>NetworkManager</strong></span> connects to the access point successfully, its applet icon will change into a graphical indicator of the wireless connection's signal strength.
+ </div><div class="figure" id="exam-Establishing_a_Wireless_Connection_Signal-Strength-Applet-icon"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_AppletStates_WiFi_Gnome3"><img src="images/Network_Configuration_NM_AppletStates_WiFi_Gnome3.png" alt="Applet icon indicating wireless connection signal strength" /><div class="longdesc"><div class="para">
+ A screen shot of the Signal Strength Applet icon indicating wireless connection signal strength
+ </div></div></div></div><h6>図6.6 Applet icon indicating wireless connection signal strength</h6></div><br class="figure-break" /><h4 id="bh-Connecting_to_a_Hidden_Wireless_Network">Connecting to a Hidden Wireless Network</h4><div class="para">
+ All access points have a <em class="firstterm">Service Set Identifier</em> (SSID) to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID, authentication method, and secrets.
+ </div><div class="para">
+ To connect to a hidden wireless network, click <span class="application"><strong>NetworkManager</strong></span>'s applet icon and then click <span class="guilabel"><strong>Network Settings</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears. Select the <span class="guilabel"><strong>Wireless</strong></span> menu entry and then click to the right of the <span class="guilabel"><strong>Network Name</strong></span> to activate the drop-down list. Select <span class="guilabel"><strong>Other</strong></span>. The <span class="guilabel"><strong>Hidden wireless network</strong></span> dialog window appears.
+ </div><div class="figure" id="exam-Establishing_a_Wireless_Connection_Wireless-Tab"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3"><img src="images/Network_Configuration_NM_Wireless_Hidden-wireless-network_Gnome3.png" alt="Hidden wireless network dialog window" /><div class="longdesc"><div class="para">
+ A screen shot of NetworkManager's Hidden wireless network dialog window
+ </div></div></div></div><h6>図6.7 Hidden wireless network dialog window</h6></div><br class="figure-break" /><div class="para">
+ If you have connected to the hidden network before, use the <span class="guilabel"><strong>Connection</strong></span> drop-down list to select it, and click <span class="guibutton"><strong>Connect</strong></span>. If you have not, leave the <span class="guilabel"><strong>Connection</strong></span> dropdown as <span class="guimenuitem"><strong>New...</strong></span>, enter the SSID of the hidden network, select its <span class="guilabel"><strong>Wireless security</strong></span> method, enter the correct authentication secrets, and click <span class="guibutton"><strong>Connect</strong></span>.
+ </div><div class="para">
+ For more information on wireless security settings, refer to <a class="xref" href="sec-Configuring_Wireless_Security.html">「Configuring Wireless Security」</a>.
+ </div><h4 id="bh-Editing_a_Connection_or_Creating_a_Completely_New_One">Editing a Connection, or Creating a Completely New One</h4><div class="para">
+ You can create a new connection by clicking on the <span class="application"><strong>NetworkManager</strong></span> applet to open its menu.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Network Settings</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Wireless</strong></span> menu entry.
+ </div></li><li class="step"><div class="para">
+ Click to the right of the <span class="guilabel"><strong>Network Name</strong></span> to activate the drop-down list.
+ </div></li><li class="step"><div class="para">
+ Select the SSID you want to connect to.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Configure</strong></span> button. The editing a wireless connection window appears.
+ </div></li></ol></div><div class="figure" id="exam-Network_Connections_Window_Wireless-Tab"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-Editing_Wireless_Connection_Gnome3"><img src="images/Network_Configuration-NM-Editing_Wireless_Connection_Gnome3.png" alt="Editing the newly-created Wireless connection" /><div class="longdesc"><div class="para">
+ A screen shot of the NetworkManager's editing a wireless connection window. The Wireless tab has been selected on the left.
+ </div></div></div></div><h6>図6.8 Editing the newly-created Wireless connection</h6></div><br class="figure-break" /><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wireless">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>Wireless</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window. By default, wireless connections are named the same as the <em class="firstterm">SSID</em> of the wireless access point. You can rename the wireless connection without affecting its ability to connect, as in the example above, but it is recommended to retain the SSID name.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">「Connecting to a Network Automatically」</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-User_and_System_Connections.html">「User and System Connections」</a> for details.
+ </div></li></ul></div><h4 id="bh-Configuring_the_Wireless_Tab">Configuring the Wireless Tab</h4><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>SSID</strong></span> </span></dt><dd><div class="para">
+ All access points have a <em class="firstterm">Service Set identifier</em> to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID (and authentication secrets).
+ </div><div class="para">
+ For information on connecting to a hidden wireless network, refer to <a class="xref" href="sec-Establishing_a_Wireless_Connection.html#bh-Connecting_to_a_Hidden_Wireless_Network">6.3.2項「Connecting to a Hidden Wireless Network」</a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Mode</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Infrastructure</strong></span> — Set <span class="guilabel"><strong>Mode</strong></span> to <span class="guimenuitem"><strong>Infrastructure</strong></span> if you are connecting to a dedicated wireless access point or one built into a network device such as a router or a switch.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Ad-hoc</strong></span> — Set <span class="guilabel"><strong>Mode</strong></span> to <span class="guimenuitem"><strong>Ad-hoc</strong></span> if you are creating a peer-to-peer network for two or more mobile devices to communicate directly with each other. If you use <span class="guimenuitem"><strong>Ad-hoc</strong></span> mode, referred to as <em class="firstterm">Independent Basic Service Set</em> (<acronym class="acronym">IBSS</acronym>) in the 802.11 standard, you must ensure that the same <span class="guilabel"><strong>SSID</strong></span> is set for all participating wireless devices, and that they are all communicating over the same channel.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>BSSID</strong></span> </span></dt><dd><div class="para">
+ The Basic Service Set Identifier (BSSID) is the MAC address of the specific wireless access point you are connecting to when in <span class="guilabel"><strong>Infrastructure</strong></span> mode. This field is blank by default, and you are able to connect to a wireless access point by <span class="guilabel"><strong>SSID</strong></span> without having to specify its <span class="guilabel"><strong>BSSID</strong></span>. If the BSSID is specified, it will force the system to associate to a specific access point only.
+ </div><div class="para">
+ For ad-hoc networks, the <span class="guilabel"><strong>BSSID</strong></span> is generated randomly by the mac80211 subsystem when the ad-hoc network is created. It is not displayed by <span class="application"><strong>NetworkManager</strong></span>
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MAC address</strong></span> </span></dt><dd><div class="para">
+ Like an Ethernet Network Interface Card (NIC), a wireless adapter has a unique MAC address (Media Access Control; also known as a <em class="firstterm">hardware address</em>) that identifies it to the system. Running the <code class="command">ip addr</code> command will show the MAC address associated with each interface. For example, in the following <code class="command">ip addr</code> output, the MAC address for the <code class="computeroutput">wlan0</code> interface (which is <code class="computeroutput">00:1c:bf:02:f8:70</code>) immediately follows the <code class="computeroutput">link/ether</code> keyword:
+ </div><pre class="screen">~]# <code class="command">ip addr</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+ link/ether 52:54:00:26:9e:f1 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.251/24 brd 192.168.122.255 scope global eth0
+ inet6 fe80::5054:ff:fe26:9ef1/64 scope link
+ valid_lft forever preferred_lft forever
+3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
+ link/ether <span class="emphasis"><em>00:1c:bf:02:f8:70</em></span> brd ff:ff:ff:ff:ff:ff
+ inet 10.200.130.67/24 brd 10.200.130.255 scope global wlan0
+ inet6 fe80::21c:bfff:fe02:f870/64 scope link
+ valid_lft forever preferred_lft forever</pre><div class="para">
+ A single system could have one or more wireless network adapters connected to it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific wireless adapter with a specific connection (or connections). As mentioned, you can determine the MAC address using the <code class="command">ip addr</code> command, and then copy and paste that value into the <span class="guilabel"><strong>MAC address</strong></span> text-entry field.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ The MTU (Maximum Transmission Unit) value represents the size in bytes of the largest packet that the connection will use to transmit. If set to a non-zero number, only packets of the specified size or smaller will be transmitted. Larger packets are broken up into multiple Ethernet frames. It is recommended to leave this setting on <span class="guimenuitem"><strong>automatic</strong></span>.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-wireless">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing the wireless connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can successfully connect to your the modified connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">「Connecting to a Network」</a> for details on selecting and connecting to a network.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ security authentication for the wireless connection, click the <span class="guilabel"><strong>Wireless Security</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Wireless_Security.html">「Configuring Wireless Security」</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv4_Settings.html">「Configuring IPv4 Settings」</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv6_Settings.html">「Configuring IPv6 Settings」</a>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_Connections.html"><strong>戻る</strong>6.3. Establishing Connections</a></li><li class="up"><a accesskey="u" href="#"><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-Establishing_a_Mobile_Broadband_Connection.html"><strong>次へ</strong>6.3.3. Establishing a Mobile Broadband Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Finding_Packages_with_Filters.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Finding_Packages_with_Filters.html
new file mode 100644
index 0000000..f10e577
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Finding_Packages_with_Filters.html
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Using_Add_Remove_Software.html" title="5.2. ソフトウェアの追加/削除の使用" /><link rel="prev" href="sec-Using_Add_Remove_Software.html" title="5.2. ソフトウェアの追加/削除の使用" /><link rel="next" href="sec-Installing_and_Removing_Packages_and_Dependencies.html" title="5.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="Documenta
tion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Add_Remove_Software.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Finding_Packages_with_Filters"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.2. フィルターを用いたパッケージの検索</h3></div></div></div><a id="idm36804096" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>を開き、<span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアのソース</strong></span>をクリックすることにより、すべての<span class="emphasis"><em>設定済み</em></span>かつフィルターされていない（以下参照） <span class="application"><strong>Yum</strong></span> リポジトリの一覧を表示できます。一度ソフトウェアのソースが更新されると、<span class="application"><strong>PackageKit</strong></span> が<span class="guilabel"><strong>検索</strong></span>の問い合わせ結果をより速く取得できるよう、いくつかのフィルターを適用することに有益です。これはとくに、多くのパッケージ検索を実行するときに助けになります。<span class="guimenu"><strong>フィルター</strong></span>ドロップダウ
ンメニューにある4つのフィルターは一つの基準に一致するまたは一致しないことにより結果を分割するために使用されます。デフォルトで、<span class="application"><strong>PackageKit</strong></span> が起動するとき、これらのフィルターはすべて適用されませんが（<span class="guibutton"><strong>フィルターなし</strong></span>）、一度それらのどれかによりフィルターすると、そのフィルターは変更するか <span class="application"><strong>PackageKit</strong></span> を閉じるまで設定されたままになります。
+ </div><div class="para">
+ 通常システムにインストールされて<span class="emphasis"><em>いない</em></span>利用可能なパッケージを検索するので、<span class="guimenu"><strong>フィルター</strong></span> → <span class="guimenuitem"><strong>インストール済</strong></span> を選択し、<span class="guimenuitem"><strong>利用可能なもののみ</strong></span>ラジオボタンを選択します。
+ <a id="idm43972592" class="indexterm"></a>
+ <a id="idm18588080" class="indexterm"></a>
+ <a id="idm18586672" class="indexterm"></a>
+ <a id="idm18584816" class="indexterm"></a>
+ <a id="idm18582960" class="indexterm"></a>
+ </div><div class="figure" id="Graphical_Package_Management-filters-only_available"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-filters-available.png" alt="すでにインストールされているパッケージのフィルター" /><div class="longdesc"><div class="para">
+ filtering out packages which are already installed
+ </div></div></div></div><h6>図5.5 すでにインストールされているパッケージのフィルター</h6></div><br class="figure-break" /><div class="para">
+ <a id="idm62139440" class="indexterm"></a>
+ <a id="idm29462960" class="indexterm"></a>
+ <a id="idm29461072" class="indexterm"></a>
+ また、C ヘッダーファイルのように開発版が必要でなければ、<span class="guimenu"><strong>エンドユーザーのファイルのみ</strong></span>のためにフィルターできます。そして、そうするとき、興味がない <code class="filename"><em class="replaceable"><code>package_name</code></em>-devel</code> をすべてフィルターで消します。
+ </div><div class="figure" id="fig-Graphical_Package_Management-filters-only_end_user"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-filters-end-user.png" alt="検索結果の一覧からの開発パッケージのフィルター" /><div class="longdesc"><div class="para">
+ filtering out development packages from our results
+ </div></div></div></div><h6>図5.6 検索結果の一覧からの開発パッケージのフィルター</h6></div><br class="figure-break" /><div class="para">
+ サブメニューにある残り 2 つのフィルターは次のとおりです:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guisubmenu"><strong>グラフィカル</strong></span> <a id="idm73164480" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ GUI インターフェースを提供するアプリケーション（<span class="guibutton"><strong>グラフィカルなもののみ</strong></span>）、またはそうではないものに検索を絞ります。このフィルターは特別な機能を実行する GUI アプリケーションを閲覧するときに有用です。
+ </div></dd><dt class="varlistentry"><span class="term"><span class="guisubmenu"><strong>Free</strong></span> <a id="idm74809808" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ フリーソフトウェアであると考えられるパッケージを検索します。承認されたライセンスの詳細は <a href="https://fedoraproject.org/wiki/Licensing#SoftwareLicenses">Fedora Licensing List</a> を参照してください。
+ </div></dd></dl></div><div class="para">
+ 残りのチェックボックスのフィルターは必ずチェックまたは解除されます。それらは以下のものです:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guimenuitem"><strong>サブパッケージを隠す</strong></span></span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>サブパッケージを隠す</strong></span> <a id="idm44069648" class="indexterm"></a>
+ チェックボックスをチェックすることにより、一般的に必要なパッケージの依存性のみである、興味のないパッケージをフィルターします。たとえば、<span class="guimenuitem"><strong>サブパッケージを隠す</strong></span>をチェックして、 <code class="filename"><em class="replaceable"><code>package</code></em> </code> を検索することにより、以下の関連パッケージを<span class="guibutton"><strong>検索</strong></span>結果からフィルターで隠します（もし存在すれば）:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code>package</code></em>-devel</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code>package</code></em>-libs</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code>package</code></em>-libs-devel</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code>package</code></em>-debuginfo</code>
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><span class="guimenuitem"><strong>最新パッケージのみ</strong></span></span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>最新パッケージのみ</strong></span> <a id="idm55816720" class="indexterm"></a>
+ を選択すると、結果の一覧から同じパッケージの古いバージョンはすべてフィルターされます。これは一般的に期待することでしょう。
+ </div><div class="important" id="important-Using_the_Only_newest_items_filter"><div class="admonition_header"><h2>最新パッケージのみフィルターの使用</h2></div><div class="admonition"><div class="para">
+ <span class="guimenuitem"><strong>最新パッケージのみ</strong></span>を選択すると、結果の一覧からあらゆるパッケージの最新のバージョン以外はフィルターされます。このフィルターは、新しい（インストールされていない）パッケージの利用可能な最新バージョンを検索するために、しばしば<span class="guimenuitem"><strong>利用可能なもののみ</strong></span> フィルターと組み合わせられます。
+ </div></div></div></dd><dt class="varlistentry"><span class="term">ディストリ固有のパッケージのみ</span></dt><dd><div class="para">
+ 複数ライブラリのシステムにおいて<span class="guimenuitem"><strong>ディストリ固有のパッケージのみ</strong></span> <a id="idm59822496" class="indexterm"></a>
+ ボックスをãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€<span class="application"><strong>PackageKit</strong></span> ãŒ<span class="emphasis"><em>互æ›ãƒ¢ãƒ¼ãƒ‰</em></span>ã«ãŠã„ã¦å®Ÿè¡Œã™ã‚‹ã‚¢ãƒ¼ã‚テクãƒãƒ£ãƒ¼ã®ãŸã‚ã«ã‚³ãƒ³ãƒ‘イルã—ãŸãƒ‘ッケージã«å¯¾ã™ã‚‹çµæžœã‚’一覧表示ã™ã‚‹ã“ã¨ã‚’çœç•¥ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€AMD64 CPU ã‚’æŒã¤ 64ビットシステムã«ãŠã„ã¦ã“ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’有効ã«ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€AMD64 マシンã«ãŠã„ã¦å®Ÿè¡Œã§ãるパッケージã§ã‚ã£ã¦ã‚‚ã€32ビット x86 CPU アーã‚テクãƒãƒ£ãƒ¼ã®ãŸã‚ã«ãƒ“ルドã•ã‚ŒãŸãƒ‘ッケージをã™ã¹ã¦çµæžœã®ä¸€è¦§ã«è¡¨ç¤ºã—ãªã„よã†ã«ã—ã¾ã™ã€‚アーã‚テクãƒãƒ£ãƒ¼éžä¾å˜ã®ï¼ˆã¤ã¾ã‚Šã€<code class="filename">crontabs-1.10-32.1.el6.noarch.rpm</code> ã®ã‚ˆã†ãª <em class="firstterm">noarch</em>ã®ï¼‰ãƒ‘ッケージã¯ã€<span class="guimenuitem"><strong>ディストリ固有ã®ãƒ‘ッケージã®ã¿</strong></span>ã‚’ãƒã‚§ã
ƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã•ã‚Œã¾ã›ã‚“。ã“ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã¯ x86 マシンã®ã‚ˆã†ãªéžè¤‡æ•°ãƒ©ã‚¤ãƒ–ラリã®ã‚·ã‚¹ãƒ†ãƒ ã«å½±éŸ¿ã—ã¾ã›ã‚“。
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Add_Remove_Software.html"><strong>戻る</strong>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="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>次へ</strong>5.2.3. パッケージ（および依存するもの）のインストールおよび削除</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing.html
new file mode 100644
index 0000000..6c77e1d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="4.2. パッケージとパッケージ グループ" /><link rel="prev" href="sec-Displaying_Package_Information.html" title="4.2.3. パッケージ情報の表示" /><link rel="next" href="sec-Removing.html" title="4.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="sec-Displaying_Pac
kage_Information.html"><strong>戻る</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">4.2.4. パッケージのインストール</h3></div></div></div><a id="idm48900112" class="indexterm"></a><a id="idm48898704" class="indexterm"></a><div class="para">
+ Yum は単一のパッケージ、複数のパッケージ、および選択したパッケージのグループをインストールできます。
+ </div><h4 id="bh-Installing_Individual_packages">各パッケージのインストール</h4><div class="para">
+ 単一のパッケージおよびインストールされていない依存パッケージすべてをインストールするには、以下の形式でコマンドを入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">install</code> <em class="replaceable"><code>package_name</code></em></pre><div class="para">
+ 引数として名前を追加することにより、同時に複数のパッケージをインストールすることもできます:
+ </div><pre class="synopsis"><code class="command">yum</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">
+ AMD64 や Intel64 マシンのような <em class="firstterm">multilib</em> システムにおいてパッケージをインストールしているならば、パッケージ名に <em class="replaceable"><code>.arch</code></em> を追加することにより、（有効なリポジトリーにおいて利用可能ならば）パッケージのアーキテクチャーを指定できます。たとえば、<code class="systemitem">i586</code> の <span class="package">sqlite2</span> をインストールするには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum install sqlite2.i586</code></pre><div class="para">
+ 同じような名前の複数のパッケージを素早くインストールするためにグロブ表現を使用することができます:
+ </div><pre class="screen">~]# <code class="command">yum install audacious-plugins-\*</code></pre><div class="para">
+ パッケージ名とグロブ表現に加えて、ファイル名を <code class="command">yum install</code> に提供することもできます。インストールしたいバイナリの名前がわかっているならば、<code class="command">yum install</code> にパス名を与えることもできます:
+ </div><pre class="screen">~]# <code class="command">yum install /usr/sbin/named</code></pre><div class="para">
+ そして、<code class="command">yum</code> はそのパッケージ一覧を検索して、<code class="filename">/usr/sbin/named</code> を探して、もしあればインストールしたいかどうかを確認します。
+ </div><div class="note" id="note-Finding_which_package_owns_a_file"><div class="admonition_header"><h2>ファイルを所有するパッケージの検索</h2></div><div class="admonition"><div class="para">
+ <code class="filename">named</code> バイナリを含むパッケージをインストールしたいと思っているが、<code class="filename">bin</code> または <code class="filename">sbin</code> ディレクトリにインストールされるファイルがわからないならば、<code class="command">yum provides</code> コマンドをグロブ表現を用いて使用します:
+ </div><pre class="screen">~]# <code class="command">yum provides "*bin/named"</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+32:bind-9.8.0-3.P1.fc15.i686 : The Berkeley Internet Name Domain (BIND) DNS
+ : (Domain Name System) server
+Repo : fedora
+Matched from:
+Filename : /usr/sbin/named</pre><div class="para">
+ <code class="command">yum provides "*/<em class="replaceable"><code>file_name</code></em>"</code> は、<em class="replaceable"><code>file_name</code></em> を含むパッケージを探すための一般的かつ有用なテクニックです。
+ </div></div></div><h4 id="bh-Installing_a_Package_Group">パッケージグループのインストール</h4><a id="idm52244896" class="indexterm"></a><a id="idm46355680" class="indexterm"></a><div class="para">
+ パッケージグループはパッケージと似ています: それ自体は有用ではありませんが、あるものをインストールすることにより、共通の目的を取り扱っている依存したパッケージのグループを取ってきます。パッケージグループは名前と <em class="firstterm">groupid</em> を持ちます。<code class="command">yum grouplist -v</code> コマンドは、すべてのパッケージグループの名前と、それに続けて括弧内にグループ ID を一覧表示します。グループ ID は必ず、以下の例にある <code class="literal">kde-desktop</code> のように、括弧の最後の組にあります:
+ </div><pre class="screen">~]# <code class="command">yum -v grouplist kde\*</code>
+Not loading "blacklist" plugin, as it is disabled
+Loading "langpacks" plugin
+Loading "presto" plugin
+Loading "refresh-packagekit" plugin
+Not loading "whiteout" plugin, as it is disabled
+Adding en_US to language list
+Config time: 0.900
+Yum Version: 3.2.29
+Setting up Group Process
+rpmdb time: 0.002
+group time: 0.995
+Available Groups:
+ KDE Software Compilation (kde-desktop)
+ KDE Software Development (kde-software-development)
+Done</pre><div class="para">
+ 完全なグループ名を（グループ ID 部分なしで） <code class="command">groupinstall</code> に渡すことによりパッケージのグループをインストールできます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">groupinstall</code> <em class="replaceable"><code>group_name</code></em></pre><div class="para">
+ groupidを使用してインストールすることもできます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">groupinstall</code> <em class="replaceable"><code>groupid</code></em></pre><div class="para">
+ <span class="keysym">@</span>-記号（<code class="command">yum</code> に <code class="command">groupinstall</code> を実行したいことを伝えます）を前につけると、 <code class="command">install</code> コマンドにグループ ID を渡すこともできます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">install</code> @<em class="replaceable"><code>group</code></em></pre><div class="para">
+ たとえば、以下は代わりになりますが、<code class="literal">KDE Desktop</code> グループをインストールする同等の方法です:
+ </div><pre class="screen">~]# <code class="command">yum groupinstall "KDE Desktop"</code>
+~]# <code class="command">yum groupinstall kde-desktop</code>
+~]# <code class="command">yum install @kde-desktop</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Displaying_Package_Information.html"><strong>戻る</strong>4.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="sec-Removing.html"><strong>次へ</strong>4.2.5. パッケージの削除</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_More_Yum_Plugins.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_More_Yum_Plugins.html
new file mode 100644
index 0000000..e61d95e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_More_Yum_Plugins.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>4.4.2. 追加の Yum プラグインのインストール</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Yum_Plugins.html" title="4.4. Yum プラグイン" /><link rel="prev" href="sec-Yum_Plugins.html" title="4.4. Yum プラグイン" /><link rel="next" href="sec-Plugin_Descriptions.html" title="4.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="sec-Yum_Plugins.html"><strong>戻る</strong></a></li><li class="next"><a accesske
y="n" href="sec-Plugin_Descriptions.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Installing_More_Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.4.2. 追加の Yum プラグインのインストール</h3></div></div></div><div class="para">
+ Yum プラグインは通常 <code class="filename">yum-plugin-<em class="replaceable"><code>plugin_name</code></em></code> パッケージ命名規約に従いますが、必ずしもそうとは限りません。たとえば、<span class="application"><strong>presto</strong></span> プラグインを提供するパッケージは <code class="filename">yum-presto</code> という名前です。他のパッケージをインストールする方法と同じように Yum プラグインをインストールできます。たとえば、<span class="application"><strong>security</strong></span> プラグインをインストールするには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum install yum-plugin-security</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Yum_Plugins.html"><strong>戻る</strong>4.4. Yum プラグイン</a></li><li class="up"><a accesskey="u" href="#"><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-Plugin_Descriptions.html"><strong>次へ</strong>4.4.3. プラグインの説明</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Removing_Package_Groups.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Removing_Package_Groups.html
new file mode 100644
index 0000000..71291e7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Removing_Package_Groups.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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Using_Add_Remove_Software.html" title="5.2. ソフトウェアの追加/削除の使用" /><link rel="prev" href="sec-Installing_and_Removing_Packages_and_Dependencies.html" title="5.2.3. パッケージ（および依存するもの）のインストールおよび削除" /><link rel="next" href="sec-Viewing_the_Transaction_Log.html" title="5.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="Documenta
tion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Viewing_the_Transaction_Log.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Installing_and_Removing_Package_Groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.4. パッケージグループのインストールおよび削除</h3></div></div></div><a id="idm73195856" class="indexterm"></a><a id="idm66971264" class="indexterm"></a><a id="idm66969776" class="indexterm"></a><a id="idm66968320" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> は、<span class="guilabel"><strong>パッケージコレクション</strong></span>と呼ばれる <span class="application"><strong>Yum</strong></span> パッケージグループをインストールする機能もあります。<span class="guilabel"><strong>ソフトウェアの更新</strong></span>ウィンドウにおいてカテゴリーの左上の一覧にある<span class="guilabel"><strong>パッケージコレクション</strong></span>をクリックすることにより、インストールしたいパッケージグループをスクロールして検索することができます。この場合、チェコ語の言語サポート（<span class="guilabel"><strong>チェコ語のサポート</strong></span>グループ）をインストールしたいです。ボックスをチェックして、<span class="guibutton"><strong>適用</strong></span>をクリックすることにより、パッ
ケージグループの依存関係を満たすためにインストールしなければいけない<span class="emphasis"><em>追加の</em></span>パッケージの数を表示します。
+ </div><div class="figure" id="fig-Graphical_Package_Management-installing_a_package_group"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-package-group.png" alt="チェコ語サポートのパッケージグループのインストール" /><div class="longdesc"><div class="para">
+ Using PackageKit to install Czech language support with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>図5.9 チェコ語サポートのパッケージグループのインストール</h6></div><br class="figure-break" /><div class="para">
+ 同様に、インストールされたパッケージグループは、<span class="guilabel"><strong>パッケージコレクション</strong></span>を選択し、適切なチェックボックスをチェック解除し、適用することによりアンインストールできます。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>戻る</strong>5.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="sec-Viewing_the_Transaction_Log.html"><strong>次へ</strong>5.2.5. トランザクションログの表示</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html
new file mode 100644
index 0000000..05f05a7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.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>5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Using_Add_Remove_Software.html" title="5.2. ソフトウェアの追加/削除の使用" /><link rel="prev" href="sec-Finding_Packages_with_Filters.html" title="5.2.2. フィルターを用いたパッケージの検索" /><link rel="next" href="sec-Installing_and_Removing_Package_Groups.html" title="5.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="sec-Finding_Packages_with_Filters.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and_Removing_Package_Groups.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Installing_and_Removing_Packages_and_Dependencies"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.3. パッケージ（および依存するもの）のインストールおよび削除</h3></div></div></div><a id="idm40337776" class="indexterm"></a><a id="idm40336288" class="indexterm"></a><div class="para">
+ 2つのフィルター、<span class="guibutton"><strong>利用可能なもののみ</strong></span>および<span class="guibutton"><strong>エンドユーザーのファイルのみ</strong></span>を選択すると、<span class="application"><strong>htop</strong></span> 対話式プロセスビューアーを検索して、パッケージをハイライトします。いくつかの非常に有用な情報を得ることができます。これは、クリック可能なプロジェクトのホームページ、もしあれば、見つかった <span class="application"><strong>Yum</strong></span> パッケージグループ、パッケージのライセンス、適用できれば、アプリケーションを開ける GNOME メニュー位置、およびダウンロードしてインストールするときに関連するパッケージの容量を含みます。
+ </div><div class="figure" id="fig-Graphical_Package_Management-install"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-install.png" alt="PackageKit のソフトウェアの追加/削除ウィンドウを用いたパッケージの表示およびインストール" /><div class="longdesc"><div class="para">
+ PackageKit のソフトウェアの追加/削除ウィンドウを用いたパッケージの表示およびインストール
+ </div></div></div></div><h6>図5.7 PackageKit のソフトウェアの追加/削除ウィンドウを用いたパッケージの表示およびインストール</h6></div><br class="figure-break" /><div class="para">
+ パッケージã¾ãŸã¯ã‚°ãƒ«ãƒ¼ãƒ—ã®éš£ã«ã‚ã‚‹ãƒã‚§ãƒƒã‚¯ãƒœãƒƒã‚¯ã‚¹ã‚’ãƒã‚§ãƒƒã‚¯ã•ã‚Œã¦ã„ã‚‹ã¨ãã€ãã®é …ç›®ã¯ã™ã§ã«ã‚·ã‚¹ãƒ†ãƒ ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã¾ã™ã€‚ãƒã‚§ãƒƒã‚¯ã•ã‚Œã¦ãªã„ボックスをãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹ã¨ã„ã†<span class="emphasis"><em>å°ã‚’ã¤ã‘ã‚‹</em></span>ã“ã¨ã«ãªã‚Šã¾ã™ã€‚インストールã¯<span class="guibutton"><strong>é©ç”¨</strong></span>ボタンãŒã‚¯ãƒªãƒƒã‚¯ã•ã‚ŒãŸã¨ãã®ã¿å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚ã“ã®ã‚ˆã†ã«ã€å®Ÿéš›ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã®ãƒˆãƒ©ãƒ³ã‚¶ã‚¯ã‚·ãƒ§ãƒ³ã‚’実行ã™ã‚‹å‰ã«è¤‡æ•°ã®ãƒ‘ッケージã¾ãŸã¯ãƒ‘ッケージグループを検索ãŠã‚ˆã³é¸æŠžã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã•ã‚‰ã«ã€ãƒã‚§ãƒƒã‚¯ãƒœãƒƒã‚¯ã‚¹ã®ãƒã‚§ãƒƒã‚¯ã‚’解除ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸãƒ‘ッケージを削除ã§ãã¾ã™ã€‚ã¾ãŸã€å‰Šé™¤ã¯<span class="guibutton"><strong>é©ç”¨</strong></span>ãŒæŠ¼ã•ã‚ŒãŸã¨ãã«ã™ã¹ã¦ã
®ä¿ç•™ã«ãªã£ã¦ã„るインストールã¨ã¨ã‚‚ã«å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚ä¾å˜æ€§ã®è§£æ±º
+ <a id="idm40924320" class="indexterm"></a>
+ （これはインストールまたは削除される追加のパッケージを追加するかもしれません）、<span class="guibutton"><strong>適用</strong></span>を押した後に実行されます。その後、<span class="application"><strong>PackageKit</strong></span> はインストールまたは削除するそれらの追加のパッケージを一覧表示するウィンドウを表示して、進めるかどうかを確認します。
+ </div><div class="para">
+ <span class="application"><strong>htop</strong></span> ã‚’ãƒã‚§ãƒƒã‚¯ã—ã¦ã€<span class="guibutton"><strong>é©ç”¨</strong></span>ボタンをクリックã—ã¾ã™ã€‚スーパーユーザーã®ãƒ‘スワードを入力è¦æ±‚ã•ã‚Œã¾ã™ã€‚ãれを入力ã™ã‚‹ã¨ã€<span class="application"><strong>PackageKit</strong></span> 㯠<span class="application"><strong>htop</strong></span> をインストールã—ã¾ã™ã€‚<span class="application"><strong>PackageKit</strong></span> ã®ç´ 晴らã—ã„機能ã®ä¸€ã¤ã¯ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã«å¾“ã£ã¦ã€ã¨ãã©ãæ–°ã—ãインストールã•ã‚ŒãŸã‚¢ãƒ—リケーションã®ä¸€è¦§ã‚’表示ã—ã¦ã€ãれらを直ã¡ã«å®Ÿè¡Œã™ã‚‹ã‚ˆã†é¸æŠžã‚’æ案ã™ã‚‹ã“ã¨ã§ã™ã€‚代ã‚ã‚Šã«ã€<span class="guilabel"><strong>ソフトウェアã®è¿½åŠ /削除</strong></span>ウィンドウã«ãŠã„ã¦ã€ãƒ‘ッケージを検索ã—ã¦é¸æŠžã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚¢ãƒ—リケーションã®ã‚·ãƒ§ãƒ¼ãƒˆã‚«ãƒƒãƒˆãŒç½®ã‹ã‚Œã‚‹ GNOME ã
ƒ¡ãƒ‹ãƒ¥ãƒ¼ã®<span class="guilabel"><strong>å ´æ‰€</strong></span>を示ã™ã“ã¨ã‚’覚ãˆã¦ãŠã„ã¦ãã ã•ã„。ãã‚Œã¯ã‚¢ãƒ—リケーションを実行ã—ãŸã„ã¨ãã«å½¹ç«‹ã¡ã¾ã™ã€‚
+ </div><div class="para">
+ 一度インストールすると、シェルプロンプトにおいて次のように入力することにより、<code class="command">top</code> プロセスビューアーのカラフルかつ高度なバージョンである <code class="command">htop</code> を実行できます:
+ </div><pre class="screen"><code class="command">htop</code></pre><div class="para">
+ <span class="application"><strong>htop</strong></span> は素晴らしいですが、<code class="command">top</code> で十分であるため、アンインストールすることにします。<span class="guibutton"><strong>利用可能なもののみ</strong></span>フィルターを<span class="guimenu"><strong>フィルター</strong></span> → <span class="guimenuitem"><strong>インストール済み</strong></span> install it to <span class="guibutton"><strong>インズトール済のもののみ</strong></span>に忘れずに変更することにより、再び <span class="application"><strong>htop</strong></span> を検索して、チェック解除します。プログラムはそれ自身の依存するものを何もインストールしません。もしあれば、システムにインストールされた他のパッケージにそれが何も依存していなければ、自動的に同じように削除されます。
+ </div><div class="warning" id="warning-PackageKit-Removing_a_Package_Without_Removing_Packages_Depending_on_It"><div class="admonition_header"><h2>他のパッケージに依存するときにパッケージを削除する</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> がパッケージのインストール中および削除中に自動的に依存関係を解決しますが、それに依存するパッケージも削除することなくパッケージを削除することはできません。この種の操作は <span class="application"><strong>RPM</strong></span> によってのみ実行できますが、推奨されません。これにより、システムが潜在的に機能しない状態になったり、アプリケーションが誤動作やクラッシュを起こしたりする可能性があります。
+ </div></div></div><div class="figure" id="fig-Graphical_Package_Management-removing_a_package"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-remove.png" alt="PackageKit のソフトウェアの追加/削除を用いたパッケージの削除" /><div class="longdesc"><div class="para">
+ Removing the htop package with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>図5.8 PackageKit のソフトウェアの追加/削除を用いたパッケージの削除</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Finding_Packages_with_Filters.html"><strong>戻る</strong>5.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="sec-Installing_and_Removing_Package_Groups.html"><strong>次へ</strong>5.2.4. パッケージグループのインストールおよび削除</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Upgrading.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Upgrading.html
new file mode 100644
index 0000000..251a23c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Installing_and_Upgrading.html
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="s1-rpm-using.html" title="B.2. RPMの使用法" /><link rel="prev" href="s1-rpm-using.html" title="B.2. RPMの使用法" /><link rel="next" href="sec-Configuration_File_Changes.html" title="B.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-rpm-using.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" h
ref="sec-Configuration_File_Changes.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Installing_and_Upgrading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.2. インストールとアップグレード</h3></div></div></div><a id="idm27411056" class="indexterm"></a><a id="idm62301808" class="indexterm"></a><a id="idm62300368" class="indexterm"></a><a id="idm31679520" class="indexterm"></a><div class="para">
+ RPM packages typically have file names
+ <a id="idm36585232" class="indexterm"></a>
+ like <code class="filename">tree-1.5.3-2.fc17.x86_64.rpm</code>. The file name includes the package name (<code class="filename">tree</code>), version (<code class="filename">1.5.3</code>), release (<code class="filename">2</code>), operating system major version (<code class="filename">fc17</code>) and CPU architecture (<code class="filename">x86_64</code>).
+ </div><div class="para">
+ <code class="command">rpm</code> の <code class="option">-U</code> オプションを使用できます:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ upgrade an existing but older package on the system to a newer version, or
+ </div></li><li class="listitem"><div class="para">
+ install the package even if an older version is not already installed.
+ </div></li></ul></div><div class="para">
+ That is, <code class="command">rpm -U <em class="replaceable"><code><rpm_file></code></em> </code> is able to perform the function of either <span class="emphasis"><em>upgrading</em></span> or <span class="emphasis"><em>installing</em></span> as is appropriate for the package.
+ </div><div class="para">
+ Assuming the <code class="filename">tree-1.5.3-2.fc17.x86_64.rpm</code> package is in the current directory, log in as root and type the following command at a shell prompt to either upgrade or install the <span class="package">tree</span> package as determined by <code class="command">rpm</code>:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh tree-1.5.3-2.fc17.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">
+ 更新/インストールが成功すると、以下の出力が表示されます:
+ </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, historically standing for <span class="emphasis"><em>install</em></span>. Because the <code class="option">-U</code> option subsumes both install and upgrade functions, we recommend to use <code class="command">rpm -Uvh</code> with all packages <span class="emphasis"><em>except <span class="package">kernel</span> packages</em></span>.
+ </div><div class="para">
+ You should always use the <code class="option">-i</code> option to simply <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, refer to <a class="xref" href="ch-Manually_Upgrading_the_Kernel.html">21章<em>カーネルをアップグレードする</em></a>.
+ </div></div></div><div class="para">
+ パッケージの署名は、パッケージのインストールまたはアップグレード時に自動的にチェックされます。署名により、パッケージが認証機関によって署名されたことを確認できます。たとえば、署名の検証が失敗すると、次のようなエラーメッセージが表示されます。
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc17.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID
+d22e77f2</pre><div class="para">
+ ヘッダのみの新しい署名なら、次のようなエラーメッセージが表示されます。
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc17.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD,
+key ID d22e77f2</pre><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.5.2.2-4.fc17.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba</pre><div class="para">
+ Refer to <a class="xref" href="s1-check-rpm-sig.html">「パッケージの署名を確認する」</a> for more information on checking a package's signature.
+ </div><div class="section" id="s3-rpm-errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">B.2.2.1. すでにインストールされているパッケージ</h4></div></div></div><div class="para">
+ If a package of the same name and version is already installed
+ <a id="idm58997440" class="indexterm"></a>
+ <a id="idm68090880" class="indexterm"></a>
+ , the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ package tree-1.5.3-2.fc17.x86_64 is already installed</pre><div class="para">
+ However, if you want to install the package anyway, you can use the <code class="command">--replacepkgs</code> option, which tells RPM to ignore the error:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --replacepkgs tree-1.5.3-2.fc17.x86_64.rpm</code>
+</pre><div class="para">
+ このオプションは、RPM からインストールされた ファイルが削除された場合や、RPM からオリジナルの 設定ファイルをインストールしたい場合に便利です。
+ </div></div><div class="section" id="s3-rpm-conflicting-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">B.2.2.2. ファイルの競合</h4></div></div></div><a id="idm26448416" class="indexterm"></a><div class="para">
+ If you attempt to install a package that contains a file which has already been installed by another package
+ <a id="idm41117792" class="indexterm"></a>
+ <a id="idm41116352" class="indexterm"></a>
+ , the following is displayed:
+ </div><pre class="screen">Preparing... ##################################################
+ file /usr/bin/foobar from install of foo-1.0-1.fc17.x86_64 conflicts
+with file from package bar-3.1.1.fc17.x86_64</pre><div class="para">
+ To make RPM ignore this error, use the <code class="command">--replacefiles</code> option:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --replacefiles foo-1.0-1.fc17.x86_64.rpm</code>
+</pre></div><div class="section" id="s3-rpm-unresolved-dependency"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">B.2.2.3. 未解決の依存性</h4></div></div></div><a id="idm18289984" class="indexterm"></a><a id="idm18288544" class="indexterm"></a><div class="para">
+ RPM packages may sometimes depend on other packages
+ <a id="idm52917536" class="indexterm"></a>
+ <a id="idm52916096" class="indexterm"></a>
+ , which means that they require other packages to be installed to run properly. If you try to install a package which has an unresolved dependency, output similar to the following is displayed:
+ </div><pre class="screen">error: Failed dependencies:
+ bar.so.3()(64bit) is needed by foo-1.0-1.fc17.x86_64</pre><div class="para">
+ If you are installing a package from the Fedora installation media, such as from a CD-ROM or DVD, the dependencies may be available. Find the suggested package(s) on the Fedora installation media or on one of the active Fedora mirrors and add it to the command:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh foo-1.0-1.fc17.x86_64.rpm bar-3.1.1.fc17.x86_64.rpm</code>
+</pre><div class="para">
+ 両方のパッケージのインストールが正常に行なわれると、以下のような出力が表示されます。
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ 1:foo ########################################### [ 50%]
+ 2:bar ########################################### [100%]</pre><div class="para">
+ You can try the <code class="option">--whatprovides</code> option to determine which package contains the required file.
+ </div><pre class="screen">
+<code class="command">rpm -q --whatprovides "bar.so.3"</code>
+</pre><div class="para">
+ <code class="filename">bar.so.3</code> を含むパッケージが RPM データベースにあると、パッケージの名前が表示されます:
+ </div><pre class="screen">bar-3.1.1.fc17.i586.rpm</pre><div class="warning" id="warning-install-Warning-Forcing_Package_Installation"><div class="admonition_header"><h2>警告: 強制的なパッケージのインストール</h2></div><div class="admonition"><div class="para">
+ Although we can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to install a package that gives us a <code class="computeroutput">Failed dependencies</code> error (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 package failing to run. Installing or removing packages with <code class="command">rpm --nodeps</code> can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager—whether <span class="application"><strong>RPM</strong></span>, <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>—shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The <span class="application"><stron
g>Yum</strong></span> package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing <code class="command">rpm</code> to carry out actions without regard to resolving dependencies.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-using.html"><strong>戻る</strong>B.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="sec-Configuration_File_Changes.html"><strong>次へ</strong>B.2.3. 設定ファイルの変更</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Interacting_with_NetworkManager.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Interacting_with_NetworkManager.html
new file mode 100644
index 0000000..5352ae1
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Interacting_with_NetworkManager.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>6.2. Interacting with NetworkManager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-NetworkManager.html" title="第6章 NetworkManager" /><link rel="prev" href="ch-NetworkManager.html" title="第6章 NetworkManager" /><link rel="next" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="6.2.2. Configuring New and Editing Existing Connections" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-NetworkManager.html"><stro
ng>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Interacting_with_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Interacting with NetworkManager</h2></div></div></div><div class="para">
+ Users do not interact with the <span class="application"><strong>NetworkManager</strong></span> system service directly. Instead, you can perform network configuration tasks via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet. The applet has multiple states that serve as visual indicators for the type of connection you are currently using.
+ </div><div class="figure" id="exam-Interacting_with_NetworkManager"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-AppletStates_Gnome3"><img src="images/Network_Configuration-NM-AppletStates_Gnome3.png" alt="NetworkManager applet states" /><div class="longdesc"><div class="para">
+ A row of four icons representing NetworkManager applet states
+ </div></div></div></div><h6>図6.1 NetworkManager applet states</h6></div><br class="figure-break" /><div class="para">
+ If you do not see the <span class="application"><strong>NetworkManager</strong></span> applet in the GNOME panel, and assuming that the <span class="application"><strong>NetworkManager</strong></span> package is installed on your system, you can start the applet by running the following command as a normal user (not root):
+ </div><pre class="screen">~]$ <code class="command">nm-applet &</code>
+</pre><div class="para">
+ After running this command, the applet appears in your Notification Area.
+ </div><div class="section" id="sec-Connecting_to_a_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.1. Connecting to a Network</h3></div></div></div><div class="para">
+ When you click on the applet icon, you are presented with:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a list of categorized networks you are currently connected to (such as <span class="guilabel"><strong>Wired</strong></span> and <span class="guilabel"><strong>Wireless</strong></span>);
+ </div></li><li class="listitem"><div class="para">
+ a list of all <span class="guilabel"><strong>Available Networks</strong></span> that <span class="application"><strong>NetworkManager</strong></span> has detected;
+ </div></li><li class="listitem"><div class="para">
+ options for connecting to any configured Virtual Private Networks (VPNs); and,
+ </div></li><li class="listitem"><div class="para">
+ options for connecting to hidden or new wireless networks.
+ </div></li></ul></div><div class="para">
+ If you are connected to a network, its name is presented first under its network type, such as <span class="guilabel"><strong>Wired</strong></span> or <span class="guilabel"><strong>Wireless</strong></span> with a bulletpoint to the left. When many networks are available, such as wireless access points, the <span class="guilabel"><strong>More</strong></span> networks expandable menu entry appears.
+ </div><div class="figure" id="exam-Connecting_to_a_Network"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3"><img src="images/Network_Configuration_NM_CableUnpluged_WiFi_List_Gnome3.png" alt="The NetworkManager applet's drop-down menu, showing all available and connected-to networks" /><div class="longdesc"><div class="para">
+ A screen shot of the NetworkManager applet's drop-down menu, showing all available and connected-to networks
+ </div></div></div></div><h6>図6.2 The <span class="application">NetworkManager</span> applet's drop-down menu, showing all available and connected-to networks</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-NetworkManager.html"><strong>戻る</strong>第6章 NetworkManager</a></li><li class="up"><a accesskey="u" href="#"><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_New_and_Editing_Existing_Connections.html"><strong>次へ</strong>6.2.2. Configuring New and Editing Existing Conne...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Listing_Packages.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Listing_Packages.html
new file mode 100644
index 0000000..5ff3518
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Listing_Packages.html
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="4.2. パッケージとパッケージ グループ" /><link rel="prev" href="sec-Packages_and_Package_Groups.html" title="4.2. パッケージとパッケージ グループ" /><link rel="next" href="sec-Displaying_Package_Information.html" title="4.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="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">4.2.2. パッケージの一覧</h3></div></div></div><a id="idm35860912" class="indexterm"></a><a id="idm57835632" class="indexterm"></a><div class="para">
+ <code class="command">yum list</code> および関連するコマンドは、パッケージ、パッケージのグループおよびリポジトリーに関する情報を提供します。
+ </div><div class="para">
+ すべての Yum の list コマンドは引数として複数の<em class="firstterm">グロブ表現</em>を追加することにより結果をフィルターできます。グロブ表現は、ワイルドカード文字 <code class="command">*</code> (あらゆる文字に複数回マッチするよう展開されます) および <code class="command">?</code> (あらゆる文字に1回マッチするよう展開されます) を複数含む文字列です。
+ </div><div class="note" id="note-Tip-Filtering_Results_with_Glob_Expressions"><div class="admonition_header"><h2>glob 表記で結果のフィルタリング</h2></div><div class="admonition"><a id="idm72715360" class="indexterm"></a><a id="idm72713472" class="indexterm"></a><div class="para">
+ 引数を <code class="command">yum</code> コマンドに渡すとき、グロブ表現をエスケープすることに注意してください。そうでなければ、Bash シェルはこれらの表現を<em class="firstterm">パス名 拡張</em>として解釈します。潜在的にグロブに一致する現在のディレクトリにあるすべてのファイルを <code class="command">yum</code> に渡します。グロブ表現が意図したとおり <code class="command">yum</code> に渡されることを確実にするには、次のようにします:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ バックスラッシュを手前につけることによりワイルドカード文字を
+ </div></li><li class="listitem"><div class="para">
+ グロブ表現全体を二重引用符または引用符でくくります
+ </div></li></ul></div><div class="para">
+ これらの方法の使用例は<a class="xref" href="sec-Listing_Packages.html#ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions">例4.1「すべての ABRT アドオンとプラグインのグロブ表現を用いた一覧表示」</a>および<a class="xref" href="sec-Listing_Packages.html#ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards">例4.4「エスケープされたワイルドカード文字を用いた単一グロブ表現を使用した利用可能なパッケージの一覧表示」</a>を参照してください。
+ </div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">yum list <em class="replaceable"><code>glob_expression</code></em>…</code></span></dt><dd><div class="para">
+ 全 glob 表記に一致するインストール済みと利用できるパッケージ情報の一覧です。
+ </div><div class="example" id="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions"><h6>例4.1 すべての ABRT アドオンとプラグインのグロブ表現を用いた一覧表示</h6><div class="example-contents"><div class="para">
+ さまざまな ABRT アドオンとプラグインを持つパッケージは <span class="quote">「<span class="quote">abrt-addon-</span>」</span> または <span class="quote">「<span class="quote">abrt-plugin-</span>」</span> から始まります。これらのパッケージを一覧表示するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum list abrt-addon\* abrt-plugin\*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+abrt-addon-ccpp.x86_64 2.0.2-5.fc15 @fedora
+abrt-addon-kerneloops.x86_64 2.0.2-5.fc15 @fedora
+abrt-addon-python.x86_64 2.0.2-5.fc15 @fedora
+abrt-plugin-bugzilla.x86_64 2.0.2-5.fc15 @fedora
+abrt-plugin-logger.x86_64 2.0.2-5.fc15 @fedora
+Available Packages
+abrt-plugin-mailx.x86_64 2.0.2-5.fc15 updates
+abrt-plugin-reportuploader.x86_64 2.0.2-5.fc15 updates
+abrt-plugin-rhtsupport.x86_64 2.0.2-5.fc15 updates</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm30513008" class="indexterm"></a>
+ <a id="idm57513840" class="indexterm"></a>
+ <code class="command">yum list all</code></span></dt><dd><div class="para">
+ インストール済み<span class="emphasis"><em>かつ</em></span>利用可能なパッケージの一覧です。
+ </div><div class="example" id="ex-Listing_all_installed_and_available_packages"><h6>例4.2 インストール済みと利用できる全パッケージの一覧</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum list all</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+ConsoleKit.x86_64 0.4.4-1.fc15 @fedora
+ConsoleKit-libs.x86_64 0.4.4-1.fc15 @fedora
+ConsoleKit-x11.x86_64 0.4.4-1.fc15 @fedora
+GConf2.x86_64 2.32.3-1.fc15 @fedora
+GConf2-gtk.x86_64 2.32.3-1.fc15 @fedora
+ModemManager.x86_64 0.4-7.git20110201.fc15 @fedora
+NetworkManager.x86_64 1:0.8.998-4.git20110427.fc15 @fedora
+NetworkManager-glib.x86_64 1:0.8.998-4.git20110427.fc15 @fedora
+NetworkManager-gnome.x86_64 1:0.8.998-4.git20110427.fc15 @fedora
+NetworkManager-openconnect.x86_64 0.8.1-9.git20110419.fc15 @fedora
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm40329232" class="indexterm"></a>
+ <a id="idm40327344" class="indexterm"></a>
+ <code class="command">yum list installed</code></span></dt><dd><div class="para">
+ システムにインストールされているすべてのパッケージを一覧表示します。出力の一番右の列は、パッケージが取得されたリポジトリーを表示します。
+ </div><div class="example" id="ex-Listing_installed_packages_using_a_double-quoted_glob_expression"><h6>例4.3 二重引用符のグロブ表現を用いたインストール済みパッケージの一覧表示</h6><div class="example-contents"><div class="para">
+ 厳密に <span class="quote">「<span class="quote">krb</span>」</span> から始まり1文字以上の文字とハイフンが続く、インストール済みパッケージをすべて表示するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum list installed "krb?-*"</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Installed Packages
+krb5-libs.x86_64 1.9-7.fc15 @fedora</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm55907296" class="indexterm"></a>
+ <a id="idm51215776" class="indexterm"></a>
+ <code class="command">yum list available</code></span></dt><dd><div class="para">
+ 有効な全リポジトリーと利用できる全パッケージの一覧です。
+ </div><div class="example" id="ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards"><h6>例4.4 エスケープされたワイルドカード文字を用いた単一グロブ表現を使用した利用可能なパッケージの一覧表示</h6><div class="example-contents"><div class="para">
+ <span class="quote">「<span class="quote">gstreamer</span>」</span> とその後に <span class="quote">「<span class="quote">plugin</span>」</span> を含む名前を持つ利用可能なパッケージをすべて表示するには、以下のコマンドを実行します:
+ </div><pre class="screen">~]# <code class="command">yum list available gstreamer\*plugin\*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Available Packages
+gstreamer-plugin-crystalhd.x86_64 3.5.1-1.fc14 fedora
+gstreamer-plugins-bad-free.x86_64 0.10.22-1.fc15 updates
+gstreamer-plugins-bad-free-devel.x86_64 0.10.22-1.fc15 updates
+gstreamer-plugins-bad-free-devel-docs.x86_64 0.10.22-1.fc15 updates
+gstreamer-plugins-bad-free-extras.x86_64 0.10.22-1.fc15 updates
+gstreamer-plugins-base.x86_64 0.10.33-1.fc15 updates
+gstreamer-plugins-base-devel.x86_64 0.10.33-1.fc15 updates
+gstreamer-plugins-base-devel-docs.noarch 0.10.33-1.fc15 updates
+gstreamer-plugins-base-tools.x86_64 0.10.33-1.fc15 updates
+gstreamer-plugins-espeak.x86_64 0.3.3-3.fc15 fedora
+gstreamer-plugins-fc.x86_64 0.2-2.fc15 fedora
+gstreamer-plugins-good.x86_64 0.10.29-1.fc15 updates
+gstreamer-plugins-good-devel-docs.noarch 0.10.29-1.fc15 updates</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm48107936" class="indexterm"></a>
+ <a id="idm48106048" class="indexterm"></a>
+ <code class="command">yum grouplist</code></span></dt><dd><div class="para">
+ 全パッケージ グループの一覧です。
+ </div><div class="example" id="ex-Listing_all_package_groups"><h6>例4.5 全パッケージ グループの一覧</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum grouplist</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">[出力の省略]</span></em></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm73216768" class="indexterm"></a>
+ <a id="idm70317264" class="indexterm"></a>
+ <code class="command">yum repolist</code></span></dt><dd><div class="para">
+ <span class="emphasis"><em>有効な</em></span> 各リポジトリーに対してリポジトリー ID、名前、および提供されるパッケージ数を一覧表示します。
+ </div><div class="example" id="ex-Listing_enabled_repositories"><h6>例4.6 有効なリポジトリーの一覧表示</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum repolist</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+repo id repo name status
+fedora Fedora 15 - i386 19,365
+updates Fedora 15 - i386 - Updates 3,848
+repolist: 23,213</pre></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>4.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-Displaying_Package_Information.html"><strong>次へ</strong>4.2.3. パッケージ情報の表示</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Loading_a_Module.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Loading_a_Module.html
new file mode 100644
index 0000000..1021c20
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Loading_a_Module.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="第22章 Working with Kernel Modules" /><link rel="prev" href="sec-Displaying_Information_About_a_Module.html" title="22.2. Displaying Information About a Module" /><link rel="next" href="sec-Unloading_a_Module.html" title="22.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">22.3. モジュールの読み込み方法</h2></div></div></div><a id="idm60260032" class="indexterm"></a><a id="idm60258112" class="indexterm"></a><a id="idm61146560" 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="idm55921728" 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 may include loading module dependencies.
+ </div><div class="example" id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>例22.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/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_tgt.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/libfc/libfc.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</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 <span class="quote">「<span class="quote">primitive</span>」</span> <code class="command">insmod</code> command to insert the modules into the running kernel.
+ </div></div></div><br class="example-break" /><a id="idm50174464" class="indexterm"></a><a id="idm52064832" 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>22.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>22.4. Unloading a Module</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Managing_Yum_Repositories.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Managing_Yum_Repositories.html
new file mode 100644
index 0000000..970f344
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Managing_Yum_Repositories.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>4.3.5. Yum リポジトリの追加・有効化および無効化</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="4.3. Yum と Yum リポジトリーの設定" /><link rel="prev" href="sec-Viewing_the_Current_Configuration.html" title="4.3.4. 現在の設定の表示" /><link rel="next" href="sec-Creating_a_Yum_Repository.html" title="4.3.6. Yum リポジトリーの作成" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.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="sec-Viewing_the_Current_Configuration.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Yum_Repository.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Managing_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.5. Yum リポジトリの追加・有効化および無効化</h3></div></div></div><a id="idm20035600" class="indexterm"></a><div class="para">
+ <a class="xref" href="sec-Setting_repository_Options.html">「[repository] オプションの設定」</a>は Yum リポジトリを定義するために使用できるさまざまなオプションを説明しています。このセクションは <code class="command">yum-config-manager</code> コマンドを使用することによりリポジトリを追加、有効化、および無効化する方法について説明しています。
+ </div><h4 id="bh-Managing_Yum_Repositories-Adding">Yum リポジトリの追加</h4><div class="para">
+ 新しいリポジトリを定義するには、<code class="filename">/etc/yum.conf</code> ファイルに <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションを追加するか、<code class="filename">/etc/yum.repos.d/</code> ディレクトリに <code class="filename">.repo</code> ファイルを追加します。このディレクトリにある <code class="filename">.repo</code> ファイル拡張子を持つすべてのファイルは <code class="command">yum</code> により読み込まれます。<code class="filename">/etc/yum.conf</code> にリポジトリを定義する代わりに、ここに定義することが最も良いです。
+ </div><div class="warning"><div class="admonition_header"><h2>信頼できないソフトウェア提供元を使用するとき注意してください</h2></div><div class="admonition"><div class="para">
+ 検証されていない、もしくは信頼されていないソフトウェア提供元からソフトウェアを取得またはインストールすることは、潜在的なセキュリティリスクになります、または、セキュリティ、安定性、互換性およびメンテナンス性の問題を引き起こす可能性があります。
+ </div></div></div><div class="para">
+ Yum リポジトリは一般的に自身の <code class="filename">.repo</code> ファイルを提供します。そのようなリポジトリをシステムに追加して有効にするには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--add-repo</code> <em class="replaceable"><code>repository_url</code></em></pre><div class="para">
+ …ここで <em class="replaceable"><code>repository_url</code></em> は <code class="filename">.repo</code> ファイルへのリンクです。たとえば、http://www.example.com/example.repo にあるリポジトリを追加するには、シェルプロンプトにおいて以下のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">yum-config-manager --add-repo http://www.example.com/example.repo</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+adding repo from: http://www.example.com/example.repo
+grabbing file http://www.example.com/example.repo to /etc/yum.repos.d/example.repo
+example.repo | 413 B 00:00
+repo saved to /etc/yum.repos.d/example.repo</pre><h4 id="bh-Managing_Yum_Repositories-Enabling">Yum リポジトリーの有効化</h4><div class="para">
+ 特定のリポジトリーを有効にするには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--enable</code> <em class="replaceable"><code>repository</code></em>…</pre><div class="para">
+ …ここで <em class="replaceable"><code>repository</code></em> は一意なリポジトリ ID です（利用可能なリポジトリ ID を一覧表示するには <code class="command">yum repolist all</code> を使用します）。代わりに、すべての一致するリポジトリを有効にするためにグロブ表現を使用できます。
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--enable</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、<code class="literal">[example]</code>, <code class="literal">[example-debuginfo]</code>, および <code class="literal">[example-source]</code> セクションに定義されたリポジトリーを無効にするには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum-config-manager --enable example\*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+============================== repo: example ==============================
+[example]
+bandwidth = 0
+base_persistdir = /var/lib/yum/repos/x86_64/6Server
+baseurl = http://www.example.com/repo/6Server/x86_64/
+cache = 0
+cachedir = /var/cache/yum/x86_64/6Server/example
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre><div class="para">
+ 成功したとき、<code class="command">yum-config-manager --enable</code> コマンドが現在のリポジトリ設定を表示します。
+ </div><h4 id="bh-Managing_Yum_Repositories-Disabling">Yum リポジトリの無効化</h4><div class="para">
+ Yum リポジトリを無効にするには、<code class="systemitem">root</code>として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--disable</code> <em class="replaceable"><code>repository</code></em>…</pre><div class="para">
+ …ここで <em class="replaceable"><code>repository</code></em> は一意なリポジトリ ID です（利用可能なリポジトリ ID を一覧表示するには <code class="command">yum repolist all</code> を使用します）。<code class="command">yum-config-manager --enable</code> と同様に、すべての一致するリポジトリを同時に無効にするためにグロブ表現を使用できます。
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--disable</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ 成功したとき、<code class="command">yum-config-manager --disable</code> コマンドが現在のリポジトリ設定を表示します。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Viewing_the_Current_Configuration.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="sec-Creating_a_Yum_Repository.html"><strong>次へ</strong>4.3.6. Yum リポジトリーの作成</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-NetworkManager_Architecture.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-NetworkManager_Architecture.html
new file mode 100644
index 0000000..1bf9595
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-NetworkManager_Architecture.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>6.5. NetworkManager Architecture</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-NetworkManager.html" title="第6章 NetworkManager" /><link rel="prev" href="sec-Configuring_IPv6_Settings.html" title="6.4.5. Configuring IPv6 Settings" /><link rel="next" href="ch-Network_Interfaces.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-Configuring_IPv6_Settings.html"><str
ong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ch-Network_Interfaces.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-NetworkManager_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.5. NetworkManager Architecture</h2></div></div></div><div class="para">
+ See <a href="http://live.gnome.org/NetworkManagerConfiguration">http://live.gnome.org/NetworkManagerConfiguration</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_IPv6_Settings.html"><strong>戻る</strong>6.4.5. Configuring IPv6 Settings</a></li><li class="up"><a accesskey="u" href="#"><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-Network_Interfaces.html"><strong>次へ</strong>第7章 ネットワーク・インターフェース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-PackageKit_Architecture.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-PackageKit_Architecture.html
new file mode 100644
index 0000000..3b43f26
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-PackageKit_Architecture.html
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. PackageKit アーキテクチャー</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-PackageKit.html" title="第5章 PackageKit" /><link rel="prev" href="sec-Viewing_the_Transaction_Log.html" title="5.2.5. トランザクションログの表示" /><link rel="next" href="ch-Graphical_Package_Management-sec-Additional_Resources.html" title="5.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-Viewing_the_Trans
action_Log.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-PackageKit_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.3. PackageKit アーキテクチャー</h2></div></div></div><a id="idm43607312" class="indexterm"></a><div class="para">
+ Fedora は、システムと互換性のあるパッケージおよびパッケージグループを表示、更新、インストールおよびアンインストールするためのアプリケーションである <span class="application"><strong>PackageKit</strong></span> スイートを提供します。アーキテクチャーとして、<span class="application"><strong>PackageKit</strong></span> は <code class="command">packagekitd</code> デーモンのバックエンドと通信するグラフィカルなフロントエンドいくつかから構成されます。これは、いパッケージのインストールや削除などのような、実際のトランザクションを実行するために <span class="application"><strong>Yum</strong></span> を利用する、パッケージマネージャー固有のバックエンドと通信します。
+ </div><div class="para">
+ <a class="xref" href="sec-PackageKit_Architecture.html#table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands">表5.1「PackageKit GUI ウィンドウ、メニュー位置、およびシェルプロンプトコマンド」</a>は、GUI ウィンドウの名前、GNOME デスクトップまたは<span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>ウィンドウからウィンドウを起動する方法、およびウィンドウを開くコマンドラインアプリケーションの名前を示しています。
+ </div><div class="table" id="table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands"><h6>表5.1 PackageKit GUI ウィンドウ、メニュー位置、およびシェルプロンプトコマンド</h6><div class="table-contents"><table summary="PackageKit GUI ウィンドウ、メニュー位置、およびシェルプロンプトコマンド" border="1"><colgroup><col align="left" class="col1" width="25%" /><col align="left" class="col2" width="25%" /><col align="left" class="col3" width="25%" /><col align="left" class="col4" width="25%" /></colgroup><thead><tr><th class="" align="left">
+ ウィンドウタイトル
+ </th><th class="" align="left">
+ 機能
+ </th><th class="" align="left">
+ 開き方
+ </th><th class="" align="left">
+ シェルコマンド
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ ソフトウェアの追加/削除
+ </td><td class="" align="left">
+ パッケージ情報のインストール、削除、または表示
+ </td><td class="" align="left">
+ <div class="para">
+ GNOME パネルから: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>管理</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの追加/削除</strong></span>
+ </div>
+
+ </td><td class="" align="left">
+ gpk-application
+ </td></tr><tr><td class="" align="left">
+ ソフトウェアの更新
+ </td><td class="" align="left">
+ パッケージの更新の実行
+ </td><td class="" align="left">
+ <div class="para">
+ GNOME パネルから: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>管理</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの更新</strong></span>
+ </div>
+
+ </td><td class="" align="left">
+ gpk-update-viewer
+ </td></tr><tr><td class="" align="left">
+ ソフトウェア提供元
+ </td><td class="" align="left">
+ <span class="application"><strong>Yum</strong></span> リポジトリーの有効化および無効化
+ </td><td class="" align="left">
+ <div class="para">
+ <span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>から: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアリポジトリ</strong></span>
+ </div>
+
+ </td><td class="" align="left">
+ gpk-repo
+ </td></tr><tr><td class="" align="left">
+ ソフトウェア更新履歴ビューアー
+ </td><td class="" align="left">
+ トランザクションログの表示
+ </td><td class="" align="left">
+ <div class="para">
+ <span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>から: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアログ</strong></span>
+ </div>
+
+ </td><td class="" align="left">
+ gpk-log
+ </td></tr><tr><td class="" align="left">
+ ソフトウェアの更新の設定
+ </td><td class="" align="left">
+ <span class="application"><strong>PackageKit</strong></span> の設定
+ </td><td class="" align="left">
+ </td><td class="" align="left">
+ gpk-prefs
+ </td></tr><tr><td class="" align="left">
+ (通知エリアの警告)
+ </td><td class="" align="left">
+ 更新が利用可能なときに警告する
+ </td><td class="" align="left">
+ <div class="para">
+ GNOME パネルから: <span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>設定</strong></span> → <span class="guimenuitem"><strong>スタートアップアプリケーション</strong></span>, <span class="guilabel"><strong>スタートアッププログラム</strong></span> タブ
+ </div>
+
+ </td><td class="" align="left">
+ gpk-update-icon
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ <code class="command">packagekitd</code> デーモンは、ユーザーセッションの外で実行され、さまざまなグラフィカルフロントウィンドウと通信します。<code class="command">packagekitd</code> デーモン<a href="#ftn.footnote-Daemons" class="footnote"><sup class="footnote" id="footnote-Daemons">[1]</sup></a> <span class="application"><strong>DBus</strong></span> システムメッセージバス経由で他のバックエンドを通信します。これは、システムに問い合わせを実行したり、変更を加えるために <span class="application"><strong>Yum</strong></span> の Python API を利用します。Red Hat Enterprise Linux と Fedora 以外の Linux システムにおいて、<code class="command">packagekitd</code> は、そのシステム固有のパッケージマネージャーを使用できる他のバックエンドと通信できます。このモジュール型アーキテクチャーは、同じ
種類のパッケージ管理タスクを基本的に実行できるよう、多くの異なるパッケージマネージャーとともに機能するために必要なグラフィカルインターフェースの抽象化を提供します。<span class="application"><strong>PackageKit</strong></span> フロントエンドをどのように使用するかを学ぶことは、<span class="application"><strong>Yum</strong></span> 以外のディストリビューション固有のパッケージマネージャーを利用するときさえ、多くの異なる Linux ディストリビューションにわたり同じようなグラフィカルインターフェースを使用できることを意味します。
+ </div><div class="para">
+ さらに、<span class="application"><strong>PackageKit</strong></span> の関心の分離により、GUI ウィンドウ—またはユーザーの X Window セッション—のどれかのクラッシュに信頼性を与えます。これは、ユーザーセッションの外側で実行する <code class="command">packagekitd</code> デーモンにより管理されるあらゆるパッケージ管理タスクに影響しません。
+ </div><div class="para">
+ 本章で説明されるフロントエンドのグラフィカルアプリケーションはすべて <span class="application"><strong>PackageKit</strong></span> とその依存パッケージの代わりに <code class="filename">gnome-packagekit</code> パッケージにより提供されます。KDE 環境を利用しているユーザーは、<span class="application"><strong>PackageKit</strong></span> の KDE インターフェースを提供する <code class="filename">kpackagekit</code> パッケージをインストールしたいかもしれません。
+ </div><div class="para">
+ 最後に、<span class="application"><strong>PackageKit</strong></span> は <code class="command">pkcon</code> というコンソールベースのフロントエンドからも利用できます。
+ </div><div class="footnotes"><br /><hr /><div id="footnote-Daemons" class="footnote"><div class="para"><a href="#footnote-Daemons" class="para"><sup class="para">[1] </sup></a>
+ システムデーモンは一般的に、ユーザーや他のプログラムにサービスを提供し、しばしば起動時に開始される、長時間実行されるプロセスです。デーモンは <code class="command">systemctl</code> コマンドに応答し、<code class="command">systemctl enable</code> または <code class="command">systemctl disable</code> コマンドを使用することにより永続的に無効化または有効化できます。一般的に <code class="command">packagekitd</code> デーモンのように <span class="quote">「<span class="quote"><span class="emphasis"><em>d</em></span></span>」</span> を付け加えることにより認識できます。システムサービスに関する詳細は<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Viewing_the_Transaction_Log.html"><strong>戻る</strong>5.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="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>次へ</strong>5.4. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html
new file mode 100644
index 0000000..8ffeb78
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>4.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-yum.html" title="第4章 Yum" /><link rel="prev" href="ch-yum.html" title="第4章 Yum" /><link rel="next" href="sec-Listing_Packages.html" title="4.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-yum.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Listing_Packages.html"><strong>次へ</s
trong></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">4.2. パッケージとパッケージ グループ</h2></div></div></div><a id="idm54060224" class="indexterm"></a><a id="idm58633744" class="indexterm"></a><div class="section" id="sec-Searching_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.1. パッケージの検索</h3></div></div></div><a id="idm58631312" class="indexterm"></a><a id="idm58629424" class="indexterm"></a><div class="para">
+ 次のコマンドですべての <acronym class="acronym">RPM</acronym> パッケージ名や説明、要約で検索できます。
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">search</code> <em class="replaceable"><code>term</code></em>…</pre><div class="para">
+ このコマンドは各項目に一致するものの一覧を表示します。たとえば、<span class="quote">「<span class="quote">meld</span>」</span> または <span class="quote">「<span class="quote">kompare</span>」</span> に一致するすべてのパッケージを一覧表示するには、次のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum 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="idm42532896" class="indexterm"></a><a id="idm35865072" class="indexterm"></a><div class="para">
+ <code class="command">yum search</code> コマンドは、名前はよくわからないが、関連する語句を知っているパッケージを検索するために有用です。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-yum.html"><strong>戻る</strong>第4章 Yum</a></li><li class="up"><a accesskey="u" href="#"><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>4.2.2. パッケージの一覧</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html
new file mode 100644
index 0000000..ea8c910
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Persistent_Module_Loading.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>22.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="第22章 Working with Kernel Modules" /><link rel="prev" href="sec-Setting_Module_Parameters.html" title="22.5. Setting Module Parameters" /><link rel="next" href="sec-Specific_Kernel_Module_Capabilities.html" title="22.7. Specific Kernel Module Capabilities" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Sett
ing_Module_Parameters.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Specific_Kernel_Module_Capabilities.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">22.6. Persistent Module Loading</h2></div></div></div><a id="idm62864864" class="indexterm"></a><a id="idm68453280" 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">例22.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 creating a new <code class="filename"><em class="replaceable"><code>file_name</code></em>.modules</code> file in the <code class="filename">/etc/sysconfig/modules/</code> directory, where <em class="replaceable"><code>file_name</code></em> is any descriptive name of your choice. Your <code class="filename"><em class="replaceable"><code>file_name</code></em>.modules</code> files are treated by the system startup scripts as shell scripts, and as such should begin with an <em class="firstterm">interpreter directive</em> (also called a <span class="quote">「<span class="quote">bang line</span>」</span>) as their first line:
+ </div><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span></pre><div class="para">
+ Additionally, the <code class="filename"><em class="replaceable"><code>file_name</code></em>.modules</code> file should be executable. You can make it executable by running:
+ </div><pre class="screen">modules]# <code class="command">chmod +x <em class="replaceable"><code>file_name</code></em>.modules</code>
+</pre><div class="example" id="ex-bluez-uinput.modules"><h6>例22.5 /etc/sysconfig/modules/bluez-uinput.modules</h6><div class="example-contents"><div class="para">
+ The following <code class="filename">bluez-uinput.modules</code> script loads the <code class="systemitem">uinput</code> module:
+ </div><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+<span class="perl_Keyword">if</span><span class="perl_Reserved"> [</span> ! -c /dev/input/uinput<span class="perl_Reserved"> ]</span> ; <span class="perl_Keyword">then</span>
+ <span class="perl_Reserved">exec</span> /sbin/modprobe uinput <span class="perl_Operator">></span>/dev/null <span class="perl_Operator">2>&1</span>
+<span class="perl_Keyword">fi</span></pre><div class="para">
+ The <code class="literal">if</code>-conditional statement on the third line ensures that the <code class="filename">/dev/input/uinput</code> file does <span class="emphasis"><em>not</em></span> already exist (the <code class="literal">!</code> symbol negates the condition), and, if that is the case, loads the <code class="systemitem">uinput</code> module by calling <code class="command">exec /sbin/modprobe uinput</code>. Note that the <code class="systemitem">uinput</code> module creates the <code class="filename">/dev/input/uinput</code> file, so testing to see if that file exists serves as verification of whether the <code class="systemitem">uinput</code> module is loaded into the kernel.
+ </div><div class="para">
+ The following <code class="command">>/dev/null 2>&1</code> clause at the end of that line redirects any output to <code class="filename">/dev/null</code> so that the <code class="command">modprobe</code> command remains quiet.
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_Module_Parameters.html"><strong>戻る</strong>22.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="sec-Specific_Kernel_Module_Capabilities.html"><strong>次へ</strong>22.7. Specific Kernel Module Capabilities</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Plugin_Descriptions.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Plugin_Descriptions.html
new file mode 100644
index 0000000..cf17b65
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Plugin_Descriptions.html
@@ -0,0 +1,150 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Yum_Plugins.html" title="4.4. Yum プラグイン" /><link rel="prev" href="sec-Installing_More_Yum_Plugins.html" title="4.4.2. 追加の Yum プラグインのインストール" /><link rel="next" href="sec-Additional_Resources.html" title="4.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="sec-Installing_More_Yum_Plugins.ht
ml"><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-Plugin_Descriptions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.4.3. プラグインの説明</h3></div></div></div><div class="para">
+ 以下の一覧は有用な Yum プラグインのいくつかを説明しています:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">
+ <a id="idm53897600" class="indexterm"></a>
+ <span class="application"><strong>fs-snapshot</strong></span> (<span class="package">yum-plugin-fs-snapshot</span>)</span></dt><dd><div class="para">
+ <span class="application"><strong>fs-snapshot</strong></span> プラグインは、システムの更新やパッケージの削除のようなトランザクションを進める前にファイルシステムのスナップショットを作成するよう Yum を拡張します。トランザクションにより行われた変更が期待しないものとユーザーが思えば、このメカニズムによりユーザーがスナップショットに保存されている変更をロールバックできるようになります。
+ </div><div class="para">
+ プラグインが機能するためには、ルートファイルシステム（つまり、<code class="filename">/</code>）が <code class="systemitem">LVM</code> (Logical Volume Manager) または <code class="systemitem">Btrfs</code> ボリューム上になければいけません。LVM ボリュームにおいて <span class="application"><strong>fs-snapshot</strong></span> プラグインを使用するには、以下の手順に従います:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ ルートファイルシステムを持つボリュームグループが十分な空きエクステントを持つことを確実にします。必要な容量は、スナップショットのライフサイクルにおいて予想される、元の論理ボリュームへの変更量によります。適切なデフォルトは元の論理ボリューム容量の 50–80 % です。
+ </div><div class="para">
+ 特定のボリュームグループに関する詳細な情報を表示するには、<code class="systemitem">root</code> として以下の形式で <code class="command">vgdisplay</code> コマンドを実行します:
+ </div><pre class="synopsis"><code class="command">vgdisplay</code> <em class="replaceable"><code>volume_group</code></em></pre><div class="para">
+ フリーなエクステント数は <code class="literal">Free PE / Size</code> 行に一覧表示されます。
+ </div></li><li class="step"><div class="para">
+ ルートファイルシステムを持つボリュームグループが十分な空きエクステントを持たなければ、新しい物理ボリュームを追加します:
+ </div><ol class="a"><li class="step"><div class="para">
+ 論理ボリュームマネージャーを用いた物理ボリュームを初期化するには、<code class="systemitem">root</code> として、以下の形式で <code class="command">pvcreate</code> コマンドを実行します。
+ </div><pre class="synopsis"><code class="command">pvcreate</code> <em class="replaceable"><code>device</code></em></pre></li><li class="step"><div class="para">
+ 物理ボリュームをボリュームグループに追加するには、<code class="systemitem">root</code> として以下の形式で <code class="command">vgextend</code> コマンドを使用します:
+ </div><pre class="synopsis"><code class="command">vgextend</code> <em class="replaceable"><code>volume_group</code></em> <em class="replaceable"><code>physical_volume</code></em></pre></li></ol></li><li class="step"><div class="para">
+ <code class="filename">/etc/yum/pluginconf.d/fs-snapshot.conf</code> に置かれている設定ファイルを編集します。そして、以下の変更を <code class="literal">[lvm]</code> セクションに行います:
+ </div><ol class="a"><li class="step"><div class="para">
+ <code class="option">enabled</code> オプションの値を <code class="literal">1</code> に変更します:
+ </div><pre class="programlisting">enabled = 1</pre></li><li class="step"><div class="para">
+ <code class="option">lvcreate_size_args</code> 行の先頭からハッシュ記号（つまり、<code class="literal">#</code>）を削除し、論理エクステントの数をスナップショットのために割り当てるよう調整します。たとえば、元の論理ボリュームの容量の 80 % を割り当てるには、以下を使用します:
+ </div><pre class="programlisting">lvcreate_size_args = -l 80%ORIGIN</pre></li></ol><div class="para">
+ 利用可能な設定オプションの完全な一覧は<a class="xref" href="sec-Plugin_Descriptions.html#tabl-Yum-Plugin_Descriptions-fs-snapshot">表4.3「サポートされる <code class="filename">fs-snapshot.conf</code> ディレクティブ」</a>を参照してください。
+ </div></li><li class="step"><div class="para">
+ 希望する <code class="command">yum</code> コマンドを実行し、変更を確認してトランザクションを進める前に、<span class="application"><strong>fs-snapshot</strong></span> が読み込んだプラグイン（<code class="literal">Loaded plugins</code> 行）の一覧に含まれることを確実にします。<span class="application"><strong>fs-snapshot</strong></span> プラグインは、それぞれの影響する論理ボリュームに対して以下の形式で行を表示します:
+ </div><pre class="synopsis">fs-snapshot: snapshotting <em class="replaceable"><code>file_system</code></em> (/dev/<em class="replaceable"><code>volume_group</code></em>/<em class="replaceable"><code>logical_volume</code></em>): <em class="replaceable"><code>logical_volume</code></em>_yum_<em class="replaceable"><code>timestamp</code></em></pre></li><li class="step"><div class="para">
+ システムが期待するとおりに動作していることを確認します:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ 変更を保持することを決めたならば、<code class="systemitem">root</code> として <code class="command">lvremove</code> コマンドを実行することにより、スナップショットを削除します:
+ </div><pre class="synopsis"><code class="command">lvremove</code> /dev/<em class="replaceable"><code>volume_group</code></em>/<em class="replaceable"><code>logical_volume</code></em>_yum_<em class="replaceable"><code>timestamp</code></em></pre></li>
+ <li class="step"><div class="para">
+ 変更を元に戻して、スナップショットに保存された状態にファイルシステムを復元することを決めたならば、以下の手順をとります:
+ </div><ol class="a"><li class="step"><div class="para">
+ スナップショットを元々の論理ボリュームに統合するには、<code class="systemitem">root</code> として、以下の形式でコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">lvconvert</code> <code class="option">--merge</code> /dev/<em class="replaceable"><code>volume_group</code></em>/<em class="replaceable"><code>logical_volume</code></em>_yum_<em class="replaceable"><code>timestamp</code></em></pre><div class="para">
+ <code class="command">lvconvert</code> コマンドは変更を反映するために必要となる再起動を促します。
+ </div></li><li class="step"><div class="para">
+ 指示されたとおりシステムを再起動します。シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力することに実行することもできます:
+ </div><pre class="synopsis"><code class="command">reboot</code></pre></li></ol></li>
+
+ </ul></li></ol></div><div class="para">
+ Btrfs ファイルシステムにおいて <span class="application"><strong>fs-snapshot</strong></span> を使用するには、以下の手順を実行します:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ 希望する <code class="command">yum</code> コマンドを実行し、変更を確認してトランザクションを進める前に、<span class="application"><strong>fs-snapshot</strong></span> が読み込んだプラグイン（<code class="literal">Loaded plugins</code> 行）の一覧に含まれることを確実にします。<span class="application"><strong>fs-snapshot</strong></span> プラグインは、それぞれの影響するファイルシステムに対して以下の形式で行を表示します:
+ </div><pre class="synopsis">fs-snapshot: snapshotting <em class="replaceable"><code>file_system</code></em>: <em class="replaceable"><code>file_system</code></em>/yum_<em class="replaceable"><code>timestamp</code></em></pre></li><li class="step"><div class="para">
+ システムが期待するとおりに動作していることを確認します:
+ </div><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ 変更を保持することを決めたならば、オプションで期待しないスナップショットを削除できます。Btrfs スナップショットを削除するには、<code class="systemitem">root</code> として以下の形式でコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">btrfs</code> <code class="option">subvolume</code> <code class="option">delete</code> <em class="replaceable"><code>file_system</code></em>/yum_<em class="replaceable"><code>timestamp</code></em></pre></li>
+ <li class="step"><div class="para">
+ 変更を元に戻して、スナップショットに保存されている状態にファイルシステムを戻すことを決めたならば、以下の手順をとります:
+ </div><ol class="a"><li class="step"><div class="para">
+ <code class="systemitem">root</code> として以下のコマンドを使用することにより特定のスナップショットの識別子を確認できます:
+ </div><pre class="synopsis"><code class="command">btrfs</code> <code class="option">subvolume</code> <code class="option">list</code> <em class="replaceable"><code>file_system</code></em></pre></li><li class="step"><div class="para">
+ <code class="systemitem">root</code> として、このスナップショットをデフォルトでマウントするようシステムを設定します:
+ </div><pre class="synopsis"><code class="command">btrfs</code> <code class="option">subvolume</code> <code class="option">set-default</code> <em class="replaceable"><code>id</code></em> <em class="replaceable"><code>file_system</code></em></pre></li><li class="step"><div class="para">
+ システムを再起動します。シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力することにより実行できます:
+ </div><pre class="synopsis"><code class="command">reboot</code></pre></li></ol></li>
+
+ </ul></li></ol></div><div class="para">
+ 論理ボリューム管理、Btrfs、およびファイルシステムスナップショットの詳細は <a href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/"><em class="citetitle">Fedora 17 Storage Administration Guide</em></a> を参照してください。プラグインとその設定に関する詳細は、<span class="bold bold"><strong>yum-fs-snapshot</strong></span>(1) および <span class="bold bold"><strong>yum-fs-snapshot.conf</strong></span>(5) のマニュアルページを参照してください。
+ </div><div class="table" id="tabl-Yum-Plugin_Descriptions-fs-snapshot"><h6>表4.3 サポートされる <code class="filename">fs-snapshot.conf</code> ディレクティブ</h6><div class="table-contents"><table summary="サポートされる fs-snapshot.conf ディレクティブ" border="1"><colgroup><col width="15%" class="section" /><col width="35%" class="directive" /><col width="50%" class="description" /></colgroup><thead><tr><th class="">
+ セクション
+ </th><th class="">
+ ｄ
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="" rowspan="2" valign="middle">
+ <code class="literal">[main]</code>
+ </td><td class="">
+ <code class="option">enabled</code>=<em class="replaceable"><code>value</code></em>
+ </td><td class="">
+ プラグインの有効化または無効化をできます。<em class="replaceable"><code>value</code></em> は <code class="literal">1</code> (有効) または <code class="literal">0</code> (無効) でなければいけません。インストールされるとき、プラグインはデフォルトで有効になっています。
+ </td></tr><tr><td class="">
+ <code class="option">exclude</code>=<em class="replaceable"><code>list</code></em>
+ </td><td class="">
+ 特定のファイルシステムを除外できます。値はスナップショットを<span class="emphasis"><em>したくない</em></span>マウントポイント（たとえば、<code class="literal">/srv /mnt/backup</code>）のスペース区切りの <em class="replaceable"><code>list</code></em> でなければいけません。このオプションはデフォルトにより設定ファイルに含まれません。
+ </td></tr><tr><td class="" rowspan="2" valign="middle">
+ <code class="literal">[lvm]</code>
+ </td><td class="">
+ <code class="option">enabled</code>=<em class="replaceable"><code>value</code></em>
+ </td><td class="">
+ LVM ボリュームにおいてプラグインの使用を有効化または無効化できます。<em class="replaceable"><code>value</code></em> は <code class="literal">1</code> (有効) または <code class="literal">0</code> (無効) のどちらかでなければいけません。このオプションはデフォルトで無効にされています。
+ </td></tr><tr><td class="">
+ <code class="option">lvcreate_size_args</code>=<em class="replaceable"><code>value</code></em>
+ </td><td class="">
+ 論理ボリュームのスナップショットの容量を指定できます。\n<em class="replaceable"><code>value</code></em> は有効な引数が続けられる <span class="application"><strong>lvcreate</strong></span> ユーティリティに対する <code class="option">-l</code> または <code class="option">-L</code> コマンドラインオプション（たとえば、<code class="literal">-l 80%ORIGIN</code>）でなければいけません。
+ </td></tr></tbody></table></div></div><br class="table-break" /></dd><dt class="varlistentry"><span class="term">
+ <a id="idm29829792" class="indexterm"></a>
+ <span class="application"><strong>presto</strong></span> (<span class="package">yum-presto</span>)</span></dt><dd><div class="para">
+ <span class="application"><strong>presto</strong></span> プラグインは、<span class="application"><strong>presto</strong></span> メタ情報を有効にしたリポジトリから更新している間に、<em class="firstterm">delta RPM</em> パッケージのダウンロードすることに関するサポートを Yum に追加します。delta RPM は、RPM パッケージを要求しているクライアントにインストールされているパッケージのバージョンとリポジトリにある更新されたバージョンの間の差異のみを含みます。
+ </div><div class="para">
+ delta RPM をダウンãƒãƒ¼ãƒ‰ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€æ›´æ–°ã•ã‚ŒãŸãƒ‘ッケージ全体をダウンãƒãƒ¼ãƒ‰ã™ã‚‹ã‚ˆã‚Šã‚‚ã‹ãªã‚Šæ—©ããªã‚Šã€æ›´æ–°ã‚’相対的ã«é€Ÿåº¦å‘上ã§ãã¾ã™ã€‚一度 delta RPM ãŒãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã•ã‚Œã‚‹ã¨ã€ç¾åœ¨ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るパッケージã«å¤‰æ›´ç‚¹ã‚’é©ç”¨ã™ã‚‹ãŸã‚ã«ãƒªãƒ“ルドã—ãªã‘ã‚Œã°ã„ã‘ã¾ã›ã‚“ã€ã“ã®ã‚ˆã†ã«å®Œå…¨ã‹ã¤æ›´æ–°ã•ã‚ŒãŸãƒ‘ッケージを作æˆã—ã¾ã™ã€‚ã“ã®ãƒ—ãƒã‚»ã‚¹ã¯ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¦ã„るマシンã«ãŠã„㦠CPU 時間を使用ã—ã¾ã™ã€‚ãã®ãŸã‚ã€delta RPM を使用ã™ã‚‹ã“ã¨ã¯ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æŽ¥ç¶šã«ä¾å˜ã™ã‚‹ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰æ™‚é–“ã€ãŠã‚ˆã³ CPU ã®é™ç•Œã«ã‚ˆã‚‹ãƒªãƒ“ルド時間ã®ãƒˆãƒ¬ãƒ¼ãƒ‰ã‚ªãƒ•ã«ãªã‚Šã¾ã™ã€‚<span class="application"><strong>presto</strong></span> プラグインを使用ã™ã‚‹ã“ã¨ã¯ã€æ¯”較的低速ãªãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æŽ¥ç¶šã‚’æŒã¤é«˜é€Ÿãªãƒžã‚·ãƒ³ã¨ã‚·ã‚¹ãƒ†ãƒ ã®ãŸã‚ã«æŽ¨å¥¨ã•ã‚
Œã¾ã™ã€‚一方ã€éžå¸¸ã«é«˜é€ŸãªæŽ¥ç¶šã‚’æŒã¤æ¯”較的低速ãªãƒžã‚·ãƒ³ã¯ã€é€šå¸¸ã® RPM パッケージをダウンãƒãƒ¼ãƒ‰ã™ã‚‹ã“ã¨ã€ã¤ã¾ã‚Š <span class="application"><strong>presto</strong></span> を無効ã«ã™ã‚‹ã“ã¨ã®æ©æµã‚’å—ã‘られる<span class="emphasis"><em>ã‹ã‚‚</em></span>ã—ã‚Œã¾ã›ã‚“。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm56956336" class="indexterm"></a>
+ <span class="application"><strong>refresh-packagekit</strong></span> (<span class="package">PackageKit-yum-plugin</span>)</span></dt><dd><div class="para">
+ <span class="application"><strong>refresh-packagekit</strong></span> プラグインは <code class="command">yum</code> を実行するときに必ず <span class="application"><strong>PackageKit</strong></span> の管理情報を更新します。<span class="application"><strong>refresh-packagekit</strong></span> プラグインはデフォルトでインストールされます。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm33651520" class="indexterm"></a>
+ <span class="application"><strong>rhnplugin</strong></span> (<span class="package">yum-rhn-plugin</span>)</span></dt><dd><div class="para">
+ <span class="application"><strong>rhnplugin</strong></span> は <code class="systemitem">RHN Classic</code> への接続サポートを提供します。これにより、<code class="systemitem">RHN Classic</code> を用いて登録されたシステムはこのシステムからパッケージを更新およびインストールできるようになります。
+ </div><div class="para">
+ プラグインに関する詳細は<span class="bold bold"><strong>rhnplugin</strong></span>(8) マニュアルページを参照してください。
+ </div></dd><dt class="varlistentry"><span class="term">
+ <a id="idm47080048" class="indexterm"></a>
+ <span class="application"><strong>security</strong></span> (<span class="package">yum-plugin-security</span>)</span></dt><dd><div class="para">
+ セキュリティ更新に関する情報を探して、簡単に適用することは、すべてのシステム管理者に対してしばしば重要になります。このため、Yum は <span class="application"><strong>security</strong></span> プラグインを提供します。これは非常に有用なセキュリティ関連のコマンド、サブコマンドおよびオプションを用いて <code class="command">yum</code> を拡張します。
+ </div><div class="para">
+ 以下のようにセキュリティ関連の更新をチェックできます:
+ </div><pre class="screen">~]# <code class="command">yum check-update --security</code>
+Loaded plugins: langpacks, presto, refresh-packagekit, security
+Limiting package lists to security relevant ones
+updates-testing/updateinfo | 329 kB 00:00
+9 package(s) needed for security, out of 270 available
+
+ConsoleKit.x86_64 0.4.5-1.fc15 updates
+ConsoleKit-libs.x86_64 0.4.5-1.fc15 updates
+ConsoleKit-x11.x86_64 0.4.5-1.fc15 updates
+NetworkManager.x86_64 1:0.8.999-2.git20110509.fc15 updates
+NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre><div class="para">
+ セキュリティ・アドバイザリにより影響されるパッケージを更新するには <code class="command">yum update --security</code> または <code class="command">yum update-minimal --security</code> を使用できます。これらのコマンドはどちらも、システムにあるセキュリティ・アドバイザリが発行されたパッケージをすべて更新します。<code class="command">yum update-minimal --security</code> はセキュリティ・アドバイザリの一部として公開された最新のパッケージに更新します。ここで <code class="command">yum update --security</code> はセキュリティ・アドバイザリにより影響されるすべてのパッケージを<span class="emphasis"><em>その利用可能なパッケージの最新バージョンに</em></span>更新します。
+ </div><div class="para">
+ 言い換えると、たとえば:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">kernel-2.6.38.4-20</span> パッケージはシステムにインストールされました;
+ </div></li><li class="listitem"><div class="para">
+ the <span class="package">kernel-2.6.38.6-22</span> パッケージがセキュリティアップデートとしてリリースされました;
+ </div></li><li class="listitem"><div class="para">
+ then <span class="package">kernel-2.6.38.6-26</span> はバグ修正アップデートとしてリリースされました、
+ </div></li></ul></div><div class="para">
+ ...そして <code class="command">yum update-minimal --security</code> は <span class="package">kernel-2.6.38.6-22</span> に更新します。また、<code class="command">yum update --security</code> は <span class="package">kernel-2.6.38.6-26</span> に更新します。保守的な管理者はできる限りパッケージを更新することにより生じるリスクを減らすために <code class="command">update-minimal</code> を使用したいと思うかもしれません。
+ </div><div class="para">
+ <span class="application"><strong>security</strong></span> プラグインが <code class="command">yum</code> に追加する機能改善に関する使用法の詳細とさらなる説明は、<span class="bold bold"><strong>yum-security</strong></span>(8) マニュアルページを参照してください。
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_More_Yum_Plugins.html"><strong>戻る</strong>4.4.2. 追加の Yum プラグインのインストール</a></li><li class="up"><a accesskey="u" href="#"><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>4.5. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Printer_Configuration.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Printer_Configuration.html
new file mode 100644
index 0000000..306e887
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-File_and_Print_Servers.html" title="第16章 ファイルサーバーおよびプリントサーバー" /><link rel="prev" href="s2-ftp-resources.html" title="16.2.6. その他のリソース" /><link rel="next" href="sec-Setting_Printer.html" title="16.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">16.3. プリンタの設定</h2></div></div></div><a id="idm68239824" class="indexterm"></a><a id="idm58198160" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Printer Configuration</strong></span> 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="idm51313232" 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">16.3.1. Starting the Printer Configuration Tool</h3></div></div></div><div class="para">
+ With the Printer Configuration tool you can perform various operations on existing printers and set up new printers.
+ </div><div class="para">
+ On the upper panel, go to <span class="guimenu"><strong>Activities</strong></span>, choose <span class="guisubmenu"><strong>Applications</strong></span> and click <span class="guimenuitem"><strong>Printing</strong></span>. Alternatively, run the <code class="command">system-config-printer</code> command from the command line to start the tool.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Printer Configuration</strong></span> window depicted in <a class="xref" href="sec-Printer_Configuration.html#fig-printconf-main">図16.2「Printer 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="Printer Configuration window" /><div class="longdesc"><div class="para">
+ Printer Configuration window
+ </div></div></div></div><h6>図16.2 Printer 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>16.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>16.3.2. Starting Printer Setup</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Removing.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Removing.html
new file mode 100644
index 0000000..cf59321
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Removing.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>4.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="4.2. パッケージとパッケージ グループ" /><link rel="prev" href="sec-Installing.html" title="4.2.4. パッケージのインストール" /><link rel="next" href="sec-Yum-Transaction_History.html" title="4.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=
"sec-Installing.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Yum-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">4.2.5. パッケージの削除</h3></div></div></div><a id="idm41098688" class="indexterm"></a><a id="idm57402880" class="indexterm"></a><div class="para">
+ パッケージのインストールと同様に、Yumは個別のパッケージとパッケージのグループをアンインストール (<span class="application"><strong>RPM</strong></span> と Yum の言葉においては削除) することができます。
+ </div><h4 id="bh-Removing_Individual_Packages">個別のパッケージの削除</h4><a id="idm57399808" class="indexterm"></a><a id="idm57397840" class="indexterm"></a><div class="para">
+ 特定のパッケージおよびそれに依存するあらゆるパッケージをアンインストールするには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">remove</code> <em class="replaceable"><code>package_name</code></em>…</pre><div class="para">
+ 複数のパッケージをインストールするときのように、複数のパッケージ名をコマンドに追加することにより同時に削除できます。たとえば、<span class="package">totem</span>, <span class="package">rhythmbox</span>, および <span class="package">sound-juicer</span> を削除するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum remove totem rhythmbox sound-juicer</code></pre><div class="para">
+ <code class="command">install</code> 同様、<code class="command">remove</code> もこれらの引数をとることができます:
+ </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></ul></div><div class="warning" id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It"><div class="admonition_header"><h2>他のパッケージに依存するときのパッケージの削除</h2></div><div class="admonition"><div class="para">
+ Yum はあるパッケージに依存しているパッケージを削除せずにそれを削除することはできません。この種の操作は <span class="application"><strong>RPM</strong></span> によってのみ実行できますが、推奨されません。そして、潜在的にシステムを機能しない状態にする可能性がありまる、またはアプリケーションを不正動作かつ/またはクラッシュさせる可能性があります。さらなる情報は <span class="application"><strong>RPM</strong></span> の章にある<a class="xref" href="s2-rpm-uninstalling.html">「アンインストール」</a>を参照してください。
+ </div></div></div><h4 id="bh-Removing_a_Package_Group">パッケージ グループの削除</h4><div class="para">
+ <code class="command">install</code> 構文を用いて構文一致を使用してパッケージグループを削除できます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">groupremove</code> <em class="replaceable"><code>group</code></em></pre><pre class="synopsis"><code class="command">yum</code> <code class="option">remove</code> @<em class="replaceable"><code>group</code></em></pre><div class="para">
+ 以下はそれぞれ異なりますが、<code class="literal">KDE Desktop</code> グループを削除する同等の方法です:
+ </div><pre class="screen">~]# <code class="command">yum groupremove "KDE Desktop"</code>
+~]# <code class="command">yum groupremove kde-desktop</code>
+~]# <code class="command">yum remove @kde-desktop</code></pre><div class="important" id="important-Package_Group_Removal"><div class="admonition_header"><h2>インテリジェントなパッケージグループの削除</h2></div><div class="admonition"><a id="idm75048544" class="indexterm"></a><a id="idm75047136" class="indexterm"></a><div class="para">
+ <span class="application"><strong>yum</strong></span> ã«ãƒ‘ッケージグループを削除ã™ã‚‹ã‚ˆã†æŒ‡ç¤ºã™ã‚‹ã¨ãã€ãれらã®ãƒ‘ッケージãŒä»–ã®ãƒ‘ッケージグループã®ãƒ¡ãƒ³ãƒãƒ¼ã§ã‚ã£ãŸã‚Šã€ä»–ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るパッケージã«ä¾å˜ã—ãŸã‚Šã—ã¦ã„ã¦ã‚‚ã€ãã®ã‚°ãƒ«ãƒ¼ãƒ—ã«ã‚ã‚‹ã™ã¹ã¦ã®ãƒ‘ッケージãŒå‰Šé™¤ã•ã‚Œã¾ã™ã€‚ã—ã‹ã—ãªãŒã‚‰ã€<code class="option">groupremove_leaf_only=1</code> ディレクティブを <code class="filename">/etc/yum.conf</code> è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã® <code class="literal">[main]</code> セクションã«è¿½åŠ ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ã‚らゆる他ã®ãƒ‘ッケージやグループã«å¿…è¦ã¨ã•ã‚Œãªã„パッケージã®ã¿ã‚’削除ã™ã‚‹ã‚ˆã† <code class="command">yum</code> ã«æŒ‡ç¤ºã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–ã®è©³ç´°ã¯<a class="xref" href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">「[main] オプションã
®è¨å®šã€</a>ã‚’å‚ç…§ã—ã¦ãã ã•ã„。
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing.html"><strong>戻る</strong>4.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="sec-Yum-Transaction_History.html"><strong>次へ</strong>4.2.6. 処理とトランザクションの履歴</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html
new file mode 100644
index 0000000..719273c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>22.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="第22章 Working with Kernel Modules" /><link rel="prev" href="sec-Unloading_a_Module.html" title="22.4. Unloading a Module" /><link rel="next" href="sec-Persistent_Module_Loading.html" title="22.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">22.5. Setting Module Parameters</h2></div></div></div><a id="idm41305328" class="indexterm"></a><a id="idm41303888" 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="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 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>手順22.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. For example:
+ </div><pre class="screen">~]# <code class="command">lsmod | grep e1000e</code>
+~]# </pre><div class="para">
+ Output indicates that the module is already loaded into the kernel, in which case you must first unload it before proceeding. Refer to <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 Energy Efficient Ethernet (EEE) turned on<a href="#ftn.footnote-Energy_Efficient_Ethernet" class="footnote"><sup class="footnote" id="footnote-Energy_Efficient_Ethernet">[3]</sup></a> , you would run, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">modprobe e1000e InterruptThrottleRate=3000,3000,3000 EEE=1</code></pre><div class="para">
+ This example illustrates passing multiple valued to a single parameter by separating them with commas and omitting any spaces between them.
+ </div></li></ol></div><div class="footnotes"><br /><hr /><div id="footnote-Energy_Efficient_Ethernet" class="footnote"><div class="para"><a href="#footnote-Energy_Efficient_Ethernet" class="para"><sup class="para">[3] </sup></a>
+ Despite what the example might imply, Energy Efficient Ethernet is turned on by default in the <code class="systemitem">e1000e</code> driver.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Unloading_a_Module.html"><strong>戻る</strong>22.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>22.6. Persistent Module Loading</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Setting_Printer.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Setting_Printer.html
new file mode 100644
index 0000000..7f1d66a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Setting_Printer.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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="next" href="sec-Adding_Other_Printer.html" title="16.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">16.3.2. Starting Printer Setup</h3></div></div></div><a id="idm41011456" 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 the root 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 Printer Configuration tool (refer to <a class="xref" href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">「Starting the Printer Configuration Tool」</a>).
+ </div></li><li class="step"><div class="para">
+ Go to <span class="guimenu"><strong>Server</strong></span> → <span class="guisubmenu"><strong>New</strong></span> → <span class="guimenuitem"><strong>Printer</strong></span>.
+ </div></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Authentication Required</strong></span> box, type the root user password and confirm.
+ </div></li><li class="step"><div class="para">
+ Select the printer connection type and provide its details in the area on the right.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Printer_Configuration.html"><strong>戻る</strong>16.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>16.3.3. ローカルプリンタの追加</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Setting_repository_Options.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Setting_repository_Options.html
new file mode 100644
index 0000000..37980ec
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Setting_repository_Options.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.3.2. [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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="4.3. Yum と Yum リポジトリーの設定" /><link rel="prev" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="4.3. Yum と Yum リポジトリーの設定" /><link rel="next" href="sec-Using_Yum_Variables.html" title="4.3.3. Yum 変数の使い方" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_Yum_and_Yum_Repositories.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Yum_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">4.3.2. [repository] オプションの設定</h3></div></div></div><a id="idm59065744" class="indexterm"></a><div class="para">
+ <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクション、ここで <em class="replaceable"><code>repository</code></em> は <code class="literal">my_personal_repo</code> のような一意なリポジトリ ID です（空白は許可されません）、は個々の Yum リポジトリを定義できます。
+ </div><div class="para">
+ 以下は <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションが受け取る形式のごく最低限の例です:
+ </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">
+ すべての <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> セクションは以下のディレクティブを必ず含まなければいけません:
+ </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">
+ …ここで <em class="replaceable"><code>repository_name</code></em> は人間が読みやすいリポジトリの説明文です。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">baseurl</code>=<em class="replaceable"><code>repository_url</code></em></span></dt><dd><div class="para">
+ …ここで <em class="replaceable"><code>repository_url</code></em> はリポジトリの repodata ディレクトリが置かれているディレクトリへの URL です:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ リポジトリが HTTP 経由で利用可能ならば、次を使用します: <code class="literal">http://path/to/repo</code>
+ </div></li><li class="listitem"><div class="para">
+ リポジトリが FTP で利用可能ならば、次を使用します: <code class="literal">ftp://path/to/repo</code>
+ </div></li><li class="listitem"><div class="para">
+ リポジトリがマシンのローカルならば、次を使用します: <code class="literal">file:///path/to/local/repo</code>
+ </div></li><li class="listitem"><div class="para">
+ 特定のオンラインのリポジトリが HTTP ベーシック認証を必要とするならば、<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> のように URL の前にユーザー名とパスワードを指定できます。たとえば、http://www.example.com/repo/ にあるリポジトリが、ユーザー名 <span class="quote">「<span class="quote">user</span>」</span> とパスワード <span class="quote">「<span class="quote">password</span>」</span> を必要とするならば、 <code class="option">baseurl</code> リンクは <code class="option">http://<strong class="userinput"><code>user</code></strong>:<strong class="userinput"><code>password</code></strong>@www.example.com/repo/</code> のように指定できます。
+ </div></li></ul></div><div class="para">
+ この URL は通常次のような HTTP リンクです:
+ </div><pre class="programlisting">baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</pre><div class="para">
+ Yum は必ず URL にある <code class="varname">$releasever</code>, <code class="varname">$arch</code>, および <code class="varname">$basearch</code> 変数を展開します。Yum 変数の詳細は <a class="xref" href="sec-Using_Yum_Variables.html">「Yum 変数の使い方」</a> を参照してください。
+ </div></dd></dl></div><div class="para">
+ 他の有用な <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> ディレクティブは以下です:
+ </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">
+ …ここで <em class="replaceable"><code>value</code></em> は次のどれかです:
+ </div><div class="para">
+ <code class="literal">0</code> — 更新およびインストールを実行するとき派ケージソースとしてこのリポジトリを含めません。これは素早くリポジトリをオンオフする簡単な情報です。これは更新またはインストールのために有効にしたくないリポジトリから単一のパッケージを希望するときに有用です。
+ </div><div class="para">
+ <code class="literal">1</code> — このリポジトリをパッケージソースとして含めます。
+ </div><div class="para">
+ リポジトリを有効または無効にするには、<code class="option">--enablerepo=<em class="replaceable"><code>repo_name</code></em></code> or <code class="option">--disablerepo=<em class="replaceable"><code>repo_name</code></em></code> オプションを <code class="command">yum</code> に渡すことにより、または、<span class="application"><strong>PackageKit</strong></span> ユーティリティの<span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span> ウィンドウにより実行できます。
+ </div></dd></dl></div><div class="para">
+ さらに多くの <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> オプションが存在します。完全な一覧は <span class="bold bold"><strong>yum.conf</strong></span>(5) マニュアルページの <code class="literal">[repository] OPTIONS</code> セクションを参照してください。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>戻る</strong>4.3. Yum と Yum リポジトリーの設定</a></li><li class="up"><a accesskey="u" href="#"><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_Yum_Variables.html"><strong>次へ</strong>4.3.3. Yum 変数の使い方</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Specific_Kernel_Module_Capabilities.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Specific_Kernel_Module_Capabilities.html
new file mode 100644
index 0000000..926b317
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Specific_Kernel_Module_Capabilities.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>22.7. Specific Kernel Module Capabilities</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="第22章 Working with Kernel Modules" /><link rel="prev" href="sec-Persistent_Module_Loading.html" title="22.6. Persistent Module Loading" /><link rel="next" href="sec-Using_Channel_Bonding.html" title="22.7.2. Using Channel Bonding" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_Module_Loading.html
"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Channel_Bonding.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Specific_Kernel_Module_Capabilities"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.7. Specific Kernel Module Capabilities</h2></div></div></div><div class="para">
+ This section explains how to enable specific kernel capabilities using various kernel modules.
+ </div><div class="section" id="sec-Using_Multiple_Ethernet_Cards"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.1. 複数のイーサネットカードの使用</h3></div></div></div><a id="idm68939040" class="indexterm"></a><div class="para">
+ It is possible to use multiple Ethernet cards on a single machine. For each card there must be an <code class="command">alias</code> and, possibly, <code class="command">options</code> lines for each card in a user-created <code class="filename"><em class="replaceable"><code>module_name</code></em>.conf</code> file in the <code class="filename">/etc/modprobe.d/</code> directory.
+ </div><div class="para">
+ For additional information about using multiple Ethernet cards, refer to the <em class="citetitle">Linux Ethernet-HOWTO</em> online at <a href="http://www.redhat.com/mirrors/LDP/HOWTO/Ethernet-HOWTO.html">http://www.redhat.com/mirrors/LDP/HOWTO/Ethernet-HOWTO.html</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Persistent_Module_Loading.html"><strong>戻る</strong>22.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="sec-Using_Channel_Bonding.html"><strong>次へ</strong>22.7.2. Using Channel Bonding</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Unloading_a_Module.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Unloading_a_Module.html
new file mode 100644
index 0000000..2561cf0
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Unloading_a_Module.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>22.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="第22章 Working with Kernel Modules" /><link rel="prev" href="sec-Loading_a_Module.html" title="22.3. モジュールの読み込み方法" /><link rel="next" href="sec-Setting_Module_Parameters.html" title="22.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">22.4. Unloading a Module</h2></div></div></div><a id="idm35005328" class="indexterm"></a><a id="idm35003888" class="indexterm"></a><a id="idm35001488" 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">
+ Refer to <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>例22.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 (because you believe there is a bug in it that is affecting system stability, for example), your terminal session might look similar to this:
+ </div><pre class="screen">~]# <code class="command">modinfo -F depends firewire_ohci</code>
+depends: firewire-core
+~]# <code class="command">modinfo -F depends firewire_core</code>
+depends: crc-itu-t
+~]# <code class="command">modinfo -F depends crc-itu-t</code>
+depends:</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 /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-ohci.ko
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-core.ko
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</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="idm66512384" class="indexterm"></a><a id="idm66509984" 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>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-Setting_Module_Parameters.html"><strong>次へ</strong>22.5. Setting Module Parameters</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-User_and_System_Connections.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-User_and_System_Connections.html
new file mode 100644
index 0000000..0f85888
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-User_and_System_Connections.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.4. User and System Connections</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Interacting_with_NetworkManager.html" title="6.2. Interacting with NetworkManager" /><link rel="prev" href="sec-Connecting_to_a_Network_Automatically.html" title="6.2.3. Connecting to a Network Automatically" /><link rel="next" href="sec-Establishing_Connections.html" title="6.3. Establishing Connections" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Connecting_to_a_Network_Automatically.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_Connections.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-User_and_System_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.4. User and System Connections</h3></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> connections are always either <span class="emphasis"><em>user connections</em></span> or <span class="emphasis"><em>system connections</em></span>. Depending on the system-specific policy that the administrator has configured, users may need root privileges to create and modify system connections. <span class="application"><strong>NetworkManager</strong></span>'s default policy enables users to create and modify user connections, but requires them to have root privileges to add, modify or delete system connections.
+ </div><div class="para">
+ User connections are so-called because they are specific to the user who creates them. In contrast to system connections, whose configurations are stored under the <code class="filename">/etc/sysconfig/network-scripts/</code> directory (mainly in <code class="filename">ifcfg-<em class="replaceable"><code><network_type></code></em> </code> interface configuration files), user connection settings are stored in the GConf configuration database and the GNOME keyring, and are only available during login sessions for the user who created them. Thus, logging out of the desktop session causes user-specific connections to become unavailable.
+ </div><div class="note" id="note-Tip-Increase_security_by_making_VPN_connections_user-specific"><div class="admonition_header"><h2>Increase security by making VPN connections user-specific</h2></div><div class="admonition"><div class="para">
+ Because <span class="application"><strong>NetworkManager</strong></span> uses the GConf and GNOME keyring applications to store user connection settings, and because these settings are specific to your desktop session, it is highly recommended to configure your personal VPN connections as user connections. If you do so, other non-root users on the system cannot view or access these connections in any way.
+ </div></div></div><div class="para">
+ System connections, on the other hand, become available at boot time and can be used by other users on the system without first logging in to a desktop session.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> can quickly and conveniently convert user to system connections and vice versa. Converting a user connection to a system connection causes <span class="application"><strong>NetworkManager</strong></span> to create the relevant interface configuration files under the <code class="filename">/etc/sysconfig/network-scripts/</code> directory, and to delete the GConf settings from the user's session. Conversely, converting a system to a user-specific connection causes <span class="application"><strong>NetworkManager</strong></span> to remove the system-wide configuration files and create the corresponding GConf/GNOME keyring settings.
+ </div><div class="figure" id="exam-User_and_System_Connections"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network_Configuration-NM-Available_to_all_users"><img src="images/Network_Configuration-NM-Available_to_all_users_Gnome3.png" alt="The Available to all users checkbox controls whether connections are user-specific or system-wide" /><div class="longdesc"><div class="para">
+ A screen shot of the Available to all users checkbox
+ </div></div></div></div><h6>図6.4 The <span class="guilabel">Available to all users</span> checkbox controls whether connections are user-specific or system-wide</h6></div><br class="figure-break" /><div class="procedure" id="procedure-Changing_a_Connection_to_be_User-Specific_instead_of_System-Wide_or_Vice-Versa"><h6>手順6.2 Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa</h6><div class="note" id="note-Depending_on_the_systems_policy_root_privileges_may_be_required"><div class="admonition_header"><h2>Root privileges may be required</h2></div><div class="admonition"><div class="para">
+ Depending on the system's policy, you may need root privileges on the system in order to change whether a connection is user-specific or system-wide.
+ </div></div></div><ol class="1"><li class="step"><div class="para">
+ Click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Network Settings</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the menu entry for the type of network connection you want to configure.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Configure</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Check the <span class="guilabel"><strong>Available to all users</strong></span> checkbox to ask <span class="application"><strong>NetworkManager</strong></span> to make the connection a system-wide connection. Depending on system policy, you may then be prompted for the root password by the <span class="application"><strong>PolicyKit</strong></span> application. If so, enter the root password to finalize the change.
+ </div><div class="para">
+ Conversely, uncheck the <span class="guilabel"><strong>Available to all users</strong></span> checkbox to make the connection user-specific.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Connecting_to_a_Network_Automatically.html"><strong>戻る</strong>6.2.3. Connecting to a Network Automatically</a></li><li class="up"><a accesskey="u" href="#"><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-Establishing_Connections.html"><strong>次へ</strong>6.3. Establishing Connections</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Add_Remove_Software.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Add_Remove_Software.html
new file mode 100644
index 0000000..572d612
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Add_Remove_Software.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-PackageKit.html" title="第5章 PackageKit" /><link rel="prev" href="ch-PackageKit.html" title="第5章 PackageKit" /><link rel="next" href="sec-Finding_Packages_with_Filters.html" title="5.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-PackageKit.html"><strong>戻る</strong></a></li><li class
="next"><a accesskey="n" href="sec-Finding_Packages_with_Filters.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Using_Add_Remove_Software"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. ソフトウェアの追加/削除の使用</h2></div></div></div><a id="idm125826496" class="indexterm"></a><a id="idm73715440" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> の <span class="application"><strong>ソフトウェアの更新</strong></span> GUI ウィンドウは、直感的に同じようなインターフェースを持ちますが、<span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>アプリケーションと独立したアプリケーションです。新しいパッケージを検索およびインストールするには、<span class="guimenu"><strong>Activities</strong></span> メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>ソフトウェアの追加/削除</strong></span>を選択するか、シェルプロンプトにおいて <code class="command">gpk-application</code> コマンドを実行します。
+ </div><div class="figure" id="fig-Graphical_Package_Management-add_remove_software"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software.png" alt="PackageKit のソフトウェアの追加/削除ウィンドウ" /><div class="longdesc"><div class="para">
+ Viewing PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>図5.4 PackageKit のソフトウェアの追加/削除ウィンドウ</h6></div><br class="figure-break" /><div class="section" id="sec-Refreshing_Software_Sources_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.1. ソフトウェアソースの更新 (Yum リポジトリー)</h3></div></div></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> リポジトリを有効化または無効化するには、<span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアのソース</strong></span>をクリックしてダイアログボックスを開き、<span class="guilabel"><strong>ソフトウェアのソース</strong></span>タブを選択します。利用可能な設定オプションの詳細は<a class="xref" href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">「ソフトウェアソースの設定」</a>を参照してください。
+ </div><div class="para">
+ 適切な <span class="application"><strong>Yum</strong></span> リポジトリの有効化・無効化後、利用可能なパッケージの最新一覧を持っていることを確実にしなければいけません。<span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>パッケージ一覧の更新</strong></span>をクリックすると、<span class="application"><strong>PackageKit</strong></span> は、すべての利用可能なソフトウェアのソース、つまり <span class="application"><strong>Yum</strong></span> リポジトリからパッケージの最新一覧を取得します。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-PackageKit.html"><strong>戻る</strong>第5章 PackageKit</a></li><li class="up"><a accesskey="u" href="#"><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-Finding_Packages_with_Filters.html"><strong>次へ</strong>5.2.2. フィルターを用いたパッケージの検索</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Channel_Bonding.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Channel_Bonding.html
new file mode 100644
index 0000000..24bb47f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Channel_Bonding.html
@@ -0,0 +1,191 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7.2. Using Channel Bonding</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Specific_Kernel_Module_Capabilities.html" title="22.7. Specific Kernel Module Capabilities" /><link rel="prev" href="sec-Specific_Kernel_Module_Capabilities.html" title="22.7. Specific Kernel Module Capabilities" /><link rel="next" href="s1-kernel-modules-additional-resources.html" title="22.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 access
key="p" href="sec-Specific_Kernel_Module_Capabilities.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="sec-Using_Channel_Bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.2. Using Channel Bonding</h3></div></div></div><a id="idm54967792" class="indexterm"></a><a id="idm68167824" class="indexterm"></a><a id="idm68166384" class="indexterm"></a><a id="idm68164944" class="indexterm"></a><a id="idm68163536" class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind NICs together into a single channel using the <code class="filename">bonding</code> kernel module and a special network interface, called a <em class="firstterm">channel bonding interface</em>. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><a id="idm58912576" class="indexterm"></a><a id="idm58911136" class="indexterm"></a><div class="para">
+ 管理者は次の手順にて 複数のネットワークインターフェースをチャネル ボンディングしてください。
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ As <code class="systemitem">root</code>, create a new file named <code class="filename"><em class="replaceable"><code>bonding</code></em>.conf</code> in the <code class="filename">/etc/modprobe.d/</code> directory. Note that you can name this file anything you like as long as it ends with a <code class="filename">.conf</code> extension. Insert the following line in this new file:
+ </div><pre class="screen">alias bond<em class="replaceable"><code>N</code></em> bonding</pre><div class="para">
+ Replace <em class="replaceable"><code>N</code></em> with the interface number, such as <code class="command">0</code>. For each configured channel bonding interface, there must be a corresponding entry in your new <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code> file.
+ </div></li><li class="listitem"><div class="para">
+ Configure a channel bonding interface as outlined in <a class="xref" href="s2-networkscripts-interfaces-chan.html">「チャンネル・ボンディング・インターフェース」</a>.
+ </div></li><li class="listitem"><div class="para">
+ To enhance performance, adjust available module options to ascertain what combination works best. Pay particular attention to the <code class="command">miimon</code> or <code class="command">arp_interval</code> and the <code class="command">arp_ip_target</code> parameters. Refer to <a class="xref" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">「Bonding Module Directives」</a> for a list of available options and how to quickly determine the best ones for your bonded interface.
+ </div></li></ol></div><div class="section" id="s3-modules-bonding-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.2.1. Bonding Module Directives</h4></div></div></div><a id="idm67964128" class="indexterm"></a><a id="idm67962240" class="indexterm"></a><a id="idm59916976" class="indexterm"></a><div class="para">
+ It is a good idea to test which channel bonding module parameters work best for your bonded interfaces before adding them to the <em class="parameter"><code>BONDING_OPTS="<em class="replaceable"><code>bonding parameters</code></em>"</code></em> directive in your bonding interface configuration file (<code class="filename">ifcfg-bond0</code> for example). Parameters to bonded interfaces can be configured without unloading (and reloading) the bonding module by manipulating files in the <code class="systemitem">sysfs</code> file system.
+ </div><div class="para">
+ <code class="systemitem">sysfs</code> is a virtual file system that represents kernel objects as directories, files and symbolic links. <code class="systemitem">sysfs</code> can be used to query for information about kernel objects, and can also manipulate those objects through the use of normal file system commands. The <code class="systemitem">sysfs</code> virtual file system has a line in <code class="filename">/etc/fstab</code>, and is mounted under the <code class="filename">/sys/</code> directory. All bonding interfaces can be configured dynamically by interacting with and manipulating files under the <code class="filename">/sys/class/net/</code> directory.
+ </div><div class="para">
+ In order to determine the best parameters for your bonding interface, create a channel bonding interface file such as <code class="filename">ifcfg-bond0</code> by following the instructions in <a class="xref" href="s2-networkscripts-interfaces-chan.html">「チャンネル・ボンディング・インターフェース」</a>. Insert the <em class="parameter"><code>SLAVE=yes</code></em> and <em class="parameter"><code>MASTER=bond0</code></em> directives in the configuration files for each interface bonded to bond0. Once this is completed, you can proceed to testing the parameters.
+ </div><div class="para">
+ First, bring up the bond you created by running <code class="command">ifconfig <code class="option">bond<em class="replaceable"><code>N</code></em></code> <code class="option">up</code></code> as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">ifconfig bond0 up</code>
+</pre><div class="para">
+ If you have correctly created the <code class="filename">ifcfg-bond0</code> bonding interface file, you will be able to see <code class="computeroutput">bond0</code> listed in the output of running <code class="command">ifconfig</code> (without any options):
+ </div><pre class="screen">~]# <code class="command">ifconfig</code>
+bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
+ UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
+ RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
+eth0 Link encap:Ethernet HWaddr 52:54:00:26:9E:F1
+ inet addr:192.168.122.251 Bcast:192.168.122.255 Mask:255.255.255.0
+ inet6 addr: fe80::5054:ff:fe26:9ef1/64 Scope:Link
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:207 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:205 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:1000
+ RX bytes:70374 (68.7 KiB) TX bytes:25298 (24.7 KiB)
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em>
+</pre><div class="para">
+ To view all existing bonds, even if they are not up, run:
+ </div><pre class="screen">~]# <code class="command">cat /sys/class/net/bonding_masters</code>
+bond0</pre><div class="para">
+ You can configure each bond individually by manipulating the files located in the <code class="filename">/sys/class/net/bond<em class="replaceable"><code>N</code></em>/bonding/</code> directory. First, the bond you are configuring must be taken down:
+ </div><pre class="screen">~]# <code class="command">ifconfig bond0 down</code>
+</pre><div class="para">
+ As an example, to enable MII monitoring on bond0 with a 1 second interval, you could run (as <code class="systemitem">root</code>):
+ </div><pre class="screen">~]# <code class="command">echo 1000 > /sys/class/net/bond0/bonding/miimon</code>
+</pre><div class="para">
+ To configure bond0 for <em class="parameter"><code>balance-alb</code></em> mode, you could run either:
+ </div><pre class="screen">~]# <code class="command">echo 6 > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ ...or, using the name of the mode:
+ </div><pre class="screen">~]# <code class="command">echo balance-alb > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ After configuring options for the bond in question, you can bring it up and test it by running <code class="command">ifconfig bond<em class="replaceable"><code>N</code></em> <code class="option">up</code> </code>. If you decide to change the options, take the interface down, modify its parameters using <code class="systemitem">sysfs</code>, bring it back up, and re-test.
+ </div><div class="para">
+ Once you have determined the best set of parameters for your bond, add those parameters as a space-separated list to the <em class="parameter"><code>BONDING_OPTS=</code></em> directive of the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code>N</code></em> </code> file for the bonding interface you are configuring. Whenever that bond is brought up (for example, by the system during the boot sequence if the <em class="parameter"><code>ONBOOT=yes</code></em> directive is set), the bonding options specified in the <em class="parameter"><code>BONDING_OPTS</code></em> will take effect for that bond. For more information on configuring bonding interfaces (and <em class="parameter"><code>BONDING_OPTS</code></em>), refer to <a class="xref" href="s2-networkscripts-interfaces-chan.html">「チャンネル・ボンディング・インターフェース」</a>.
+ </div><div class="para">
+ The following list provides the names of many of the more common channel bonding parameters, along with a descriptions of what they do. For more information, refer to the brief descriptions for each <code class="computeroutput">parm</code> in <code class="command">modinfo bonding</code> output, or the exhaustive descriptions in the <code class="filename">bonding.txt</code> file in the <span class="package">kernel-doc</span> package (see <a class="xref" href="s1-kernel-modules-additional-resources.html">「その他のリソース」</a>).
+ </div><div class="variablelist"><h6>Bonding Interface Parameters</h6><dl class="variablelist compact"><dt class="varlistentry"><span class="term"> <code class="literal">arp_interval=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often ARP monitoring occurs.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure you specify all required parameters</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div><div class="para">
+ If using this setting while in <code class="literal">mode=0</code> or <code class="literal">mode=1</code> (the two load-balancing modes), the network switch must be configured to distribute packets evenly across the NICs. For more information on how to accomplish this, refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/bonding.txt</code>
+ </div><div class="para">
+ The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_ip_target=<em class="replaceable"><code>ip_address</code></em>[<span class="optional">,<em class="replaceable"><code>ip_address_2</code></em>,…<em class="replaceable"><code>ip_address_16</code></em></span>] </code> </span></dt><dd><div class="para">
+ Specifies the target IP address of ARP requests when the <code class="literal">arp_interval</code> parameter is enabled. Up to 16 IP addresses can be specified in a comma separated list.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_validate=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Validate source/distribution of ARP probes; default is <strong class="userinput"><code>none</code></strong>. Other valid values are <strong class="userinput"><code>active</code></strong>, <strong class="userinput"><code>backup</code></strong>, and <strong class="userinput"><code>all</code></strong>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">debug=<em class="replaceable"><code>number</code></em> </code> </span></dt><dd><div class="para">
+ Enables debug messages. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Debug messages are disabled. This is the default.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Debug messages are enabled.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">downdelay=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait after link failure before disabling the link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term">lacp_rate=<em class="replaceable"><code>value</code></em> </span></dt><dd><div class="para">
+ Specifies the rate at which link partners should transmit LACPDU packets in 802.3ad mode. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>slow</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. This specifies that partners should transmit LACPDUs every 30 seconds.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>fast</code></strong> or <strong class="userinput"><code>1</code></strong> — Specifies that partners should transmit LACPDUs every 1 second.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">miimon=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often MII link monitoring occurs. This is useful if high availability is required because MII is used to verify that the NIC is active. To verify that the driver for a particular NIC supports the MII tool, type the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">ethtool <em class="replaceable"><code>interface_name</code></em> | grep "Link detected:"</code>
+</pre><div class="para">
+ In this command, replace <em class="replaceable"><code>interface_name</code></em> with the name of the device interface, such as <strong class="userinput"><code>eth0</code></strong>, not the bond interface. If MII is supported, the command returns:
+ </div><pre class="screen">Link detected: yes</pre><div class="para">
+ If using a bonded interface for high availability, the module for each NIC must support MII. Setting the value to <strong class="userinput"><code>0</code></strong> (the default), turns this feature off. When configuring this setting, a good starting point for this parameter is <strong class="userinput"><code>100</code></strong>.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure you specify all required parameters</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">mode=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Allows you to specify the bonding policy. The <em class="replaceable"><code>value</code></em> can be one of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-rr</code></strong> or <strong class="userinput"><code>0</code></strong> — Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>active-backup</code></strong> or <strong class="userinput"><code>1</code></strong> — Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-xor</code></strong> or <strong class="userinput"><code>2</code></strong> — Sets an XOR (exclusive-or) policy for fault tolerance and load balancing. Using this method, the interface matches up the incoming request's MAC address with the MAC address for one of the slave NICs. Once this link is established, transmissions are sent out sequentially beginning with the first available interface.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>broadcast</code></strong> or <strong class="userinput"><code>3</code></strong> — Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>802.3ad</code></strong> or <strong class="userinput"><code>4</code></strong> — Sets an IEEE 802.3ad dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a switch that is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-tlb</code></strong> or <strong class="userinput"><code>5</code></strong> — Sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-alb</code></strong> or <strong class="userinput"><code>6</code></strong> — Sets an Active Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for IPV4 traffic. Receive load balancing is achieved through ARP negotiation.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">num_unsol_na=<em class="replaceable"><code>number</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the number of unsolicited IPv6 Neighbor Advertisements to be issued after a failover event. One unsolicited NA is issued immediately after the failover.
+ </div><div class="para">
+ The valid range is <strong class="userinput"><code>0 - 255</code></strong>; the default value is <strong class="userinput"><code>1</code></strong>. This parameter affects only the active-backup mode.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary=<em class="replaceable"><code>interface_name</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the interface name, such as <strong class="userinput"><code>eth0</code></strong>, of the primary device. The <code class="literal">primary</code> device is the first of the bonding interfaces to be used and is not abandoned unless it fails. This setting is particularly useful when one NIC in the bonding interface is faster and, therefore, able to handle a bigger load.
+ </div><div class="para">
+ This setting is only valid when the bonding interface is in <strong class="userinput"><code>active-backup</code></strong> mode. Refer to <code class="filename"> /usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel-version</code></em>/Documentation/networking/bonding.txt</code> for more information.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary_reselect=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the reselection policy for the primary slave. This affects how the primary slave is chosen to become the active slave when failure of the active slave or recovery of the primary slave occurs. This parameter is designed to prevent flip-flopping between the primary slave and other slaves. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>always</code></strong> or <strong class="userinput"><code>0</code></strong> (default) — The primary slave becomes the active slave whenever it comes back up.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>better</code></strong> or <strong class="userinput"><code>1</code></strong> — The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>failure</code></strong> or <strong class="userinput"><code>2</code></strong> — The primary slave becomes the active slave only if the current active slave fails and the primary slave is up.
+ </div></li></ul></div><div class="para">
+ The <code class="literal">primary_reselect</code> setting is ignored in two cases:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no slaves are active, the first slave to recover is made the active slave.
+ </div></li><li class="listitem"><div class="para">
+ When initially enslaved, the primary slave is always made the active slave.
+ </div></li></ul></div><div class="para">
+ Changing the <code class="literal">primary_reselect</code> policy via <code class="systemitem">sysfs</code> will cause an immediate selection of the best active slave according to the new policy. This may or may not result in a change of the active slave, depending upon the circumstances
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">updelay=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait before enabling a link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">use_carrier=<em class="replaceable"><code>number</code></em> </code> </span></dt><dd><div class="para">
+ Specifies whether or not <code class="literal">miimon</code> should use MII/ETHTOOL ioctls or <code class="function">netif_carrier_ok()</code> to determine the link state. The <code class="function">netif_carrier_ok()</code> function relies on the device driver to maintains its state with <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>; most device drivers support this function.
+ </div><div class="para">
+ The MII/ETHROOL ioctls tools utilize a deprecated calling sequence within the kernel. However, this is still configurable in case your device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>.
+ </div><div class="para">
+ Valid values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Default setting. Enables the use of <code class="function">netif_carrier_ok()</code>.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Enables the use of MII/ETHTOOL ioctls.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ If the bonding interface insists that the link is up when it should not be, it is possible that your network device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em></code>.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">xmit_hash_policy=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Selects the transmit hash policy used for slave selection in <strong class="userinput"><code>balance-xor</code></strong> and <strong class="userinput"><code>802.3ad</code></strong> modes. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> or <strong class="userinput"><code>layer2</code></strong> — Default setting. This parameter uses the XOR of hardware MAC addresses to generate the hash. The formula used is:
+ </div><pre class="screen">(<em class="replaceable"><code>source_MAC_address</code></em> XOR <em class="replaceable"><code>destination_MAC</code></em>) MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave, and is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> or <strong class="userinput"><code>layer3+4</code></strong> — Uses upper layer protocol information (when available) to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves.
+ </div><div class="para">
+ The formula for unfragmented TCP and UDP packets used is:
+ </div><pre class="screen">((<em class="replaceable"><code>source_port</code></em> XOR <em class="replaceable"><code>dest_port</code></em>) XOR
+ ((<em class="replaceable"><code>source_IP</code></em> XOR <em class="replaceable"><code>dest_IP</code></em>) AND <code class="constant">0xffff</code>)
+ MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ For fragmented TCP or UDP packets and all other IP protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as the <code class="command">layer2</code> transmit hash policy.
+ </div><div class="para">
+ This policy intends to mimic the behavior of certain switches; particularly, Cisco switches with PFC2 as well as some Foundry and IBM products.
+ </div><div class="para">
+ The algorithm used by this policy is not 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>2</code></strong> or <strong class="userinput"><code>layer2+3</code></strong> — Uses a combination of layer2 and layer3 protocol information to generate the hash.
+ </div><div class="para">
+ Uses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is:
+ </div><pre class="screen">(((<em class="replaceable"><code>source_IP</code></em> XOR <em class="replaceable"><code>dest_IP</code></em>) AND <code class="constant">0xffff</code>) XOR
+ ( <em class="replaceable"><code>source_MAC</code></em> XOR <em class="replaceable"><code>destination_MAC</code></em> ))
+ MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy.
+ </div><div class="para">
+ This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.
+ </div><div class="para">
+ This algorithm is 802.3ad compliant.
+ </div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Specific_Kernel_Module_Capabilities.html"><strong>戻る</strong>22.7. Specific Kernel Module Capabilities</a></li><li class="up"><a accesskey="u" href="#"><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>22.8. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Yum_Variables.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Yum_Variables.html
new file mode 100644
index 0000000..0dbcfc7
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Using_Yum_Variables.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>4.3.3. Yum 変数の使い方</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="4.3. Yum と Yum リポジトリーの設定" /><link rel="prev" href="sec-Setting_repository_Options.html" title="4.3.2. [repository] オプションの設定" /><link rel="next" href="sec-Viewing_the_Current_Configuration.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 accesske
y="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_Yum_Variables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.3. Yum 変数の使い方</h3></div></div></div><a id="idm59803680" class="indexterm"></a><div class="para">
+ <code class="command">yum</code> コマンドと Yum 設定ファイル（つまり、<code class="filename">/etc/yum.conf</code> および <code class="filename">/etc/yum.repos.d/</code> ディレクトリにあるすべての <code class="filename">.repo</code> ファイル）において以下の組み込み変数を使用および参照できます:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="varname">$releasever</code></span></dt><dd><div class="para">
+ Fedora のリリースバージョンを参照するためにこの変数を使用できます。Yum は <code class="filename">/etc/yum.conf</code> 設定ファイルの <code class="literal">distroverpkg=<em class="replaceable"><code>value</code></em></code> 行から <code class="varname">$releasever</code> の値を取得します。もし <code class="filename">/etc/yum.conf</code> にそのような行がなければ、<code class="command">yum</code> は <span class="package">redhat-release</span> パッケージからバージョン番号を取り出すことにより正しい値を推測します。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="varname">$arch</code></span></dt><dd><div class="para">
+ Python の <code class="methodname">os.uname()</code> 関数を呼び出すとき返されるように、システムの CPU アーキテクチャーを参照するためにこの値を使用できます。<code class="varname">$arch</code> の有効な値は次のとおりです: <code class="literal">i586</code>, <code class="literal">i686</code> および <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">
+ システムの基本アーキテクチャーを参照するために <code class="varname">$basearch</code> を使用できます。たとえば、i686 と i586 のマシンはどちらも <code class="literal">i386</code> の基本アーキテクチャーを持ちます。また、AMD64 と Intel64 のマシンは <code class="literal">x86_64</code> の基本アーキテクチャーを持ちます。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="varname">$YUM0-9</code></span></dt><dd><div class="para">
+ これらの10個の変数は、同じ名前のシェル環境変数の値でそれぞれ置き換えられます。これらの変数のどれかが（たとえば <code class="filename">/etc/yum.conf</code> において）参照され、同じ名前を持つシェル環境変数が存在しなければ、設定ファイルの変数は置き換えられません。
+ </div></dd></dl></div><div class="para">
+ 個別の変数を定義する、または既存のものの値を上書きするには、<code class="filename">/etc/yum/vars/</code> ディレクトリに、変数と同じ名前を持つファイルを（<span class="quote">「<span class="quote"><code class="literal">$</code></span>」</span> 記号なしで）作成します。そして、その最初の行に希望する値を追加します。
+ </div><div class="para">
+ たとえば、リポジトリ記述はしばしばオペレーティングシステム名を含みます。<code class="varname">$osname</code> という新しい変数を定義するには、最初の行に <span class="quote">「<span class="quote">Fedora</span>」</span> を持つ新しいファイルを作成して、<code class="filename">/etc/yum/vars/osname</code> として保存します:
+ </div><pre class="screen">~]# <code class="command">echo "Fedora" > /etc/yum/vars/os名</code></pre><div class="para">
+ <span class="quote">「<span class="quote">Fedora 17</span>」</span> の代わりに、<code class="filename">.repo</code> ファイルにおいて以下を使用することができます:
+ </div><pre class="programlisting">name=$osname $releasever</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_repository_Options.html"><strong>戻る</strong>4.3.2. [repository] オプションの設定</a></li><li class="up"><a accesskey="u" href="#"><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>4.3.4. 現在の設定の表示</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
new file mode 100644
index 0000000..a349d4e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 初期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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="第21章 カーネルをアップグレードする" /><link rel="prev" href="s1-kernel-perform-upgrade.html" title="21.4. アップグレードの実行" /><link rel="next" href="s1-kernel-boot-loader.html" title="21.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">21.5. 初期RAMディスクイメージの確認</h2></div></div></div><a id="idm32743088" 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 17 systems, whenever a new kernel is installed using either the <span class="application"><strong>Yum</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">21.5項「 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>手順21.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><pre class="screen">~]# <code class="command">ls /boot</code>
+config-3.1.0-0.rc6.git0.3.fc16.x86_64
+config-3.1.0-0.rc9.git0.0.fc16.x86_64
+elf-memtest86+-4.20
+grub
+grub2
+initramfs-3.1.0-0.rc6.git0.3.fc16.x86_64.img
+initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img
+initrd-plymouth.img
+memtest86+-4.20
+System.map-3.1.0-0.rc6.git0.3.fc16.x86_64
+System.map-3.1.0-0.rc9.git0.0.fc16.x86_64
+vmlinuz-3.1.0-0.rc6.git0.3.fc16.x86_64
+vmlinuz-3.1.0-0.rc9.git0.0.fc16.x86_64</pre><div class="para">
+ The example above shows that:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ we have two kernels installed (or, more correctly, two 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-vmlinuz-3.1.0-0.rc9.git0.0.fc16.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.1.0-0.rc9.git0.0.fc16.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 may 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>, refer to <a class="xref" href="ch-kdump.html">23章<em>The kdump Crash Recovery Service</em></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 may 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.1.0-0.rc9.git0.0.fc16.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.1.0-0.rc9.git0.0.fc16.x86_64.img</code>
+/boot/initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img: 16M
+========================================================================
+dracut-013-15.fc16
+========================================================================
+drwxr-xr-x 8 root root 0 Oct 11 20:36 .
+lrwxrwxrwx 1 root root 17 Oct 11 20:36 lib -> run/initramfs/lib
+drwxr-xr-x 2 root root 0 Oct 11 20:36 sys
+drwxr-xr-x 2 root root 0 Oct 11 20:36 proc
+lrwxrwxrwx 1 root root 17 Oct 11 20:36 etc -> run/initramfs/etc
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre><div class="para">
+ Refer to <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">initrd <code class="filename">/<em class="replaceable"><code>path</code></em>/initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code></code> exists for the kernel version you are booting. For example:
+ </div><pre class="screen">~]# <code class="command">grep initrd /boot/grub2/grub.cfg</code>
+ initrd /initramfs-3.1.0-0.rc6.git0.3.fc16.x86_64.img
+ initrd /initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img</pre><div class="para">
+ Refer to <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="idm48846496" 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>21.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>21.6. ブートローダの確認</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Viewing_the_Current_Configuration.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Viewing_the_Current_Configuration.html
new file mode 100644
index 0000000..23007a0
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Viewing_the_Current_Configuration.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="4.3. Yum と Yum リポジトリーの設定" /><link rel="prev" href="sec-Using_Yum_Variables.html" title="4.3.3. Yum 変数の使い方" /><link rel="next" href="sec-Managing_Yum_Repositories.html" title="4.3.5. Yum リポジトリの追加・有効化および無効化" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="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-Using_Yum_Variables.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Managing_Yum_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"><h3 class="title">4.3.4. 現在の設定の表示</h3></div></div></div><div class="para">
+ Yum の全体オプション（つまり、<code class="filename">/etc/yum.conf</code> ファイルの <code class="literal">[main]</code> セクションにおいて指定されているオプション）の現在の値を表示するには、コマンドラインのオプションなしで <code class="command">yum-config-manager</code> を実行します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code></pre><div class="para">
+ 異なる設定セクションの内容を一覧表示するには、以下の形式でコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <em class="replaceable"><code>section</code></em>…</pre><div class="para">
+ すべての一致するセクションの設定を表示するためにグロブ表現を使用することもできます:
+ </div><pre class="synopsis"><code class="command">yum-config-manager</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、すべての設定オプションとそれぞれ対応する値を一覧表示するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]$ <code class="command">yum-config-manager main \*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+================================== main ===================================
+[main]
+alwaysprompt = True
+assumeyes = False
+bandwith = 0
+bugtracker_url = https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%206&component=yum
+cache = 0
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Yum_Variables.html"><strong>戻る</strong>4.3.3. Yum 変数の使い方</a></li><li class="up"><a accesskey="u" href="#"><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_Yum_Repositories.html"><strong>次へ</strong>4.3.5. Yum リポジトリの追加・有効化および無効化</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Viewing_the_Transaction_Log.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Viewing_the_Transaction_Log.html
new file mode 100644
index 0000000..1a09eef
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Viewing_the_Transaction_Log.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>5.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Using_Add_Remove_Software.html" title="5.2. ソフトウェアの追加/削除の使用" /><link rel="prev" href="sec-Installing_and_Removing_Package_Groups.html" title="5.2.4. パッケージグループのインストールおよび削除" /><link rel="next" href="sec-PackageKit_Architecture.html" title="5.3. PackageKit アーキテクチャー" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><l
i class="previous"><a accesskey="p" href="sec-Installing_and_Removing_Package_Groups.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-PackageKit_Architecture.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Viewing_the_Transaction_Log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.5. トランザクションログの表示</h3></div></div></div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> は実行したトランザクションのログ
+ <a id="idm62197712" class="indexterm"></a>
+ <a id="idm62196304" class="indexterm"></a>
+ を維持します。ログを表示するには、<span class="guilabel"><strong>ソフトウェアの追加/削除</strong></span>ウィンドウから<span class="guimenu"><strong>システム</strong></span> → <span class="guimenuitem"><strong>ソフトウェアのログ</strong></span>をクリックします、またはシェルプロンプトにおいて <code class="command">gpk-log</code> コマンドを実行します。
+ </div><div class="para">
+ <span class="guilabel"><strong>ソフトウェア更新履歴ビューアー</strong></span>は、<code class="literal">更新されたパッケージ</code>や<code class="literal">インストール済みパッケージ</code>、アクションが実行された<span class="guilabel"><strong>日付</strong></span>、アクションを実行した<span class="guilabel"><strong>ユーザー名</strong></span>、およびユーザーが使用したフロントエンドの<span class="guilabel"><strong>アプリケーション</strong></span>（たとえば、<code class="literal">ソフトウェアの追加/削除</code>や<code class="literal">システムの更新</code>）のような<span class="guilabel"><strong>アクション</strong></span>を表示します。<span class="guilabel"><strong>詳細</strong></span>の列は、トランザクションが実行されたパッケージの一覧と同じように、<code class="literal">更新</code>、<code class="lite
ral">インストール</code>、または<code class="literal">削除</code>のような、トランザクションの種類を提供します。
+ </div><div class="figure" id="fig-Graphical_Package_Management-Software_Log_Viewer"><div class="figure-contents"><div class="mediaobject"><img src="images/add-remove-software-log.png" alt="ソフトウェアログビューアーを用いたパッケージ管理トランザクションのログの表示" /><div class="longdesc"><div class="para">
+ Viewing the log of package management transactions with PackageKit's Software Log Viewer window
+ </div></div></div></div><h6>図5.10 ソフトウェアログビューアーを用いたパッケージ管理トランザクションのログの表示</h6></div><br class="figure-break" /><div class="para">
+ 上部のテキスト入力フィールドにパッケージの名前を入力することにより、パッケージに影響するトランザクションの一覧をフィルターします。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Removing_Package_Groups.html"><strong>戻る</strong>5.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="sec-PackageKit_Architecture.html"><strong>次へ</strong>5.3. PackageKit アーキテクチャー</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Yum-Transaction_History.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Yum-Transaction_History.html
new file mode 100644
index 0000000..566c064
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Yum-Transaction_History.html
@@ -0,0 +1,221 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="4.2. パッケージとパッケージ グループ" /><link rel="prev" href="sec-Removing.html" title="4.2.5. パッケージの削除" /><link rel="next" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="4.3. Yum と Yum リポジトリーの設定" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-R
emoving.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Yum-Transaction_History"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.6. 処理とトランザクションの履歴</h3></div></div></div><div class="para">
+ <code class="command">yum history</code> コマンドにより、ユーザーが時系列の Yum トランザクション、それらが発生した日時、影響されたパッケージの数、トランザクションが成功したか中断されたかどうか、およびトランザクション中に RPM データベースが変更されたかどうか、に関する情報を確認できます。加えて、このコマンドは特定のトランザクションを元に戻したり、再実行したりするために使用できます。
+ </div><h4 id="bh-Yum-Transaction_History-Listing">トランザクションの一覧</h4><div class="para">
+ 最新のトランザクション20個の一覧を表示するには、<code class="systemitem">root</code>として、引数なしで <code class="command">yum history</code> を実行します、またはシェルプロンプトにおいて以下のように入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">list</code></pre><div class="para">
+ すべてのトランザクションを表示するには、<code class="literal">all</code> キーワードを追加します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">list</code> <code class="option">all</code></pre><div class="para">
+ 与えられた範囲にあるトランザクションのみを表示するには、以下の形式でコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">yum</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">
+ 特定のパッケージに関するトランザクションのみを一覧表示することもできます。そうするには、パッケージ名またはグロブ表現とともにコマンドを使用します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">list</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、以下のように最初の5トランザクションの一覧が表示されます:
+ </div><pre class="screen">~]# <code class="command">yum history list 1..5</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+ID | Login user | Date and time | Action(s) | Altered
+-------------------------------------------------------------------------------
+ 5 | Jaromir ... <jhradilek> | 2011-07-29 15:33 | Install | 1
+ 4 | Jaromir ... <jhradilek> | 2011-07-21 15:10 | Install | 1
+ 3 | Jaromir ... <jhradilek> | 2011-07-16 15:27 | I, U | 73
+ 2 | System <unset> | 2011-07-16 15:19 | Update | 1
+ 1 | System <unset> | 2011-07-16 14:38 | Install | 1106
+history list</pre><div class="para">
+ すべての形式の <code class="command">yum history list</code> コマンドは、以下の列から構成される各行をタブ区切りを生成します:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">ID</code> — 特定のトランザクションを識別する整数値です。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Login user</code> — トランザクションを初期化するために使用されたログインセッションのユーザー名です。この情報は一般的に<code class="computeroutput"><em class="replaceable"><code>Full Name</code></em> (完全名) <<em class="replaceable"><code>username</code></em> (ユーザー名) ></code> 形式で表現されます。（自動的なシステム更新のように）ユーザーにより発行されていないトランザクションは、<code class="computeroutput">System <unset></code> が代わりに使用されます。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Date and time</code> — トランザクションが発行された日付と時刻です。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Action(s)</code> — <a class="xref" href="sec-Yum-Transaction_History.html#tabl-Yum-Transaction_History-Actions">表4.1「Action(s) フィールドの取り得る値」</a>に説明されているように、トランザクション中に実行されたアクションの一覧です。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Altered</code> — トランザクションにより影響を受けるパッケージの数です。<a class="xref" href="sec-Yum-Transaction_History.html#tabl-Yum-Transaction_History-Altered">表4.2「Altered フィールドの利用可能な値」</a>に記載されているように追加の情報を続けることができます。
+ </div></li></ul></div><div class="table" id="tabl-Yum-Transaction_History-Actions"><h6>表4.1 Action(s) フィールドの取り得る値</h6><div class="table-contents"><table summary="Action(s) フィールドの取り得る値" border="1"><colgroup><col width="20%" class="Action" /><col width="15%" class="Abbreviation" /><col width="65%" class="Description" /></colgroup><thead><tr><th class="">
+ アクション
+ </th><th class="">
+ 略号
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="literal">Downgrade</code>
+ </td><td class="">
+ <code class="literal">D</code>
+ </td><td class="">
+ 少なくとも1つのパッケージが古いバージョンにダウングレードされました。
+ </td></tr><tr><td class="">
+ <code class="literal">Erase</code>
+ </td><td class="">
+ <code class="literal">E</code>
+ </td><td class="">
+ 少なくとも 1 つのパッケージが削除されました。
+ </td></tr><tr><td class="">
+ <code class="literal">インストール</code>
+ </td><td class="">
+ <code class="literal">I</code>
+ </td><td class="">
+ 少なくとも 1 つの新規パッケージがインストールされました。
+ </td></tr><tr><td class="">
+ <code class="literal">Obsoleting</code>
+ </td><td class="">
+ <code class="literal">O</code>
+ </td><td class="">
+ 少なくとも一つのパッケージに推奨されないという印がついています。
+ </td></tr><tr><td class="">
+ <code class="literal">再インストール</code>
+ </td><td class="">
+ <code class="literal">R</code>
+ </td><td class="">
+ 少なくとも 1 つのパッケージを再インストールしました。
+ </td></tr><tr><td class="">
+ <code class="literal">アップグレード</code>
+ </td><td class="">
+ <code class="literal">U</code>
+ </td><td class="">
+ 少なくとも 1 つのパッケージを新しいバージョンに更新しました。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table" id="tabl-Yum-Transaction_History-Altered"><h6>表4.2 Altered フィールドの利用可能な値</h6><div class="table-contents"><table summary="Altered フィールドの利用可能な値" border="1"><colgroup><col width="20%" class="Symbol" /><col width="80%" class="Description" /></colgroup><thead><tr><th class="">
+ シンボル
+ </th><th class="">
+ 説明
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="literal"><</code>
+ </td><td class="">
+ トランザクションの終了前で、データベース <code class="filename">rpmdb</code> が Yum 以外で変更されました。
+ </td></tr><tr><td class="">
+ <code class="literal">></code>
+ </td><td class="">
+ トランザクションの終了後、<code class="filename">rpmdb</code> データベースが Yum 以外で更新されました
+ </td></tr><tr><td class="">
+ <code class="literal">*</code>
+ </td><td class="">
+ トランザクションの終了に失敗しました。
+ </td></tr><tr><td class="">
+ <code class="literal">#</code>
+ </td><td class="">
+ トランザクションの実行に成功しましたが、<code class="command">yum</code> は 0 以外の終了コードを返しました。
+ </td></tr><tr><td class="">
+ <code class="literal">E</code>
+ </td><td class="">
+ トランザクションの終了に成功しましたが、エラーか警告が表示されました。
+ </td></tr><tr><td class="">
+ <code class="literal">P</code>
+ </td><td class="">
+ トランザクションが正常に終了しましたが、問題はすでに<code class="filename">rpmdb</code> データベースに存在しました。
+ </td></tr><tr><td class="">
+ <code class="literal">s</code>
+ </td><td class="">
+ トランザクションが正常に終了しました。ただし、<code class="option">--skip-broken</code> コマンドラインオプションが使用され、特定のパッケージがスキップされました。
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Yum は過去のトランザクションすべての概要を表示することもできます。そうするには、<code class="systemitem">root</code> として以下の形式でコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">summary</code></pre><div class="para">
+ 指定した範囲のトランザクションのみを表示するには、次のように入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">summary</code> <em class="replaceable"><code>start_id</code></em>..<em class="replaceable"><code>end_id</code></em></pre><div class="para">
+ <code class="command">yum history list</code> コマンドと同様に、パッケージ名またはグロブ表現を与えることにより特定のパッケージに関するトランザクションの概要を表示することもできます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">summary</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、上に表示されたトランザクション履歴の概要は以下にあるように見えます:
+ </div><pre class="screen">~]# <code class="command">yum history summary 1..5</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Login user | Time | Action(s) | Altered
+-------------------------------------------------------------------------------
+Jaromir ... <jhradilek> | Last day | Install | 1
+Jaromir ... <jhradilek> | Last week | Install | 1
+Jaromir ... <jhradilek> | Last 2 weeks | I, U | 73
+System <unset> | Last 2 weeks | I, U | 1107
+history summary</pre><div class="para">
+ すべての形式の <code class="command">yum history summary</code> コマンドは <code class="command">yum history list</code> の出力と似ているものを単純化されたタブ区切りの出力を生成します。
+ </div><div class="para">
+ 上で示したように、<code class="command">yum history list</code> と <code class="command">yum history summary</code> はどちらもトランザクション指向です。与えられたパッケージに関連するトランザクションのみを表示できますが、パッケージのバージョンのような重要な詳細が不足しています。パッケージの観点からトランザクションを一覧表示するには、以下のコマンドを <code class="systemitem">root</code> として実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">package-list</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
+ たとえば、<span class="package">subscription-manager</span> と関連するパッケージの履歴を追跡するには、シェルプロンプトにおいて以下のように入力します:
+ </div><pre class="screen">~]# <code class="command">yum history package-list subscription-manager\*</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+ID | Action(s) | Package
+-------------------------------------------------------------------------------
+ 3 | Updated | subscription-manager-0.95.11-1.el6.x86_64
+ 3 | Update | 0.95.17-1.el6_1.x86_64
+ 3 | Updated | subscription-manager-firstboot-0.95.11-1.el6.x86_64
+ 3 | Update | 0.95.17-1.el6_1.x86_64
+ 3 | Updated | subscription-manager-gnome-0.95.11-1.el6.x86_64
+ 3 | Update | 0.95.17-1.el6_1.x86_64
+ 1 | Install | subscription-manager-0.95.11-1.el6.x86_64
+ 1 | Install | subscription-manager-firstboot-0.95.11-1.el6.x86_64
+ 1 | Install | subscription-manager-gnome-0.95.11-1.el6.x86_64
+history package-list</pre><div class="para">
+ この例では、3つのパッケージがシステムの初期インストール中にインストールされました: <span class="package">subscription-manager</span>, <span class="package">subscription-manager-firstboot</span>, および <span class="package">subscription-manager-gnome</span>。3回目のトランザクションにおいて、すべてのパッケージがバージョン 0.95.11 からバージョン 0.95.17 に更新されました。
+ </div><h4 id="bh-Yum-Transaction_History-Examining">トランザクションの検証</h4><div class="para">
+ 単一のトランザクションの概要を表示するには、<code class="systemitem">root</code> として <code class="command">yum history summary</code> コマンドを以下の形式で使用します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">summary</code> <em class="replaceable"><code>id</code></em></pre><div class="para">
+ 特定のトランザクションを詳細に確認するには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">info</code> <em class="replaceable"><code>id</code></em>…</pre><div class="para">
+ <em class="replaceable"><code>id</code></em> 引数はオプションです。省略したとき、<code class="command">yum</code> は自動的に最後のトランザクションを使用します。複数のトランザクションを指定するときに、範囲を使用することもできることに注意してください:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">info</code> <em class="replaceable"><code>start_id</code></em>..<em class="replaceable"><code>end_id</code></em></pre><div class="para">
+ 以下は、2つのトランザクションのサンプル出力です。それぞれ新規パッケージを1つインストールしています:
+ </div><pre class="screen">~]# <code class="command">yum history info 4..5</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Transaction ID : 4..5
+Begin time : Thu Jul 21 15:10:46 2011
+Begin rpmdb : 1107:0c67c32219c199f92ed8da7572b4c6df64eacd3a
+End time : 15:33:15 2011 (22 minutes)
+End rpmdb : 1109:1171025bd9b6b5f8db30d063598f590f1c1f3242
+User : Jaromir Hradilek <jhradilek>
+Return-Code : Success
+Command Line : install screen
+Command Line : install yum-plugin-fs-snapshot
+Transaction performed with:
+ Installed rpm-4.8.0-16.el6.x86_64
+ Installed yum-3.2.29-17.el6.noarch
+ Installed yum-metadata-parser-1.1.2-16.el6.x86_64
+Packages Altered:
+ Install screen-4.0.3-16.el6.x86_64
+ Install yum-plugin-fs-snapshot-1.1.30-6.el6.noarch
+history info</pre><div class="para">
+ トランザクションを実行したときに使用された設定オプションや、どのリポジトリからパッケージがインストールされたか、特定のパッケージがなぜインストールされたか、などのような追加の情報を表示することもできます。特定のトランザクションに対してどの追加の情報が利用可能であるかを決めるには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">addon-info</code> <em class="replaceable"><code>id</code></em></pre><div class="para">
+ <code class="command">yum history info</code> と同様、<em class="replaceable"><code>id</code></em> を与えないとき、<code class="command">yum</code> は自動的に最後のトランザクションを使用します。最後のトランザクションを参照する別の方法は <code class="literal">last</code> キーワードを使用することです:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">addon-info</code> <code class="option">last</code></pre><div class="para">
+ たとえば、前の例にある最初のトランザクションに対して、<code class="command">yum history addon-info</code> コマンドは以下のように出力します:
+ </div><pre class="screen">~]# <code class="command">yum history addon-info 4</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+Transaction ID: 4
+Available additional history information:
+ config-main
+ config-repos
+ saved_tx
+
+history addon-info</pre><div class="para">
+ この例では、3種類の情報が利用可能です:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">config-main</code> — トランザクション中に使用される Yum 全体オプションです。全体オプションを変更する方法については<a class="xref" href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">「[main] オプションの設定」</a>を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">config-repos</code> — 各 Yum リポジトリーに対するオプションです。各リポジトリーに対するオプションを変更する方法については<a class="xref" href="sec-Setting_repository_Options.html">「[repository] オプションの設定」</a>を参照してください。
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">saved_tx</code> — 他のマシンにおいてトランザクションを繰り返すために <code class="command">yum load-transaction</code> コマンドにより使用できるデータです（以下、参照）。
+ </div></li></ul></div><div class="para">
+ 選択した形式の追加の情報を表示するには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">addon-info</code> <em class="replaceable"><code>id</code></em> <em class="replaceable"><code>information</code></em></pre><h4 id="bh-Yum-Transaction_History-Reverting">トランザクションの復帰および繰り返し</h4><div class="para">
+ トランザクション履歴の確認のほか、<code class="command">yum history</code> コマンドは選択したトランザクションの復帰および繰り返しをする手段を提供します。トランザクションを復帰するには、シェルプロンプトにおいて以下のコマンドを <code class="systemitem">root</code> として入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">undo</code> <em class="replaceable"><code>id</code></em></pre><div class="para">
+ 特定のトランザクションを繰り返すには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">redo</code> <em class="replaceable"><code>id</code></em></pre><div class="para">
+ どちらのコマンドも、最後に実行したトランザクションを取り消すまたは繰り返すために、<code class="literal">last</code> キーワードを受け付けます。
+ </div><div class="para">
+ <code class="command">yum history undo</code> と <code class="command">yum history redo</code> コマンドはどちらも単にトランザクション中に実行された手順を復帰または繰り返すだけであることに注意してください。トランザクションが新しいパッケージをインストールしているならば、<code class="command">yum history undo</code> コマンドはそれをアンインストールします。逆もまた同様です。可能ならば、このコマンドはすべての更新したパッケージをそれらの前のバージョンにダウングレードしようとしますが、これらの古いパッケージはもはや利用可能ではないかもしれません。もしシステムを更新前の状態に復元できる必要があるならば、<a class="xref" href="sec-Plugin_Descriptions.html">「プラグインの説明」</a>において説明されている <span class="application"><strong
>fs-snapshot</strong></span> プラグインの使用を検討してください。
+ </div><div class="para">
+ いくつかの同一システムを管理するとき、Yumはそのうちのどれか１つにおいてトランザクションを実行し、トランザクションの詳細をファイルに保存し、テスト後に同じトランザクションを残りのシステムにおいて同じように繰り返すこともできるようにします。トランザクションの詳細をファイルに保存するには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のように入力します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">-q</code> <code class="option">history</code> <code class="option">addon-info</code> <em class="replaceable"><code>id</code></em> <code class="option">saved_tx</code> > <code class="filename">file_name</code></pre><div class="para">
+ 一度このファイルを対象システムにコピーすると、<code class="systemitem">root</code> として以下のコマンドを使用することによりトランザクションを繰り返すことができます:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">load-transaction</code> <em class="replaceable"><code>file_name</code></em></pre><div class="para">
+ しかしながら、ファイルに保存されている <code class="literal">rpmdb</code> バージョンは対象システムにおけるバージョンと同一でなければいけません。<code class="command">yum version nogroups</code> コマンドを使用することにより <code class="literal">rpmdb</code> のバージョンを確認できます。
+ </div><h4 id="bh-Yum-Transaction_History-New">新規トランザクション履歴の開始</h4><div class="para">
+ Yum はトランザクション履歴を単独の SQLite データベースファイルに保存します。新規トランザクション履歴を開始するには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">new</code></pre><div class="para">
+ これにより、新しい空のデータベースファイルが <code class="filename">/var/lib/yum/history/</code> ディレクトリに作成されます。古いトランザクション履歴は保持されますが、新しいデータベースがディレクトリに存在する限りアクセスできません。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Removing.html"><strong>戻る</strong>4.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="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>次へ</strong>4.3. Yum と Yum リポジトリーの設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Yum_Plugins.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Yum_Plugins.html
new file mode 100644
index 0000000..4a14618
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-Yum_Plugins.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>4.4. Yum プラグイン</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-yum.html" title="第4章 Yum" /><link rel="prev" href="sec-Creating_a_Yum_Repository.html" title="4.3.6. Yum リポジトリーの作成" /><link rel="next" href="sec-Installing_More_Yum_Plugins.html" title="4.4.2. 追加の Yum プラグインのインストール" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Creating_a_Yum_Repository.html"><stron
g>戻る</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_More_Yum_Plugins.html"><strong>次へ</strong></a></li></ul><div class="section" id="sec-Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Yum プラグイン</h2></div></div></div><a id="idm50278640" class="indexterm"></a><div class="para">
+ Yum はその機能を拡張および向上させるプラグインを提供します。特定のプラグインはデフォルトでインストールされます。あらゆる <code class="command">yum</code> コマンドを呼び出すときは必ず、Yum はプラグインがあればどれが読み込まれて有効化されているかを必ず通知します。たとえば:
+ </div><pre class="screen">~]# <code class="command">yum info yum</code>
+ロードされたプラグイン: langpacks, presto, refresh-packagekit
+<em class="lineannotation"><span class="lineannotation">[出力の省略]</span></em></pre><div class="para">
+ <code class="command">Loaded plugins</code> に続くプラグイン名は <code class="option">--disableplugins=<em class="replaceable"><code>plugin_name</code></em></code> オプションに対して提供できる名前であることに注意してください。
+ </div><div class="section" id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.4.1. Yum プラグインの無効化、有効化、設定</h3></div></div></div><a id="idm55777840" class="indexterm"></a><a id="idm55776432" class="indexterm"></a><a id="idm55775024" class="indexterm"></a><div class="para">
+ Yum プラグインを有効にするには、<code class="filename">/etc/yum.conf</code> の <code class="literal">[main]</code> セクションに <code class="command">plugins=</code> で始まる行が存在して、その値が <code class="literal">1</code> に設定されていることを確実にします:
+ </div><pre class="programlisting">plugins=1</pre><div class="para">
+ この行を <code class="command">plugins=0</code> に変更することにより、すべてのプラグインを無効にできます。
+ </div><div class="important" id="important-Disabling_all_plugins_is_not_advised-plugins"><div class="admonition_header"><h2>すべてのプラグインを無効にすることは推奨されません</h2></div><div class="admonition"><div class="para">
+ あるプラグインは重要な <code class="command">Yum</code> サービスを提供するので、すべてのプラグインを無効にすることは推奨されません。プラグインを全体的に無効にすることは、便利なオプションとして提供され、一般的に <code class="command">Yum</code> に関する潜在的な問題を診断するときにのみ推奨されます。
+ </div></div></div><div class="para">
+ すべてのインストールされたプラグインは <code class="filename">/etc/yum/pluginconf.d/</code> ディレクトリに自身の設定ファイルを持ちます。これらのファイルにプラグイン固有のオプションを設定できます。たとえば、これは <span class="application"><strong>refresh-packagekit</strong></span> プラグインの <code class="filename">refresh-packagekit.conf</code> 設定ファイルです:
+ </div><pre class="programlisting">[main]
+enabled=1</pre><div class="para">
+ プラグインの設定ファイルは必ず <code class="literal">[main]</code> セクション（Yum の <code class="filename">/etc/yum.conf</code> ファイルと似ています）を含みます。<code class="command">yum</code> コマンドを実行するときにプラグインを有効にするかどうかを制御する <code class="literal">enabled=</code> オプションがあります（もしなければ置くことができます）。
+ </div><div class="para">
+ <code class="filename">/etc/yum.conf</code> において <code class="command">enabled=0</code> を設定することにより、すべてのプラグインを無効にしているならば、すべてのプラグインは各設定ファイルにおいて有効にしているかどうかによらず無効にされます。
+ </div><div class="para">
+ 単に1回の <code class="command">yum</code> コマンドのためにすべての Yum プラグインを無効にしたいならば、<code class="option">--noplugins</code> オプションを使用します。
+ </div><div class="para">
+ 1回の <code class="command">yum</code> コマンドのために1つかそれ以上の Yum プラグインを無効にしたいならば、コマンドに <code class="option">--disableplugin=<em class="replaceable"><code>plugin_name</code></em></code> オプションを追加します。たとえば、システムを更新中に <span class="application"><strong>presto</strong></span> プラグインを無効にするには、次のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">yum update --disableplugin=presto</code></pre><div class="para">
+ <code class="option">--disableplugin=</code> オプションに提供するプラグイン名は、すべての <code class="command">yum</code> コマンドの出力において <code class="command">Loaded plugins</code> 行に表示される名前と同じものです。複数のプラグインの名前をコンマで区切ることにより、それらを無効にできます。さらに、グロブ表現を使用することにより、複数のプラグイン名に一致されたり、長いものを省略したりできます:
+ </div><pre class="screen">~]# <code class="command">yum update --disableplugin=presto,refresh-pack*</code></pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_a_Yum_Repository.html"><strong>戻る</strong>4.3.6. Yum リポジトリーの作成</a></li><li class="up"><a accesskey="u" href="#"><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_More_Yum_Plugins.html"><strong>次へ</strong>4.4.2. 追加の Yum プラグインのインストール</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html
new file mode 100644
index 0000000..2aab6fe
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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>16.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sec-Printer_Configuration.html" title="16.3. プリンタの設定" /><link rel="prev" href="s1-printing-ipp-printer.html" title="16.3.5. IPP プリンタの追加" /><link rel="next" href="s1-printing-smb-printer.html" title="16.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">16.3.6. Adding an LPD/LPR Host or Printer</h3></div></div></div><a id="idm49354080" 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 hostname 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>図16.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. Refer to <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>16.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>16.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/17/html/System_Administrators_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html
new file mode 100644
index 0000000..502a524
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html
@@ -0,0 +1,114 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Configuring a Multihomed DHCP 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-DHCP_Servers.html" title="第11章 DHCP サーバー" /><link rel="prev" href="s1-dhcp-configuring-client.html" title="11.3. DHCP クライアントの設定" /><link rel="next" href="s1-dhcp_for_ipv6_dhcpv6.html" title="11.5. IPv6 向け DHCP (DHCPv6)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-dhcp-configuring-client.html"><strong>戻る</strong
></a></li><li class="next"><a accesskey="n" href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Configuring_a_Multihomed_DHCP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.4. Configuring a Multihomed DHCP Server</h2></div></div></div><a id="idm35018112" class="indexterm"></a><div class="para">
+ A multihomed DHCP server serves multiple networks, that is, multiple subnets. The examples in these sections detail how to configure a DHCP server to serve multiple networks, select which network interfaces to listen on, and how to define network settings for systems that move networks.
+ </div><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="para">
+ The DHCP daemon listens on all network interfaces unless otherwise specified. Use the <code class="filename">/etc/sysconfig/dhcpd</code> file to specify which network interfaces the DHCP daemon listens on. The following <code class="filename">/etc/sysconfig/dhcpd</code> example specifies that the DHCP daemon listens on the <code class="filename">eth0</code> and <code class="filename">eth1</code> interfaces:
+ </div><pre class="programlisting">DHCPDARGS="eth0 eth1";</pre><div class="para">
+ If a system has three network interfaces cards -- <code class="filename">eth0</code>, <code class="filename">eth1</code>, and <code class="filename">eth2</code> -- and it is only desired that the DHCP daemon listens on <code class="filename">eth0</code>, then only specify <code class="computeroutput">eth0</code> in <code class="filename">/etc/sysconfig/dhcpd</code>:
+ </div><pre class="programlisting">DHCPDARGS="eth0";</pre><div class="para">
+ The following is a basic <code class="filename">/etc/dhcp/dhcpd.conf</code> file, for a server that has two network interfaces, <code class="filename">eth0</code> in a 10.0.0.0/24 network, and <code class="filename">eth1</code> in a 172.16.0.0/24 network. Multiple <code class="computeroutput">subnet</code> declarations allow different settings to be defined for multiple networks:
+ </div><pre class="programlisting">default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="computeroutput">subnet <em class="replaceable"><code>10.0.0.0</code></em> netmask <em class="replaceable"><code>255.255.255.0</code></em>;</code></span></dt><dd><div class="para">
+ A <code class="computeroutput">subnet</code> declaration is required for every network your DHCP server is serving. Multiple subnets require multiple <code class="computeroutput">subnet</code> declarations. If the DHCP server does not have a network interface in a range of a <code class="computeroutput">subnet</code> declaration, the DHCP server does not serve that network.
+ </div><div class="para">
+ If there is only one <code class="computeroutput">subnet</code> declaration, and no network interfaces are in the range of that subnet, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">dhcpd: No subnet declaration for eth0 (0.0.0.0).
+dhcpd: ** Ignoring requests on eth0. If this is not what
+dhcpd: you want, please write a subnet declaration
+dhcpd: in your dhcpd.conf file for the network segment
+dhcpd: to which interface eth1 is attached. **
+dhcpd:
+dhcpd:
+dhcpd: Not configured to listen on any interfaces!</pre></dd><dt class="varlistentry"><span class="term"><code class="computeroutput">option subnet-mask <em class="replaceable"><code>255.255.255.0</code></em>;</code></span></dt><dd><div class="para">
+ <code class="computeroutput">option subnet-mask</code> オプションはサブネットマスクを定義します。<code class="computeroutput">subnet</code> 宣言における <code class="computeroutput">netmask</code> 値を上書きします。簡単な例では、サブネットとネットマスクの値は同じです。
+ </div></dd><dt class="varlistentry"><span class="term"><code class="computeroutput">option routers <em class="replaceable"><code>10.0.0.1</code></em>;</code></span></dt><dd><div class="para">
+ The <code class="computeroutput">option routers</code> option defines the default gateway for the subnet. This is required for systems to reach internal networks on a different subnet, as well as external networks.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="computeroutput">range <em class="replaceable"><code>10.0.0.5</code></em> <em class="replaceable"><code>10.0.0.15</code></em>;</code></span></dt><dd><div class="para">
+ <code class="computeroutput">range</code> オプションは利用可能な IP アドレスのプールを指定します。システムは指定された IP アドレスの範囲からアドレスを割り当てられます。
+ </div></dd></dl></div><div class="para">
+ 詳細は <code class="computeroutput">dhcpd.conf(5)</code> マニュアルページを参照してください。
+ </div><div class="warning"><div class="admonition_header"><h2>エイリアス・インターフェースを使用しないでください</h2></div><div class="admonition"><div class="para">
+ エイリアス・インターフェースは DHCP によりサポートされません。エイリアス・インターフェースが <code class="filename">/etc/dhcp/dhcpd.conf</code> において指定されている唯一のサブネットにおける唯一のインターフェースならば、DHCP デーモンは開始に失敗します。
+ </div></div></div><div class="section" id="sect-dns_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.4.1. ホストの設定</h3></div></div></div><a id="idm29618144" class="indexterm"></a><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm73416800">Configuring a single system for multiple networks</h5>
+ 以下の <code class="filename">/etc/dhcp/dhcpd.conf</code> の例は2つのサブネットを作成し、接続しているネットワークに応じて同じシステムに対する IP アドレスを設定します。
+ </div><pre class="programlisting">default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}
+host example0 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 10.0.0.20;
+}
+host example1 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 172.16.0.20;
+}</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="computeroutput">host <em class="replaceable"><code>example0</code></em> </code></span></dt><dd><div class="para">
+ The <code class="computeroutput">host</code> declaration defines specific parameters for a single system, such as an IP address. To configure specific parameters for multiple hosts, use multiple <code class="computeroutput">host</code> declarations.
+ </div><div class="para">
+ Most DHCP clients ignore the name in <code class="computeroutput">host</code> declarations, and as such, this name can anything, as long as it is unique to other <code class="computeroutput">host</code> declarations. To configure the same system for multiple networks, use a different name for each <code class="computeroutput">host</code> declaration, otherwise the DHCP daemon fails to start. Systems are identified by the <code class="computeroutput">hardware ethernet</code> option, not the name in the <code class="computeroutput">host</code> declaration.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">hardware ethernet <em class="replaceable"><code>00:1A:6B:6A:2E:0B</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">hardware ethernet</code> option identifies the system. To find this address, run the <code class="command">ip link</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="computeroutput">fixed-address <em class="replaceable"><code>10.0.0.20</code></em>;</code></span></dt><dd><div class="para">
+ The <code class="computeroutput">fixed-address</code> option assigns a valid IP address to the system specified by the <code class="computeroutput">hardware ethernet</code> option. This address must be outside the IP address pool specified with the <code class="computeroutput">range</code> option.
+ </div></dd></dl></div><div class="para">
+ If <code class="computeroutput">option</code> statements do not end with a semicolon, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">/etc/dhcp/dhcpd.conf line 20: semicolon expected.
+dhcpd: }
+dhcpd: ^
+dhcpd: /etc/dhcp/dhcpd.conf line 38: unexpected end of file
+dhcpd:
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting</pre><div class="formalpara"><h5 class="formalpara" id="idm56687664">複数のネットワークインターフェースを持つシステムの設定</h5>
+ The following <code class="computeroutput">host</code> declarations configure a single system, that has multiple network interfaces, so that each interface receives the same IP address. This configuration will not work if both network interfaces are connected to the same network at the same time:
+ </div><pre class="programlisting">host interface0 {
+ hardware ethernet 00:1a:6b:6a:2e:0b;
+ fixed-address 10.0.0.18;
+}
+host interface1 {
+ hardware ethernet 00:1A:6B:6A:27:3A;
+ fixed-address 10.0.0.18;
+}</pre><div class="para">
+ For this example, <code class="computeroutput">interface0</code> is the first network interface, and <code class="computeroutput">interface1</code> is the second interface. The different <code class="computeroutput">hardware ethernet</code> options identify each interface.
+ </div><div class="para">
+ If such a system connects to another network, add more <code class="computeroutput">host</code> declarations, remembering to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ assign a valid <code class="computeroutput">fixed-address</code> for the network the host is connecting to.
+ </div></li><li class="listitem"><div class="para">
+ make the name in the <code class="computeroutput">host</code> declaration unique.
+ </div></li></ul></div><div class="para">
+ When a name given in a <code class="computeroutput">host</code> declaration is not unique, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">dhcpd: /etc/dhcp/dhcpd.conf line 31: host interface0: already exists
+dhcpd: }
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting</pre><div class="para">
+ This error was caused by having multiple <code class="computeroutput">host interface0</code> declarations defined in <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-configuring-client.html"><strong>戻る</strong>11.3. DHCP クライアントの設定</a></li><li class="up"><a accesskey="u" href="#"><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-dhcp_for_ipv6_dhcpv6.html"><strong>次へ</strong>11.5. IPv6 向け DHCP (DHCPv6)</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Additional_Resources.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Additional_Resources.html
new file mode 100644
index 0000000..78605af
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Configuring_the_Date_and_Time.html" title="第2章 日付と時刻の設定" /><link rel="prev" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html" title="2.2.3. Network Time Protocol の設定" /><link rel="next" href="ch-Managing_Users_and_Groups.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="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.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-Configuring_the_Date_and_Time-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. その他のリソース</h2></div></div></div><div class="para">
+ 日付と時刻の設定に関する詳細は、以下のリソースを参照してください。
+ </div><div class="section" id="sect-Configuring_the_Date_and_Time-Additional_Resources-Installed_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.1. インストールされているドキュメント</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">date</code>(1) — <span class="application"><strong>date</strong></span> ユーティリティのマニュアルページです。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">ntpdate</code>(8) — <span class="application"><strong>ntpdate</strong></span> ユーティリティのマニュアルページです。
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">ntpd</code>(8) — <code class="systemitem">ntpd</code> サービスのマニュアルページです。
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html"><strong>戻る</strong>2.2.3. Network Time Protocol の設定</a></li><li class="up"><a accesskey="u" href="#"><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>第3章 ユーザーとグループの管理</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html
new file mode 100644
index 0000000..2d28bd9
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.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>2.2.3. Network Time Protocol の設定</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html" title="2.2. コマンドラインツールの使用" /><link rel="prev" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html" title="2.2.2. 時刻の変更方法" /><link rel="next" href="sect-Configuring_the_Date_and_Time-Additional_Resources.html" title="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="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_the_Date_and_Time-Additional_Resources.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.3. Network Time Protocol の設定</h3></div></div></div><a id="idm60345664" class="indexterm"></a><a id="idm60344224" class="indexterm"></a><a id="idm60343264" class="indexterm"></a><a id="idm36761616" class="indexterm"></a><div class="para">
+ 上述の手動セットアップと対照的に、Network Time Protocol (<acronym class="acronym">NTP</acronym>) を通してリモートサーバーとシステムクロックを同期することもできます。一度だけの同期には、<span class="application"><strong>ntpdate</strong></span> コマンドを使用します:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ 以下の形式で <code class="command">ntpdate</code> を使用することにより、選択した NTP サーバーがアクセス可能であるかを確認します:
+ </div><pre class="screen"><code class="command">ntpdate -q <em class="replaceable"><code>server_address</code></em></code></pre><div class="para">
+ たとえば、<code class="systemitem">0.fedora.pool.ntp.org</code> に接続するには、次のとおり入力します:
+ </div><pre class="screen">~]$ <code class="command">ntpdate -q 0.fedora.pool.ntp.org</code>
+server 204.15.208.61, stratum 2, offset -39.275438, delay 0.16083
+server 69.65.40.29, stratum 2, offset -39.269122, delay 0.17191
+server 148.167.132.201, stratum 2, offset -39.270239, delay 0.20482
+17 Oct 17:41:09 ntpdate[10619]: step time server 204.15.208.61 offset -39.275438 sec</pre></li><li class="step"><div class="para">
+ 良好なサーバーを検索するとき、<code class="systemitem">root</code> として、1つ以上のサーバーアドレスを引数として <span class="application"><strong>ntpdate</strong></span> コマンドを実行してください:
+ </div><pre class="screen"><code class="command">ntpdate <em class="replaceable"><code>server_address…</code></em></code></pre><div class="para">
+ たとえば:
+ </div><pre class="screen">~]# <code class="command">ntpdate 0.fedora.pool.ntp.org 1.fedora.pool.ntp.org</code>
+17 Oct 17:42:13 ntpdate[10669]: step time server 204.15.208.61 offset -39.275436 sec</pre><div class="para">
+ エラーメッセージが何も表示されなければ、システム時刻が設定されます。<code class="command">date</code> コマンドを引数なしで実行することにより現在の時刻を確認できます。
+ </div></li><li class="step"><div class="para">
+ 大抵の場合、これらの手順で十分です。1つ以上のサービスが常に現在の時刻を使用する必要が本当にあるならば、<code class="systemitem">root</code> として以下のコマンドを実行することにより、起動時に <span class="application"><strong>ntpdate</strong></span> を実行するようにします:
+ </div><pre class="screen"><code class="command">systemctl enable ntpdate.service</code></pre><div class="para">
+ システムサービスとそのセットアップに関する詳細は、<a class="xref" href="ch-Services_and_Daemons.html">8章<em>サービスおよびデーモン</em></a>を参照してください。
+ </div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
+ 起動時に時刻サーバーと同期を続けることに失敗するならば、関連するエラーメッセージを <code class="filename">/var/log/boot.log</code> において確認できます。以下の行を <code class="filename">/etc/sysconfig/network</code> に追加してみてください:
+ </div><pre class="screen">NETWORKWAIT=1</pre></div></div></li></ol></div><a id="idm39577664" class="indexterm"></a><a id="idm39576224" class="indexterm"></a><a id="idm72956656" class="indexterm"></a><a id="idm72955056" class="indexterm"></a><div class="para">
+ しかしながら、起動時に時刻を自動的に同期されるためのより便利な方法は <code class="systemitem">ntpd</code> デーモンを設定することです:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ <code class="systemitem">root</code> として、NTP 設定ファイル <code class="filename">/etc/ntp.conf</code> をテキストエディターで開きます。もしまだ存在しなければ、新しいものを作成します。
+ </div></li><li class="step"><div class="para">
+ 公開されている NTP サーバーの一覧を追加または編集します。Fedora 17 を使用しているならば、すでに以下の行が含まれているファイルが存在しますが、必要に応じてこれらを気軽に変更や拡張してください:
+ </div><pre class="screen">server 0.fedora.pool.ntp.org iburst
+server 1.fedora.pool.ntp.org iburst
+server 2.fedora.pool.ntp.org iburst</pre><div class="note"><div class="admonition_header"><h2>初期同期の高速化</h2></div><div class="admonition"><div class="para">
+ 初期同期を高速化するには、<code class="command">iburst</code> ディレクティブを各サーバー設定行の最後に加えることが推奨されます。
+ </div></div></div></li><li class="step"><div class="para">
+ 同じファイルにおいて、適切なパーミッションを設定して、localhost のみにアクセスを制限します:
+ </div><pre class="screen">restrict default kod nomodify notrap nopeer noquery
+restrict -6 default kod nomodify notrap nopeer noquery
+restrict 127.0.0.1
+restrict -6 ::1</pre></li><li class="step"><div class="para">
+ 変更を保存して、エディタを終了して、NTP デーモンを再起動します:
+ </div><pre class="screen"><code class="command">systemctl restart ntpd.service</code></pre></li><li class="step"><div class="para">
+ 加えて、<code class="command">ntpd</code> デーモンがブート時に起動することを確実にします:
+ </div><pre class="screen"><code class="command">systemctl enable ntpd.service</code></pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html"><strong>戻る</strong>2.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="sect-Configuring_the_Date_and_Time-Additional_Resources.html"><strong>次へ</strong>2.3. その他のリソース</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html
new file mode 100644
index 0000000..01273c5
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration-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>2.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html" title="2.2. コマンドラインツールの使用" /><link rel="prev" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html" title="2.2. コマンドラインツールの使用" /><link rel="next" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html" title="2.2.3. Network Time Protocol の設定" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/image
s/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.2. 時刻の変更方法</h3></div></div></div><div class="para">
+ 現在の時刻を変更するには、<code class="systemitem">root</code> として以下のコマンドを実行します:
+ </div><pre class="screen"><code class="command">date +%T -s <em class="replaceable"><code>HH:MM:SS</code></em></code></pre><div class="para">
+ …ここで <em class="replaceable"><code>HH</code></em> は時間を意味して、<em class="replaceable"><code>MM</code></em> は時間、<em class="replaceable"><code>SS</code></em> は秒です。システムクロックが <acronym class="acronym">UTC</acronym> (Coordinated Universal Time) を使用するよう設定されているならば、以下のオプションも追加してください:
+ </div><pre class="screen"><code class="command">date +%T -s <em class="replaceable"><code>HH:MM:SS</code></em> -u</code></pre><div class="para">
+ たとえば、システムクロックを <acronym class="acronym">UTC</acronym> を使用して 11:26 PM に設定するには、次のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">date +%T -s 23:26:00 -u</code></pre><div class="para">
+ 何も引数をつけずに <code class="command">date</code> を実行することにより現在の設定を確認できます。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html"><strong>戻る</strong>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="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Network_Time_Protocol.html"><strong>次へ</strong>2.2.3. Network Time Protocol の設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration.html
new file mode 100644
index 0000000..781af61
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-Command_Line_Configuration.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Configuring_the_Date_and_Time.html" title="第2章 日付と時刻の設定" /><link rel="prev" href="ch-Configuring_the_Date_and_Time.html" title="第2章 日付と時刻の設定" /><link rel="next" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html" title="2.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-Configuring_the_Date_and_Time.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Configuring_the_Date_and_Time-Command_Line_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. コマンドラインツールの使用</h2></div></div></div><div class="para">
+ Fedora 17 は、手動または NTP プロトコルを用いて日付と時刻を設定できるコマンドラインツールを提供しています。
+ </div><div class="section" id="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Date"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.1. 日付の変更方法</h3></div></div></div><a id="idm55489648" class="indexterm"></a><a id="idm55488688" class="indexterm"></a><div class="para">
+ システムの日付を変更するには、シェルプロンプトにおいて <code class="systemitem">root</code> として以下のとおり入力します:
+ </div><pre class="screen"><code class="command">date +%D -s <em class="replaceable"><code>YYYY-MM-DD</code></em></code></pre><div class="para">
+ …ここで <em class="replaceable"><code>YYYY</code></em> は4桁の年、<em class="replaceable"><code>MM</code></em> は2桁の月、<em class="replaceable"><code>DD</code></em> は2桁の日です。たとえば、日付を2010年6月2日に変更するには、次のとおり入力します:
+ </div><pre class="screen">~]# <code class="command">date +%D -s 2010-06-02</code></pre><div class="para">
+ 何も引数をつけずに <code class="command">date</code> を実行することにより現在の設定を確認できます。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configuring_the_Date_and_Time.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="sect-Configuring_the_Date_and_Time-Command_Line_Configuration-Time.html"><strong>次へ</strong>2.2.2. 時刻の変更方法</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-Formats.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-Formats.html
new file mode 100644
index 0000000..e8f7f3d
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-Formats.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>1.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Configuring_the_Language_and_Keyboard.html" title="第1章 言語とキーボードの設定" /><link rel="prev" href="ch-Configuring_the_Language_and_Keyboard.html" title="第1章 言語とキーボードの設定" /><link rel="next" href="sect-Configuring_the_Language_and_Keyboard-Layouts.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"><l
i class="previous"><a accesskey="p" href="ch-Configuring_the_Language_and_Keyboard.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_the_Language_and_Keyboard-Layouts.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Configuring_the_Language_and_Keyboard-Formats"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.2. 日付、時刻および数字の形式の変更</h2></div></div></div><a id="idm59546016" class="indexterm"></a><div class="para">
+ デフォルトの日付、時刻、および通貨のフォーマットを変更するには、<span class="application"><strong>地域と言語</strong></span>アプリケーションの<span class="guilabel"><strong>フォーマット</strong></span>タブを選択します。利用可能なフォーマットの簡単な一覧が表示されます。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Formats"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-formats.png" alt="日付、時刻および数字の形式の変更" /><div class="longdesc"><div class="para">
+ 日付、時刻および数字の形式の変更
+ </div></div></div></div><h6>図1.3 日付、時刻および数字の形式の変更</h6></div><br class="figure-break" /><div class="para">
+ デフォルトで、このリストはいくつかの利用可能なフォーマットのみを含みます。他のフォーマットを追加するには、リストの下にある <span class="guibutton"><strong>+</strong></span> (プラス記号) ボタンをクリックします。ダイアログウィンドウが表示され、地域により希望するフォーマットを選択できます。ダイアログウィンドウの下部にある入力フィールドを使用して、そこに地域名の最初の数文字を入力すると表示される言語を減らすことができるようになります（たとえば、スロバキアには <span class="quote">「<span class="quote">slov</span>」</span> です）。言語を選択すると、選んだものを確認するために<span class="guibutton"><strong>選択</strong></span>ボタンをクリックします。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Formats-Add"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-formats-add.png" alt="フォーマットの追加" /><div class="longdesc"><div class="para">
+ フォーマットの追加
+ </div></div></div></div><h6>図1.4 フォーマットの追加</h6></div><br class="figure-break" /><div class="para">
+ 一覧の中から特定のフォーマットを選択するには、その名前をクリックします。変更は次回ログイン時に有効になります。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configuring_the_Language_and_Keyboard.html"><strong>戻る</strong>第1章 言語とキーボードの設定</a></li><li class="up"><a accesskey="u" href="#"><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_Language_and_Keyboard-Layouts.html"><strong>次へ</strong>1.3. キーボードのレイアウト変更</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-Layouts.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-Layouts.html
new file mode 100644
index 0000000..65cd479
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-Layouts.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. キーボードのレイアウト変更</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Configuring_the_Language_and_Keyboard.html" title="第1章 言語とキーボードの設定" /><link rel="prev" href="sect-Configuring_the_Language_and_Keyboard-Formats.html" title="1.2. 日付、時刻および数字の形式の変更" /><link rel="next" href="sect-Configuring_the_Language_and_Keyboard-System.html" title="1.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="docn
av"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Language_and_Keyboard-Formats.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_the_Language_and_Keyboard-System.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Configuring_the_Language_and_Keyboard-Layouts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.3. キーボードのレイアウト変更</h2></div></div></div><a id="idm45520000" class="indexterm"></a><a id="idm45518432" class="indexterm"></a><div class="para">
+ システム管理者がインストール中にインストールプログラムによりキーボード配置を設定できるにも関わらず、デフォルトの設定は現在の要望に対して常に適切ではないかもしれません。デフォルトのキーボードレイアウトを変更するには、<span class="application"><strong>地域と言語</strong></span>アプリケーションの<span class="application"><strong>レイアウト</strong></span>タブを選択します。現在有効なレイアウトの一覧が表示されます。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Layouts"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-layouts.png" alt="キーボードのレイアウトの変更" /><div class="longdesc"><div class="para">
+ キーボードのレイアウトの変更
+ </div></div></div></div><h6>図1.5 キーボードのレイアウトの変更</h6></div><br class="figure-break" /><div class="para">
+ 他のレイアウトを一覧に追加するには、リストの下にある <span class="guibutton"><strong>+</strong></span> (プラス記号) ボタンをクリックします。ダイアログウィンドウが表示され、希望するレイアウトを選択できます。ダイアログウィンドウの下部にある入力フィールドを使用して、そこにレイアウト名の最初の数文字を入力すると表示される言語を減らすことができるようになります（たとえば、スロバキアのレイアウトには <span class="quote">「<span class="quote">slov</span>」</span> です）。言語を選択すると、選んだものを確認するために<span class="guibutton"><strong>追加</strong></span>ボタンをクリックします。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-Layouts-Add"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-layouts-add.png" alt="キーボードのレイアウトの追加" /><div class="longdesc"><div class="para">
+ キーボードのレイアウトの追加
+ </div></div></div></div><h6>図1.6 キーボードのレイアウトの追加</h6></div><br class="figure-break" /><div class="para">
+ 一覧の最初にあるレイアウトが常にデフォルトと考えられます。特定のレイアウトを一覧において上下させるには、それを選択して、それぞれ <span class="guibutton"><strong>∧</strong></span> (上矢印) または <span class="guibutton"><strong>∨</strong></span> (下矢印) ボタンをクリックします。レイアウトを削除するには、 <span class="guibutton"><strong>−</strong></span> (マイナス記号) ボタンをクリックします。さらに、ウィンドウの右側にあるオプションボタンを選択することにより、個々のウィンドウに対して異なるキーボード配置を使用するか、すべてのウィンドウに対して一つのレイアウトを使用するかを選択できます。
+ </div><div class="para">
+ 複数のレイアウトを有効にしているとき、レイアウトを切り替えられるよう、パネルにキーボードインジケーターが表示されます。
+ </div><div class="figure" id="fig-keyboard-layouts-indicator"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-layouts-indicator.png" alt="キーボードのレイアウトのインジケーター" /><div class="longdesc"><div class="para">
+ キーボードのレイアウトのインジケーター
+ </div></div></div></div><h6>図1.7 キーボードのレイアウトのインジケーター</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Language_and_Keyboard-Formats.html"><strong>戻る</strong>1.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="sect-Configuring_the_Language_and_Keyboard-System.html"><strong>次へ</strong>1.4. 現在の設定の表示</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-System.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-System.html
new file mode 100644
index 0000000..1ad789f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Configuring_the_Language_and_Keyboard-System.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>1.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Configuring_the_Language_and_Keyboard.html" title="第1章 言語とキーボードの設定" /><link rel="prev" href="sect-Configuring_the_Language_and_Keyboard-Layouts.html" title="1.3. キーボードのレイアウト変更" /><link rel="next" href="ch-Configuring_the_Date_and_Time.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="sect-Configuring_the_Language_and_Keyboard-Layouts.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-Configuring_the_Language_and_Keyboard-System"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.4. 現在の設定の表示</h2></div></div></div><a id="idm69554768" class="indexterm"></a><div class="para">
+ 現在の設定を表示するには、<span class="application"><strong>地域と言語</strong></span>アプリケーションの<span class="guilabel"><strong>システム</strong></span>タブを選択します。あなた自身の設定とシステム全体の設定の比較が表示されます。
+ </div><div class="figure" id="fig-Configuring_the_Language_and_Keyboard-System"><div class="figure-contents"><div class="mediaobject"><img src="images/region-and-language-system.png" alt="現在の設定の表示" /><div class="longdesc"><div class="para">
+ 現在の設定の表示
+ </div></div></div></div><h6>図1.8 現在の設定の表示</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_the_Language_and_Keyboard-Layouts.html"><strong>戻る</strong>1.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-Configuring_the_Date_and_Time.html"><strong>次へ</strong>第2章 日付と時刻の設定</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-Enabling_and_Disabling.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-Enabling_and_Disabling.html
new file mode 100644
index 0000000..d075596
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-Enabling_and_Disabling.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.3. Enabling and Disabling the Feature</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="appe-Consistent_Network_Device_Naming.html" title="付録A Consistent Network Device Naming" /><link rel="prev" href="sect-Consistent_Network_Device_Naming-System_Requirements.html" title="A.2. システム要求" /><link rel="next" href="sect-Consistent_Network_Device_Naming-Notes.html" title="A.4. Notes for Administrators" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="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-Consistent_Network_Device_Naming-System_Requirements.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Consistent_Network_Device_Naming-Notes.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Consistent_Network_Device_Naming-Enabling_and_Disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.3. Enabling and Disabling the Feature</h2></div></div></div><div class="para">
+ To disable the consistent network device naming on Dell systems that would normally have it on by default, pass the following option on the boot command line, both during and after installation:
+ </div><pre class="screen"><code class="option">biosdevname=0</code></pre><div class="para">
+ To enable this feature on other system types that meet the minimum requirements (see <a class="xref" href="sect-Consistent_Network_Device_Naming-System_Requirements.html">「システム要求」</a>), pass the following option on the boot command line, both during and after installation:
+ </div><pre class="screen"><code class="option">biosdevname=1</code></pre><div class="para">
+ Unless the system meets the minimum requirements, this option will be ignored and the system will boot with the traditional network interface name format.
+ </div><div class="para">
+ If the <code class="option">biosdevname</code> install option is specified, it must remain as a boot option for the lifetime of the system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Consistent_Network_Device_Naming-System_Requirements.html"><strong>戻る</strong>A.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="sect-Consistent_Network_Device_Naming-Notes.html"><strong>次へ</strong>A.4. Notes for Administrators</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-Notes.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-Notes.html
new file mode 100644
index 0000000..69b2685
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-Notes.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>A.4. Notes for Administrators</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="appe-Consistent_Network_Device_Naming.html" title="付録A Consistent Network Device Naming" /><link rel="prev" href="sect-Consistent_Network_Device_Naming-Enabling_and_Disabling.html" title="A.3. Enabling and Disabling the Feature" /><link rel="next" href="ch-RPM.html" title="付録B 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-Consistent_Netwo
rk_Device_Naming-Enabling_and_Disabling.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ch-RPM.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Consistent_Network_Device_Naming-Notes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.4. Notes for Administrators</h2></div></div></div><div class="para">
+ Many system customization files can include network interface names, and thus will require updates if moving a system from the old convention to the new convention. If you use the new naming convention, you will also need to update network interface names in areas such as custom iptables rules, scripts altering irqbalance, and other similar configuration files. Also, enabling this change for installation will require modification to existing kickstart files that use device names via the <code class="option">ksdevice</code> parameter; these kickstart files will need to be updated to use the network device's MAC address or the network device's new name.
+ </div><div class="para">
+ The Fedora Project strongly recommends that you consider this feature to be an install-time choice; enabling or disabling the feature post-install, while technically possible, can be complicated and is not recommended. For those system administrators who wish to do so, on a system that meets the minimum requirements, remove the <code class="filename">/etc/udev/rules.d/70-persistent-net.rules</code> file and the <code class="option">HWADDR</code> lines from all <code class="filename">/etc/sysconfig/network-scripts/ifcfg-*</code> files. In addition, rename those <code class="filename">ifcfg-*</code> files to use this new naming convention. The new names will be in effect after reboot. Remember to update any custom scripts, iptables rules, and service configuration files that might include network interface names.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Consistent_Network_Device_Naming-Enabling_and_Disabling.html"><strong>戻る</strong>A.3. Enabling and Disabling the Feature</a></li><li class="up"><a accesskey="u" href="#"><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>付録B RPM</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-System_Requirements.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-System_Requirements.html
new file mode 100644
index 0000000..4dc9c0a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Consistent_Network_Device_Naming-System_Requirements.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>A.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="appe-Consistent_Network_Device_Naming.html" title="付録A Consistent Network Device Naming" /><link rel="prev" href="appe-Consistent_Network_Device_Naming.html" title="付録A Consistent Network Device Naming" /><link rel="next" href="sect-Consistent_Network_Device_Naming-Enabling_and_Disabling.html" title="A.3. Enabling and Disabling the Feature" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li c
lass="previous"><a accesskey="p" href="appe-Consistent_Network_Device_Naming.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Consistent_Network_Device_Naming-Enabling_and_Disabling.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Consistent_Network_Device_Naming-System_Requirements"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.2. システム要求</h2></div></div></div><div class="para">
+ The <span class="application"><strong>biosdevname</strong></span> program uses information from the system's BIOS, specifically the <span class="emphasis"><em>type 9</em></span> (System Slot) and <span class="emphasis"><em>type 41</em></span> (Onboard Devices Extended Information) fields contained within the SMBIOS. If the system's BIOS does not have SMBIOS version 2.6 or higher and this data, the new naming convention will not be used. Most older hardware does not support this feature because of a lack of BIOSes with the correct SMBIOS version and field information. For BIOS or SMBIOS version information, contact your hardware vendor.
+ </div><div class="para">
+ For this feature to take effect, the <span class="package">biosdevname</span> package must also be installed. The <span class="package">biosdevname</span> package is part of the <code class="literal">base</code> package group in Fedora 17. All install options, except for <span class="guimenuitem"><strong>Minimal Install</strong></span>, include this package.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Consistent_Network_Device_Naming.html"><strong>戻る</strong>付録A Consistent Network Device Naming</a></li><li class="up"><a accesskey="u" href="#"><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-Consistent_Network_Device_Naming-Enabling_and_Disabling.html"><strong>次へ</strong>A.3. Enabling and Disabling the Feature</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html
new file mode 100644
index 0000000..86a81ea
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.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>3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sect-Managing_Users_and_Groups-User_Accounts.html" title="3.2. ユーザー アカウントのツールを使う" /><link rel="prev" href="sect-Managing_Users_and_Groups-User_Accounts.html" title="3.2. ユーザー アカウントのツールを使う" /><link rel="next" href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html" title="3.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="sect-Managing_Users_and_Groups-User_Accounts.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.2. 新規ユーザーを追加する</h3></div></div></div><a id="idm60360480" class="indexterm"></a><div class="para">
+ 新しいユーザーを追加するには、確実に設定ツールがロック解除して、アカウント一覧の下にある <span class="guibutton"><strong>+</strong></span> ボタン（つまり、プラス記号）をクリックします。ダイアログウィンドウが表示され、ユーザーの詳細を決められます。
+ </div><div class="figure" id="fig-Managing_Users_and_Groups-User_Accounts-Adding_an_Account"><div class="figure-contents"><div class="mediaobject"><img src="images/user-accounts-create.png" alt="新しいアカウントの作成" /><div class="longdesc"><div class="para">
+ 新しいアカウントの作成
+ </div></div></div></div><h6>図3.3 新しいアカウントの作成</h6></div><br class="figure-break" /><div class="para">
+ アカウントを作成するために以下の手順をとります:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ <span class="guimenu"><strong>アカウントの種類</strong></span>プルダウンリストからアカウントの種類を選択します。利用可能なアカウントの種類は<code class="option">管理者</code> と <code class="option">標準</code>（デフォルトのオプション）です。
+ </div></li><li class="step"><div class="para">
+ アカウントに関連づける名前を設定するには、<span class="guilabel"><strong>フルネーム</strong></span>入力フィールドを記入します。この名前はログインマネージャーにより使用され、パネルに表示されます。
+ </div></li><li class="step"><div class="para">
+ <span class="guilabel"><strong>ユーザー名</strong></span>プルダウンリストから推奨されたユーザー名を選択するか、対応する入力フィールドを記入します。
+ </div></li><li class="step"><div class="para">
+ 設定を確認するには、<span class="guibutton"><strong>作成</strong></span>ボタンをクリックします。
+ </div></li></ol></div><div class="para">
+ Fedora は <em class="firstterm">ユーザープライベートグループ</em> (UPG: user private group) スキーマを使用します。UPG スキーマは標準的な UNIX のグループの取り扱い方法を何も追加や変更をしません。新しい利便性を提供します。新規ユーザーを作成すると必ず、ユーザーと同じ名前を持つ一意なグループが作成されます。
+ </div><div class="para">
+ 新規アカウントが作成されたとき、デフォルトの設定ファイルが <code class="filename">/etc/skel/</code> ディレクトリから新規ホームディレクトリの中にコピーされます。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Managing_Users_and_Groups-User_Accounts.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="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html"><strong>次へ</strong>3.2.3. ユーザーの削除</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.html
new file mode 100644
index 0000000..ef0c7bd
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User.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>3.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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="sect-Managing_Users_and_Groups-User_Accounts.html" title="3.2. ユーザー アカウントのツールを使う" /><link rel="prev" href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html" title="3.2.2. 新規ユーザーを追加する" /><link rel="next" href="s1-users-configui.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="docna
v"><li class="previous"><a accesskey="p" href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="s1-users-configui.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.3. ユーザーの削除</h3></div></div></div><a id="idm33679008" class="indexterm"></a><div class="para">
+ ユーザーを削除するには、設定ツールを確実にロック解除して、アカウント一覧から希望するアカウントを選択して、アカウント一覧の下にある <span class="guibutton"><strong>−</strong></span> ボタン（つまり、マイナス記号）をクリックします。ダイアログが表示され、変更を確認するかキャンセルできます。
+ </div><div class="figure" id="fig-Managing_Users_and_Groups-User_Accounts-Removing_an_Account"><div class="figure-contents"><div class="mediaobject"><img src="images/user-accounts-remove.png" alt="アカウントの削除" /><div class="longdesc"><div class="para">
+ アカウントの削除
+ </div></div></div></div><h6>図3.4 アカウントの削除</h6></div><br class="figure-break" /><div class="para">
+ ユーザーに属しているファイルやディレクトリ（つまり、ホームディレクトリ、メールスプールおよび一時ファイル）を削除するには、<span class="guibutton"><strong>ファイルを削除</strong></span>ボタンをクリックします。これらのファイルをそのまま残して、ユーザーアカウントのみを削除するには、<span class="guibutton"><strong>ファイルを残す</strong></span>をクリックします。削除を中止するには、<span class="guibutton"><strong>キャンセル</strong></span>をクリックします。
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html"><strong>戻る</strong>3.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="s1-users-configui.html"><strong>次へ</strong>3.3. ユーザー管理のツールを使う</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts.html
new file mode 100644
index 0000000..104b7da
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Managing_Users_and_Groups-User_Accounts.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="第3章 ユーザーとグループの管理" /><link rel="prev" href="ch-Managing_Users_and_Groups.html" title="第3章 ユーザーとグループの管理" /><link rel="next" href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html" title="3.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="p
revious"><a accesskey="p" href="ch-Managing_Users_and_Groups.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-Managing_Users_and_Groups-User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. ユーザー アカウントのツールを使う</h2></div></div></div><a id="idm57135280" class="indexterm"></a><a id="idm73264192" class="indexterm"></a><a id="idm73262784" class="indexterm"></a><div class="para">
+ <span class="application"><strong>ユーザーアカウント</strong></span>設定ツールは、ローカルユーザーを表示、修正、追加、および削除をできます。ツールを実行するには、<span class="guimenu"><strong>アクティビティ</strong></span>メニューから<span class="guimenu"><strong>アプリケーション</strong></span> → <span class="guisubmenu"><strong>システムツール</strong></span> → <span class="guimenuitem"><strong>システム設定</strong></span>を選択して、<span class="guimenu"><strong>ユーザーアカウント</strong></span>アイコンをクリックします。
+ </div><div class="figure" id="fig-Managing_Users_and_Groups-User_Accounts"><div class="figure-contents"><div class="mediaobject"><img src="images/user-accounts.png" alt="ユーザー アカウントの設定ツール" /><div class="longdesc"><div class="para">
+ ユーザー アカウントの設定ツール
+ </div></div></div></div><h6>図3.1 ユーザー アカウントの設定ツール</h6></div><br class="figure-break" /><div class="para">
+ デフォルトで、ツールは自分のアカウントに関連する特定の設定のみを変更できます。このため、<code class="systemitem">root</code> ユーザーのみがユーザーとグループを設定できます。すべての種類の変更のために設定ツールをロック解除するには、ウィンドウの右上角にある<span class="guibutton"><strong>ロック解除</strong></span>ボタンをクリックして、プロンプトに正しいパスワードを入力します。
+ </div><div class="section" id="sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.1. アカウントの設定</h3></div></div></div><div class="para">
+ アカウントに関連づけられている画像を変更するには、アカウント名の次にあるアイコンをクリックして、プルダウンリストから画像を選択するか、ローカルドライブから画像を使用するために<span class="guimenuitem"><strong>他の画像も参照...</strong></span> をクリックします。
+ </div><div class="para">
+ アカウントに関連する名前を変更するには、編集するために名前の次にあるアイコンをクリックします。
+ </div><div class="para">
+ アカウントの種類を変更するには、<span class="guimenu"><strong>アカウントの種類</strong></span>ラベルの次にあるテキストをクリックします。この変更は、自分自身のアカウントを変更するときでも、設定ツールがロック解除されている必要があることに注意してください。
+ </div><div class="para">
+ アカウントのデフォルトの言語を変更するには、<span class="guilabel"><strong>言語</strong></span>ラベルの次のあるテキストをクリックして、一覧から言語を選択します。
+ </div><div class="para">
+ パスワードを変更するには、<span class="guilabel"><strong>パスワード</strong></span>ラベルの次にあるテキストをクリックします。ダイアログボックスが表示され、新しいパスワードを設定できます。変更を確認するには現在をパスワードを入力しなければいけません。これをすると、変更を保存するために<span class="guibutton"><strong>変更</strong></span>ボタンをクリックします。
+ </div><div class="figure" id="fig-Managing_Users_and_Groups-User_Accounts-Changing_Password"><div class="figure-contents"><div class="mediaobject"><img src="images/user-accounts-password-change.png" alt="パスワードの変更" /><div class="longdesc"><div class="para">
+ パスワードの変更
+ </div></div></div></div><h6>図3.2 パスワードの変更</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>パスワードのセキュリティのアドバイス</h2></div><div class="admonition"><div class="para">
+ 非常に長いパスワードを使用することをお勧めします。これにより、侵入者がパスワードを推測して、権限なくアカウントにアクセスすることを難しくなるからです。また、パスワードは辞書に載っている単語を基にしないことをお勧めします。文字、数字と特殊文字の組み合わせを使用します。
+ </div></div></div><div class="para">
+ 最後に、特定のアカウントに対して自動ログインを設定するには、<span class="guilabel"><strong>自動的にログイン</strong></span>スイッチを有効にします。変更をするには、設定ツールがロック解除されなければいけません。
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Managing_Users_and_Groups.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-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User.html"><strong>次へ</strong>3.2.2. 新規ユーザーを追加する</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Preface-Book_Organization.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Preface-Book_Organization.html
new file mode 100644
index 0000000..501ce61
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Preface-Book_Organization.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>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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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-Configuring_the_Language_and_Keyboard.html">1章<em>言語とキーボードの設定</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">2章<em>日付と時刻の設定</em></a> covers the configuration of the system date and time. Read this chapter if you need to change the date and time setup, or configure the system to synchronize the clock with a remote Network Time Protocol (NTP) server.
+ </div><div class="para">
+ <a class="xref" href="ch-Managing_Users_and_Groups.html">3章<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 both <span class="application"><strong>Yum</strong></span> and the <span class="application"><strong>PackageKit</strong></span> suite of graphical package management tools.
+ </div><div class="para">
+ <a class="xref" href="ch-yum.html">4章<em>Yum</em></a> describes the <span class="application"><strong>Yum</strong></span> package manager. Read this chapter for information how to search, install, update, and uninstall packages on the command line.
+ </div><div class="para">
+ <a class="xref" href="ch-PackageKit.html">5章<em>PackageKit</em></a> describes the <span class="application"><strong>PackageKit</strong></span> suite of graphical package management tools. Read this chapter for information how to search, install, update, and uninstall packages using a graphical user interface.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="part-Networking.html">パートIII「ネットワーク」</a></span></dt><dd><div class="para">
+ このパートは Fedora のネットワーク設定の仕方について記述しています。
+ </div><div class="para">
+ <a class="xref" href="ch-Network_Interfaces.html">7章<em>ネットワーク・インターフェース</em></a> explores various interface configuration files, interface control scripts, and network function files located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. Read this chapter for information how to use these files to configure network interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="part-Infrastructure_Services.html">パートIV「インフラストラクチャーサービス」</a></span></dt><dd><div class="para">
+ このパートはリモート ログインの有効化、認証の設定、daemon やサービスの設定方法についての情報を提供します。
+ </div><div class="para">
+ <a class="xref" href="ch-Services_and_Daemons.html">8章<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-Configuring_Authentication.html">9章<em>認証の設定</em></a> describes how to configure user information retrieval from Lightweight Directory Access Protocol (LDAP), Network Information Service (NIS), and Winbind user account databases, and provides an introduction to the System Security Services Daemon (SSSD). Read this chapter if you need to configure authentication on your system.
+ </div><div class="para">
+ <a class="xref" href="ch-OpenSSH.html">10章<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">パートV「サーバー」</a></span></dt><dd><div class="para">
+ このパートは、ウェブサーバーを導入する、またはネットワーク上にファイルとディレクトリを共有する方法のようなサーバーに関連したさまざまな話題を説明しています。
+ </div><div class="para">
+ <a class="xref" href="ch-DHCP_Servers.html">11章<em>DHCP サーバー</em></a> guides you through the installation of a Dynamic Host Configuration Protocol (DHCP) server and client. Read this chapter if you need to configure DHCP on your system.
+ </div><div class="para">
+ <a class="xref" href="ch-DNS_Servers.html">12章<em>DNS サーバー</em></a> introduces you to Domain Name System (DNS), explains how to install, configure, run, and administer the <span class="application"><strong>BIND</strong></span> DNS server. Read this chapter if you need to configure a DNS server on your system.
+ </div><div class="para">
+ <a class="xref" href="ch-Web_Servers.html">13章<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">14章<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">15章<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">16章<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></dd><dt class="varlistentry"><span class="term"><a class="xref" href="part-Monitoring_and_Automation.html">パートVI「監視および自動化」</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 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">パートVII「カーネル、モジュールおよびドライバーの設定」</a></span></dt><dd><div class="para">
+ このパートはカーネルのカスタマイズと管理を支援するさまざまなツールをカバーします。
+ </div><div class="para">
+ <a class="xref" href="ch-Manually_Upgrading_the_Kernel.html">21章<em>カーネルをアップグレードする</em></a> provides important information how to manually update a kernel package using the <code class="command">rpm</code> command instead of <code class="command">yum</code>. Read this chapter if you cannot update a kernel package with the <span class="application"><strong>Yum</strong></span> package manager.
+ </div><div class="para">
+ <a class="xref" href="ch-Working_with_Kernel_Modules.html">22章<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><div class="para">
+ <a class="xref" href="ch-kdump.html">23章<em>The kdump Crash Recovery Service</em></a> explains how to configure, test, and use the <code class="systemitem">kdump</code> service in Fedora, and provides a brief overview of how to analyze the resulting core dump using the <span class="application"><strong>crash</strong></span> debugging utility. Read this chapter to learn how to enable <code class="systemitem">kdump</code> on your system.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="appe-Consistent_Network_Device_Naming.html">付録A <em>Consistent Network Device Naming</em></a></span></dt><dd><div class="para">
+ This appendix covers consistent network device naming for network interfaces, a feature that changes the name of network interfaces on a system in order to make locating and differentiating the interfaces easier. Read this appendix to learn more about this feature and how to enable or disable it.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="ch-RPM.html">付録B <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">yum</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="ch-The_X_Window_System.html">付録C <em>X Window System</em></a></span></dt><dd><div class="para">
+ This appendix covers the configuration of the X Window System, the graphical environment used by Fedora. Read this appendix if you need to adjust the configuration of your X Window System.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="ch-The_sysconfig_Directory.html">付録D <em>sysconfig ディレクトリー</em></a></span></dt><dd><div class="para">
+ This appendix outlines some of the files and directories located in the <code class="filename">/etc/sysconfig/</code> directory. Read this appendix if you want to learn more about these files and directories, their function, and their contents.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="ch-proc.html">付録E <em>The proc File System</em></a></span></dt><dd><div class="para">
+ This appendix explains the concept of a virtual file system, and describes some of the top-level files and directories within the <code class="systemitem">proc</code> file system (that is, the <code class="filename">/proc/</code> directory). Read this appendix if you want to learn more about this file system.
+ </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/17/html/System_Administrators_Guide/sect-Preface-Feedback.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Preface-Feedback.html
new file mode 100644
index 0000000..5a48caa
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-Preface-Feedback.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. フィードバック</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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="sect-Preface-Feedback" lang="ja-JP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4. フィードバック</h2></div></div></div><a id="idm39392192" 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 <a href="http://bugzilla.redhat.com/">Bugzilla</a> against the product <span class="application"><strong>Fedora Documentation</strong></span>.
+ </div><div class="para">
+ バグリポートの送信時は、必ず以下の情報を確認してください:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Manual's identifier: <code class="literal">system-administrator's-guide</code>
+ </div></li><li class="listitem"><div class="para">
+ バージョン番号: <code class="literal">17</code>
+ </div></li></ul></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/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html
new file mode 100644
index 0000000..a183897
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.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>9.2.6. Setting Up Kerberos 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Configuring_Domains.html" title="9.2.5. Configuring Domains" /><link rel="next" href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html" title="9.2.7. Configuring a Proxy Domain" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-SSSD_User_Guide-Configuring_Domains.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.6. Setting Up Kerberos Authentication</h3></div></div></div><a id="idm65921184" class="indexterm"></a><div class="para">
+ In order to set up Kerberos authentication, you need to know the address of your <em class="firstterm">key distribution center</em> (KDC) and the Kerberos domain. The client configuration is then stored in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="para">
+ The Kerberos 5 authentication back end does not contain an identity provider and must be paired with one in order to function properly (for example, <code class="option">id_provider = ldap</code>). Some information required by the Kerberos 5 authentication back end must be supplied by the identity provider, such as the user's <em class="firstterm">Kerberos Principal Name</em> (UPN). The identity provider configuration should contain an entry to specify this UPN. Refer to the manual page for the applicable identity provider for details on how to configure the UPN.
+ </div><div class="para">
+ If the UPN is not available in the identity back end, SSSD will construct a UPN using the format <code class="systemitem">username at krb5_realm</code>.
+ </div><div class="para">
+ SSSD assumes that the Kerberos KDC is also a Kerberos kadmin server. However, it is very common for production environments to have multiple, read-only replicas of the KDC, but only a single kadmin server (because password changes and similar procedures are comparatively rare). To manage this type of configuration, you can use the <code class="option">krb5_kpasswd</code> option to specify where your password changing service is running, or if it is running on a non-default port. If the <code class="option">krb5_kpasswd</code> option is not defined, SSSD tries to use the Kerberos KDC in order to change the password. Refer to the <em class="citetitle">sssd-krb5(5)</em> manual page for more information about this and all Kerberos configuration options.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Setting_Up_Kerberos_Authentication-How_to_Set_up_Kerberos_Authentication"><h5 class="formalpara">How to Set Up Kerberos Authentication</h5>
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file to include the following settings:
+ </div><pre class="screen"># A domain with identities provided by LDAP and authentication by Kerberos
+[domain/KRBDOMAIN]
+enumerate = false
+id_provider = ldap
+chpass_provider = krb5
+ldap_uri = ldap://ldap.mydomain.org
+ldap_search_base = dc=mydomain,dc=org
+tls_reqcert = demand
+ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+
+auth_provider = krb5
+krb5_server = 192.168.1.1
+krb5_realm = EXAMPLE.COM
+krb5_changepw_principal = kadmin/changepw
+krb5_ccachedir = /tmp
+krb5_ccname_template = FILE:%d/krb5cc_%U_XXXXXX
+krb5_auth_timeout = 15
+</pre><div class="para">
+ This example describes the minimum options that must be configured when using Kerberos authentication. Refer to the <em class="citetitle">sssd-krb5(5)</em> manual page for a full description of all the options that apply to configuring Kerberos authentication.
+ </div><div class="note"><div class="admonition_header"><h2>DNS Service Discovery</h2></div><div class="admonition"><div class="para">
+ The <code class="systemitem">DNS</code> service discovery feature allows the Kerberos 5 authentication back end to automatically find the appropriate <code class="systemitem">DNS</code> servers to connect to using a special <code class="systemitem">DNS</code> query. For more information on the <code class="systemitem">DNS</code> service discovery feature, refer to <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">「Using SRV Records with Failover」</a>.
+ </div></div></div><div class="section" id="sect-setting-up-sasl-gssapi-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.6.1. Setting up SASL/GSSAPI Authentication</h4></div></div></div><div class="para">
+ <em class="firstterm">GSSAPI</em> (Generic Security Services Application Programming Interface) is a supported <em class="firstterm">SASL</em> (Simple Authentication and Security Layer) authentication method. Kerberos is currently the only commonly used GSSAPI implementation. An LDAP client and an LDAP server use SASL to take advantage of GSSAPI as the authentication method (an alternative to plain text passwords, etc.). The GSSAPI plug-in for SASL is then invoked on the client and server side to use Kerberos to communicate.
+ </div><div class="para">
+ Using GSSAPI protected communication for LDAP is an advanced configuration not supported by the Authentication Configuration tool; the following steps show how to manually configure it.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">On the KDC</span></dt><dd><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Using <span class="application"><strong>kadmin</strong></span>, set up a Kerberos service principal for the directory server. Use the <code class="option">-randkey</code> option for the <span class="application"><strong>kadmin</strong></span>'s <code class="command">addprinc</code> command to create the principal and assign it a random key:
+ </div><pre class="screen">kadmin: addprinc -randkey ldap/server.example.com</pre></li><li class="listitem"><div class="para">
+ Use the <code class="command">ktadd</code> command to write the service principal to a file:
+ </div><pre class="screen">kadmin: ktadd -k /root/ldap.keytab ldap/server.example.com</pre></li><li class="listitem"><div class="para">
+ Using <span class="application"><strong>kadmin</strong></span>, set up a Kerberos host principal for the client running SSSD. Use the <code class="option">-randkey</code> option for the <span class="application"><strong>kadmin</strong></span>'s <code class="command">addprinc</code> command to create the principal and assign it a random key:
+ </div><pre class="screen">kadmin: addprinc -randkey host/client.example.com</pre></li><li class="listitem"><div class="para">
+ Use the <code class="command">ktadd</code> command to write the host principal to a file:
+ </div><pre class="screen">kadmin: ktadd -k /root/client.keytab host/client.example.com</pre></li></ol></div></dd><dt class="varlistentry"><span class="term">On the Directory Server</span></dt><dd><div class="para">
+ Complete the following steps for a directory server of your choice:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">OpenLDAP</span></dt><dd><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Copy the previously created <code class="filename">/root/ldap.keytab</code> file from the KDC to the <code class="filename">/etc/openldap/</code> directory and name it <code class="filename">ldap.keytab</code>.
+ </div></li><li class="listitem"><div class="para">
+ Make the <code class="filename">/etc/openldap/ldap.keytab</code> file read-writable for the <code class="systemitem">ldap</code> user and readable for the <code class="systemitem">ldap</code> group only.
+ </div></li></ol></div></dd><dt class="varlistentry"><span class="term">Red Hat Directory Server</span></dt><dd><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Copy the previously created <code class="filename">/root/ldap.keytab</code> file from the KDC to the <code class="filename">/etc/dirsrv/</code> directory and name it <code class="filename">ldap.keytab</code>.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="varname">KRB5_KTNAME</code> line in the <code class="filename">/etc/sysconfig/dirsrv</code> (or instance-specific) file, and set the keytab location for the <code class="varname">KRB5_KTNAME</code> variable. For example:
+<pre class="screen">
+# In order to use SASL/GSSAPI the directory
+# server needs to know where to find its keytab
+# file - uncomment the following line and set
+# the path and filename appropriately
+KRB5_KTNAME=/etc/dirsrv/ldap.keytab; export KRB5_KTNAME</pre>
+
+ </div></li></ol></div></dd></dl></div></dd><dt class="varlistentry"><span class="term">On the Client</span></dt><dd><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Copy the previously created <code class="filename">/root/client.keytab</code> file from the KDC to the <code class="filename">/etc/</code> directory and name it <code class="filename">krb5.keytab</code>. If the <code class="filename">/etc/krb5.keytab</code> file exists already, use the <span class="application"><strong>ktutil</strong></span> utility to merge both files properly. For more information on the <span class="application"><strong>ktutil</strong></span> utility, refer to <code class="command">man ktutil</code>.
+ </div></li><li class="listitem"><div class="para">
+ Modify your /etc/sssd/sssd.conf file to include the following settings:
+ </div><pre class="screen">
+ldap_sasl_mech = gssapi
+ldap_sasl_authid = host/client.example.com at EXAMPLE.COM
+ldap_krb5_keytab = /etc/krb5.keytab (default)
+ldap_krb5_init_creds = true (default)
+ldap_krb5_ticket_lifetime = 86400 (default)
+krb5_realm = EXAMPLE.COM
+</pre></li></ol></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Configuring_Domains.html"><strong>戻る</strong>9.2.5. Configuring Domains</a></li><li class="up"><a accesskey="u" href="#"><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-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html"><strong>次へ</strong>9.2.7. Configuring a Proxy Domain</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html
new file mode 100644
index 0000000..7e3b27f
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7. Configuring a Proxy Domain</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html" title="9.2.6. Setting Up Kerberos Authentication" /><link rel="next" href="chap-SSSD_User_Guide-Troubleshooting.html" title="9.2.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 c
lass="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Troubleshooting.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.7. Configuring a Proxy Domain</h3></div></div></div><a id="idm29586496" class="indexterm"></a><div class="para">
+ SSSD currently only supports LDAP and Kerberos as authentication providers. If you prefer to use SSSD (for example, to take advantage of its caching functionality), but SSSD does not support your authentication method, you can set up a proxy authentication provider. This could be the case if you use fingerprint scanners or smart cards as part of your authentication process. Similarly, you can set up proxy to serve as an identity provider.
+ </div><div class="para">
+ The following sections cover combinations of identity and authentication providers in which the proxy server takes the role of one.
+ </div><div class="section" id="sect-SSSD-proxy-krb5"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.7.1. proxy/KRB5</h4></div></div></div><div class="para">
+ The following configuration is an example of a combination of a proxy identity provider used with Kerberos authentication:
+ </div><div class="para">
+ Edit the <code class="filename">/etc/sssd/sssd.conf</code> configuration file to include the following settings:
+ </div><pre class="screen">
+[domain/PROXY_KRB5]
+auth_provider = krb5
+krb5_server = 192.168.1.1
+krb5_realm = EXAMPLE.COM
+
+id_provider = proxy
+proxy_lib_name = nis
+enumerate = true
+cache_credentials = true</pre><div class="para">
+ For more information on various Kerberos configuration options, refer to <a class="xref" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">「Setting Up Kerberos Authentication」</a>.
+ </div></div><div class="section" id="sect-SSSD-LDAP-proxy"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.7.2. LDAP/proxy</h4></div></div></div><div class="para">
+ An example of a combination of an LDAP identity provider and a proxy authentication provider is the use of the LDAP with a custom PAM stack. To enable authentication via the PAM stack, complete the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/sssd/sssd.conf</code> configuration file to include the following settings:
+ </div><pre class="screen">
+[domain/LDAP_PROXY]
+id_provider = ldap
+ldap_uri = ldap://example.com
+ldap_search_base = dc=example,dc=com
+
+auth_provider = proxy
+proxy_pam_target = sssdpamproxy
+enumerate = true
+cache_credentials = true
+</pre><div class="para">
+ By specifying the options above, authentication requests will be proxied via the <code class="filename">/etc/pam.d/sssdpamproxy</code> file which provides the needed module interfaces. Note that the <code class="filename">pam_ldap.so</code> file can be substituted with a PAM module of your choice.
+ </div><div class="para">
+ For more information on various LDAP configuration options, refer to <a class="xref" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">「Configuring an LDAP Domain」</a>.
+ </div></li><li class="listitem"><div class="para">
+ Create a <code class="filename">/etc/pam.d/sssdpamproxy</code> file (if not already created) and specify the following settings in it:
+ </div><pre class="screen">
+auth required pam_ldap.so
+account required pam_ldap.so
+password required pam_ldap.so
+session required pam_ldap.so</pre></li></ol></div></div><div class="section" id="sect-SSSD-proxy-proxy"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.7.3. proxy/proxy</h4></div></div></div><div class="para">
+ An example of a combination of an proxy identity provider and a proxy authentication provider is the use of the proxy identity provider with a custom PAM stack. To enable authentication via the PAM stack, complete the following steps:
+ </div><div class="note"><div class="admonition_header"><h2>Make sure the nss-pam-ldapd package is installed</h2></div><div class="admonition"><div class="para">
+ In order to use the proxy identity provider, you must have the <span class="package">nss-pam-ldapd</span> package installed.
+ </div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/sssd/sssd.conf</code> configuration file to include the following settings:
+ </div><pre class="screen">
+[domain/PROXY_PROXY]
+auth_provider = proxy
+id_provider = proxy
+proxy_lib_name = ldap
+proxy_pam_target = sssdproxyldap
+enumerate = true
+cache_credentials = true
+</pre><div class="para">
+ By specifying the options above, authentication requests will be proxied via the <code class="filename">/etc/pam.d/sssdproxyldap</code> file which provides the needed module interfaces.
+ </div><div class="para">
+ For more information on the options used in the configuration example above, refer to <code class="command">man sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ Create a <code class="filename">/etc/pam.d/sssdproxyldap</code> file (if not already created) and specify the following settings in it:
+ </div><pre class="screen">
+auth required pam_ldap.so
+account required pam_ldap.so
+password required pam_ldap.so
+session required pam_ldap.so</pre></li><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/nslcd.conf</code> file (the default configuration file for the LDAP name service daemon) to include the following settings:
+ </div><pre class="screen">
+uid nslcd
+gid ldap
+uri ldaps://ldap.mydomain.org:636
+base dc=mydomain,dc=org
+ssl on
+tls_cacertdir /etc/openldap/cacerts</pre><div class="para">
+ For more information on the options used in the configuration example above, refer to <code class="command">man nslcd.conf</code>
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>戻る</strong>9.2.6. Setting Up Kerberos 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="chap-SSSD_User_Guide-Troubleshooting.html"><strong>次へ</strong>9.2.8. トラブルシューティング</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html
new file mode 100644
index 0000000..d16d15e
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.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>9.2.2. SSIDの特徴</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="next" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html" title="9.2.3. Setting Up SSSD" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.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="chap-SSSD_User_Guide-Introduction.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-SSSD_User_Guide-Introduction-SSSD_Features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.2. SSIDの特徴</h3></div></div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Offline_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.1. オフライン認証</h4></div></div></div><div class="para">
+ One of the primary benefits of SSSD is offline authentication. This solves the case of users having a separate corporate account and a local machine account because of the common requirement to implement a Virtual Private Network (<abbr class="abbrev">VPN</abbr>).
+ </div><div class="para">
+ SSSD can cache remote identities and authentication credentials. This means that you can still authenticate with these remote identities even when a machine is offline. In an SSSD system, you only need to manage one account.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Server_Load_Reduction"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.2. Server Load Reduction</h4></div></div></div><div class="para">
+ The use of SSSD also helps to reduce the load on identification servers. For example, using <span class="package">nss_ldap</span>, every client application that needs to request user information opens its own connection to the LDAP server. Managing these multiple connections can lead to a heavy load on the LDAP server. In an SSSD system, only the SSSD Data Provider process actually communicates with the LDAP server, reducing the load to one connection per client system.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.3. Support for Multiple Domains</h4></div></div></div><a id="idm70024448" class="indexterm"></a><div class="para">
+ You can use SSSD to specify multiple domains of the same type. Compare this to an <code class="filename">nsswitch.conf</code> file configuration, with which you can only request user information from a single server of any particular type (LDAP, NIS, etc.). With SSSD, you can create multiple domains of the same, or of different types of identity provider.
+ </div><div class="para">
+ Beginning with version 0.6.0, SSSD maintains a separate database file for each domain. This means that each domain has its own cache, and in the event that problems occur and maintenance is necessary, it is very easy to purge the cache for a single domain, by stopping <code class="systemitem">sssd</code> and deleting the corresponding cache file. These cache files are stored in the <code class="filename">/var/lib/sss/db/</code> directory.
+ </div><div class="para">
+ All cache files are named according to the domain that they represent, for example <code class="filename">cache_<em class="replaceable"><code>DOMAINNAME</code></em>.ldb</code>.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm70030208">Considerations Associated with Deleting Cache Files</h5><a id="idm70030864" class="indexterm"></a>
+ Deleting a domain's cache file can have some unexpected side effects. You should be aware of the following before you proceed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Deleting the cache file also deletes all user data (both identification and cached credentials). Consequently, you should not proceed unless you are online and can authenticate with your username against the domain's servers, because offline authentication will fail.
+ </div></li><li class="listitem"><div class="para">
+ If you are online and change your configuration to reference a different identity provider, SSSD will recognize users from both providers until the cached entries from the original provider time out.
+ </div><div class="para">
+ To avoid this situation, you can either purge the cache or use a different domain name for the new provider (this is the recommended practice). Changing the domain name means that when you restart SSSD it will create a new cache file (with the new name) and the old file will be ignored.
+ </div></li></ul></div></div><div class="section" id="idm61945792"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm61945792">9.2.2.4. Support for LDAP Referrals</h4></div></div></div><div class="para">
+ SSSD supports two types of LDAP referrals: object-level referrals and subtree referrals. These referral types and the extent of SSSD support is outlined below.
+ </div><div class="section" id="idm61947408"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm61947408">9.2.2.4.1. Object-level Referrals</h5></div></div></div><div class="para">
+ SSSD provides full support for object-level referrals within the same LDAP server, correctly handling any differences in the distinguished name (DN) that might exist as part of the LDAP server referral configuration.
+ </div><div class="para">
+ SSSD provides partial support for object-level referrals between different LDAP servers, and requires that the full DN of an LDAP request be identical on each server. SSSD does not support referrals to different DN paths on other servers.
+ </div></div><div class="section" id="idm61949920"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm61949920">9.2.2.4.2. Subtree Referrals</h5></div></div></div><div class="para">
+ SSSD provides a similar level of support for subtree referrals as it does for object-level referrals. That is, it supports referrals to a changed DN on the local system or to an identical DN on a remote system. The difference with subtree referrals, however, is the ability to set up identical subtrees on each LDAP server and to then configure referrals between these subtrees.
+ </div></div><div class="section" id="idm61951344"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm61951344">9.2.2.4.3. Enabling LDAP Referrals</h5></div></div></div><div class="para">
+ To take advantage of the SSSD LDAP referral functionality, you need to set the <code class="option">ldap_referrals</code> option to <code class="literal">TRUE</code> in the LDAP domain configuration section of the <code class="filename">/etc/sssd/sssd.conf</code> file. This will enable anonymous access to the second LDAP server.
+ </div><div class="note"><div class="admonition_header"><h2>Make sure SSSD is compiled with OpenLDAP version 2.4.13 or later</h2></div><div class="admonition"><div class="para">
+ SSSD only supports LDAP referrals when it is compiled with OpenLDAP version 2.4.13 or later.
+ </div></div></div></div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Differentiating_Like_named_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.5. Differentiating Like-named Users</h4></div></div></div><div class="para">
+ SSSD supports the differentiation of like-named users in different domains. For example, you can differentiate the user <code class="systemitem">kate</code> in the <code class="systemitem">ldap.example.com</code> domain from the user <code class="systemitem">kate</code> in the <code class="systemitem">ldap.myhome.com</code> domain. You can use SSSD to make requests using fully-qualified usernames. If you request information for <code class="systemitem">kate</code>, you will receive the information from whichever domain is listed first in the look-up order. If you request information for <code class="systemitem">kate at ldap.myhome.com</code>, however, you will receive the correct user information.
+ </div><div class="para">
+ SSSD also provides a <code class="option">filter_users</code> option, which you can use to exclude certain users from being fetched from the database. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for full details about this option.
+ </div></div><div class="section" id="sect-SSSD_User_Guide-SSSD_Features-Integration_with_IPA"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.2.2.6. IPAとの統合</h4></div></div></div><div class="para">
+ Beyond the offline authentication, multiple domain management and other features already described, SSSD is also designed to integrate with and enhance the functionality of IPA clients. In an environment with the latest version of IPA installed, SSSD provides additional functionality, including support for dynamic DNS updates, host-based access control, and password migration from an LDAP-only environment into the LDAP/Kerberos 5 environment employed by IPA.
+ </div><div class="section" id="idm21963696"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm21963696">9.2.2.6.1. ダイナミックDNSアップデートのサポート</h5></div></div></div><div class="para">
+ Because the IP address of IPA clients can change, SSSD provides the ability to dynamically update the client's DNS entry on the IPA server. Using a combination of Kerberos and GSS-TSIG (Generic Security Service Algorithm for Secret Key Transaction), IPA can determine the identity of the host machine, authenticate it, and allow that machine to edit its own DNS record. These changes are then stored in the LDAP back end.
+ </div><div class="note"><div class="admonition_header"><h2>Each IPA client can only edit its own DNS record</h2></div><div class="admonition"><div class="para">
+ Using this authentication system means that each IPA client can only edit its own DNS record; it cannot edit the DNS record of any other client.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm21966224">ダイナミックDNSアップデート設定</h5>
+ The SSSD configuration file provides two options used for setting up dynamic DNS updates: <code class="option">ipa_dyndns_update</code>, used to enable dynamic DNS updates; and <code class="option">ipa_dyndns_iface</code>, which specifies the interface whose IP address should be used for dynamic DNS updates.
+ </div><div class="para">
+ Refer to the <em class="citetitle">sssd-ipa</em> manual page for more information about these options, and how to configure dynamic DNS updates.
+ </div><div class="note"><div class="admonition_header"><h2>Support for dynamic DNS updates</h2></div><div class="admonition"><div class="para">
+ Support for dynamic DNS updates is only available on IPA version 2 or later, and with DNS correctly configured.
+ </div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Introduction.html"><strong>戻る</strong>9.2. The System Security Services Daemon (SSSD)</a></li><li class="up"><a accesskey="u" href="#"><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-SSSD_User_Guide-Setting_Up_SSSD.html"><strong>次へ</strong>9.2.3. Setting Up SSSD</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html
new file mode 100644
index 0000000..44ef13c
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.9. SSSD Configuration File 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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="システム管理者ガイド" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="9.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Troubleshooting.html" title="9.2.8. トラブルシューティング" /><link rel="next" href="ch-OpenSSH.html" title="第10章 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="chap-SSSD_User_Guide-Troubleshoo
ting.html"><strong>戻る</strong></a></li><li class="next"><a accesskey="n" href="ch-OpenSSH.html"><strong>次へ</strong></a></li></ul><div class="section" id="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.9. SSSD Configuration File Format</h3></div></div></div><div class="para">
+ The following listing describes the current version (Version 2) of the SSSD configuration file format.
+ </div><pre class="programlisting">[sssd]
+config_file_version = 2
+services = nss, pam
+domains = mybox.example.com, ldap.example.com, ipa.example.com, nis.example.com
+# sbus_timeout = 300
+
+[nss]
+nss_filter_groups = root
+nss_filter_users = root
+nss_entry_cache_timeout = 30
+nss_enum_cache_timeout = 30
+
+[domain/mybox.example.com]
+domain_type = local
+enumerate = true
+min_id = 1000
+# max_id = 2000
+
+local_default_shell = /bin/bash
+local_default_homedir = /home
+
+# Possible overrides
+# id_provider = local
+# auth_provider = local
+# authz_provider = local
+# passwd_provider = local
+
+[domain/ldap.example.com]
+domain_type = ldap
+server = ldap.example.com, ldap3.example.com, 10.0.0.2
+# ldap_uri = ldaps://ldap.example.com:9093
+# ldap_use_tls = ssl
+ldap_search_base = dc=ldap,dc=example,dc=com
+enumerate = false
+
+# Possible overrides
+# id_provider = ldap
+# id_server = ldap2.example.com
+# auth_provider = krb5
+# auth_server = krb5.example.com
+# krb5_realm = KRB5.EXAMPLE.COM
+
+[domain/ipa.example.com]
+domain_type = ipa
+server = ipa.example.com, ipa2.example.com
+enumerate = false
+
+# Possible overrides
+# id_provider = ldap
+# id_server = ldap2.example.com
+# auth_provider = krb5
+# auth_server = krb5.example.com
+# krb5_realm = KRB5.EXAMPLE.COM
+
+[domain/nis.example.com]
+id_provider = proxy
+proxy_lib = nis
+auth_provider = proxy
+proxy_auth_target = nis_pam_proxy
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Troubleshooting.html"><strong>戻る</strong>9.2.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="ch-OpenSSH.html"><strong>次へ</strong>第10章 OpenSSH</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Configuring.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Configuring.html
new file mode 100644
index 0000000..0561b41
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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 17 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 at 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 <admin at example.com></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 <admin at example.com>
+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 <admin at example.com>
+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/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html
new file mode 100644
index 0000000..c9f67ca
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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. Refer to 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/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html
new file mode 100644
index 0000000..8915434
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Running.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP-Running.html
new file mode 100644
index 0000000..ab4c73a
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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">8章<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/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP.html b/public_html/ja-JP/Fedora/17/html/System_Administrators_Guide/sect-System_Monitoring_Tools-Net-SNMP.html
new file mode 100644
index 0000000..e7ea5b8
--- /dev/null
+++ b/public_html/ja-JP/Fedora/17/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-17-ja-JP-1-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.17');
+
+ addID('Fedora.17.books');
+ addID('Fedora.17.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 17 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">yum</code> command in the following form:
+ </div><pre class="synopsis"><code class="command">yum</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">yum 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">「パッケージのインストール」</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/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.pdf b/public_html/ja-JP/Fedora/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.pdf
new file mode 100644
index 0000000..ced8b27
Binary files /dev/null and b/public_html/ja-JP/Fedora/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.pdf differ
diff --git a/public_html/ja-JP/Site_Statistics.html b/public_html/ja-JP/Site_Statistics.html
index 5ea3096..e2edf01 100644
--- a/public_html/ja-JP/Site_Statistics.html
+++ b/public_html/ja-JP/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>言語数の合計: </b>44<br />
- <b>パッケージ数の合計: </b>851
+ <b>パッケージ数の合計: </b>852
</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 2268bb3..6ccc8f4 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:12</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 21ab4a7..7ff3f94 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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</updated>
<!--author>
<name></name>
<uri></uri>
@@ -385,20 +385,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/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-en-US.epub</id>
+ <title>システム管理者ガイド</title>
+ <id>http://docs.fedoraproject.org/ja-JP/Fedora/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.epub</id>
<!--author>
<name></name>
<uri></uri>
</author-->
- <updated>2012-08-09</updated>
+ <updated>2013-03-15</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 17
-</summary>
- <content type="text">The System Administrator's Guide documents relevant information regarding the deployment, configuration, and administration of Fedora 17. 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/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-en-US.epub">
+ <summary>Fedora 17 の導入、設定および管理</summary>
+ <content type="text">システム管理者ガイドは、Fedora 17 の導入、設定および管理に関連する情報をドキュメント化しています。システムの基本的な理解をしているシステム管理者向けになっています。</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/ja-JP/Fedora/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
index 2c3d96e..5d86588 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_Documentation.xml</id>
<title>Fedora コントリビュータ用ドキュメント</title>
<subtitle>Fedora コントリビュータ用ドキュメント</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 696fe52..5170180 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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 9842475..d95da1a 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.xml</id>
<title>Fedora ドラフト文書</title>
<subtitle>Fedora ドラフト文書</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 3e3800f..7b6908f 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds.xml b/public_html/ja-JP/opds.xml
index 3d32fde..b72584e 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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:12</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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 ドラフト文書</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</updated>
<dc:language>ja-JP</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/ja-JP/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 73bf731..2f9f600 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -254,6 +254,15 @@
<a class="type" href="./Fedora/17/pdf/Release_Notes/Fedora-17-Release_Notes-ja-JP.pdf" onclick="window.top.location='./Fedora/17/pdf/Release_Notes/Fedora-17-Release_Notes-ja-JP.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.17.System_Administrators_Guide' class="book collapsed">
+ <a class="type" href="Fedora/17/html/System_Administrators_Guide/index.html" onclick="window.top.location='./Fedora/17/html/System_Administrators_Guide/index.html'"><span class="book">システム管理者ガイド</span></a>
+ <div id='Fedora.17.System_Administrators_Guide.types' class="types" onclick="work=0;">
+ <a class="type" href="./Fedora/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.epub" >epub</a>
+ <a class="type" href="./Fedora/17/html/System_Administrators_Guide/index.html" onclick="window.top.location='./Fedora/17/html/System_Administrators_Guide/index.html';return false;">html</a>
+ <a class="type" href="./Fedora/17/html-single/System_Administrators_Guide/index.html" onclick="window.top.location='./Fedora/17/html-single/System_Administrators_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="./Fedora/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.pdf" onclick="window.top.location='./Fedora/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.17' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.17.untrans_books');">
<span class="version">未翻訳</span>
<div id='Fedora.17.untrans_books' class="books hidden">
@@ -302,15 +311,6 @@
<a class="type" href="../en-US/./Fedora/17/pdf/Security_Guide/Fedora-17-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Security_Guide/Fedora-17-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
- <div id='Fedora.17.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.System_Administrators_Guide.types');">
- <a class="type" href="../en-US/Fedora/17/html/System_Administrators_Guide/index.html" onclick="window.top.location='../en-US/Fedora/17/html/System_Administrators_Guide/index.html'"><span class="book">System Administrators Guide</span></a>
- <div id='Fedora.17.System_Administrators_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-en-US.epub" >epub</a>
- <a class="type" href="../en-US/./Fedora/17/html/System_Administrators_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/System_Administrators_Guide/index.html';return false;">html</a>
- <a class="type" href="../en-US/./Fedora/17/html-single/System_Administrators_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/System_Administrators_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-en-US.pdf';return false;">pdf</a>
- </div>
- </div>
<div id='Fedora.17.Wireless_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Wireless_Guide.types');">
<a class="type" href="../en-US/Fedora/17/html/Wireless_Guide/index.html" onclick="window.top.location='../en-US/Fedora/17/html/Wireless_Guide/index.html'"><span class="book">Wireless Guide</span></a>
<div id='Fedora.17.Wireless_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/kn-IN/Site_Statistics.html b/public_html/kn-IN/Site_Statistics.html
index 9fdb6ed..183c8cd 100644
--- a/public_html/kn-IN/Site_Statistics.html
+++ b/public_html/kn-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 91726ed..1c59234 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 a62e174..e461198 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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 0a46678..da36b5b 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 788bdcc..a241943 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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 c6c6f61..bd3e829 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 83924a2..4e23339 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds.xml b/public_html/kn-IN/opds.xml
index 0f8b601..e3a3fea 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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:14</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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 9fdb6ed..183c8cd 100644
--- a/public_html/ko-KR/Site_Statistics.html
+++ b/public_html/ko-KR/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 cca69bb..ac38749 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:14</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 ef144a3..5306c66 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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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 92e6259..44e0c9e 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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 4c85f30..377418c 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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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 323e9fd..1ebbd31 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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 99e7c82..a3b2a12 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds.xml b/public_html/ko-KR/opds.xml
index 38f0f65..323ec76 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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:14</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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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/ml-IN/Site_Statistics.html b/public_html/ml-IN/Site_Statistics.html
index 9fdb6ed..183c8cd 100644
--- a/public_html/ml-IN/Site_Statistics.html
+++ b/public_html/ml-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 3e794af..3987429 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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 4d10b80..e944948 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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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 be4417d..478e121 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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 0fdb62a..4704cb9 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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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 ad30364..758d6a0 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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 5758b08..b0de24f 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds.xml b/public_html/ml-IN/opds.xml
index c7ff9aa..283d5c7 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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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 9fdb6ed..183c8cd 100644
--- a/public_html/mr-IN/Site_Statistics.html
+++ b/public_html/mr-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 2ff5d95..1bd6758 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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 94dd1a9..496d562 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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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 3fa3847..70f9f2e 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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 6e7abf7..7d922fc 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>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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 96c32a6..ca80b6f 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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 bc88801..b619553 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds.xml b/public_html/mr-IN/opds.xml
index b2c96aa..96e457a 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>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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 9fdb6ed..183c8cd 100644
--- a/public_html/nb-NO/Site_Statistics.html
+++ b/public_html/nb-NO/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 ad82f64..d98e0ec 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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 36744a9..2dab5e4 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>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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 25cded4..a78f81b 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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 3889415..8e3151d 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>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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 33d850f..bc550af 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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 f7cf0e5..4f79776 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds.xml b/public_html/nb-NO/opds.xml
index 1e840e6..f0954c6 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>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</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>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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 ee6567e..01c1e32 100644
--- a/public_html/nl-NL/Site_Statistics.html
+++ b/public_html/nl-NL/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Totaal talen: </b>44<br />
- <b>Totaal pakketten: </b>851
+ <b>Totaal pakketten: </b>852
</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 9e1ca8f..87acf19 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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 8e7687f..ffa1fba 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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:16</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 5a9d6c1..03143b0 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 d6eb624..7667f33 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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 0635916..55ad1eb 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 ba133a6..0791330 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds.xml b/public_html/nl-NL/opds.xml
index 4cf825f..fc68c36 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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</updated>
<dc:language>nl-NL</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/nl-NL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 e4f989b..eedda87 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>2013-03-15T14:21:51</updated>
+ <updated>2013-03-15T15:10:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -16,7 +16,7 @@
<entry>
<title>অসমীয়া</title>
<id>as-IN/opds.xml</id>
- <updated>2013-03-15T14:21:28</updated>
+ <updated>2013-03-15T15:10:00</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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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>2013-03-15T14:21:29</updated>
+ <updated>2013-03-15T15:10:01</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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:02</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>2013-03-15T14:21:30</updated>
+ <updated>2013-03-15T15:10:03</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>2013-03-15T14:21:31</updated>
+ <updated>2013-03-15T15:10:03</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>2013-03-15T14:21:32</updated>
+ <updated>2013-03-15T15:10:04</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>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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>2013-03-15T14:21:33</updated>
+ <updated>2013-03-15T15:10:05</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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:06</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>2013-03-15T14:21:34</updated>
+ <updated>2013-03-15T15:10:07</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>2013-03-15T14:21:35</updated>
+ <updated>2013-03-15T15:10:07</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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:08</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>2013-03-15T14:21:36</updated>
+ <updated>2013-03-15T15:10:09</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>2013-03-15T14:21:37</updated>
+ <updated>2013-03-15T15:10:10</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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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>2013-03-15T14:21:38</updated>
+ <updated>2013-03-15T15:10:10</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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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>2013-03-15T14:21:39</updated>
+ <updated>2013-03-15T15:10:11</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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:12</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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:13</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>2013-03-15T14:21:40</updated>
+ <updated>2013-03-15T15:10:14</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>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:14</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>മലയാളം</title>
<id>ml-IN/opds.xml</id>
- <updated>2013-03-15T14:21:41</updated>
+ <updated>2013-03-15T15:10:15</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ml-IN/opds.xml"/>
@@ -216,7 +216,7 @@
<entry>
<title>मराठी</title>
<id>mr-IN/opds.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:15</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="mr-IN/opds.xml"/>
@@ -224,7 +224,7 @@
<entry>
<title>Norsk (bokmål)</title>
<id>nb-NO/opds.xml</id>
- <updated>2013-03-15T14:21:42</updated>
+ <updated>2013-03-15T15:10:16</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nb-NO/opds.xml"/>
@@ -232,7 +232,7 @@
<entry>
<title>Nederlands</title>
<id>nl-NL/opds.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nl-NL/opds.xml"/>
@@ -240,7 +240,7 @@
<entry>
<title>ଓଡ଼ିଆ</title>
<id>or-IN/opds.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="or-IN/opds.xml"/>
@@ -248,7 +248,7 @@
<entry>
<title>ਪੰਜਾਬੀ</title>
<id>pa-IN/opds.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pa-IN/opds.xml"/>
@@ -256,7 +256,7 @@
<entry>
<title>Polski</title>
<id>pl-PL/opds.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pl-PL/opds.xml"/>
@@ -264,7 +264,7 @@
<entry>
<title>Português Brasileiro</title>
<id>pt-BR/opds.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:19</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-BR/opds.xml"/>
@@ -272,7 +272,7 @@
<entry>
<title>Português</title>
<id>pt-PT/opds.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-PT/opds.xml"/>
@@ -280,7 +280,7 @@
<entry>
<title>Romanian</title>
<id>ro/opds.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:20</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ro/opds.xml"/>
@@ -288,7 +288,7 @@
<entry>
<title>Русский</title>
<id>ru-RU/opds.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ru-RU/opds.xml"/>
@@ -296,7 +296,7 @@
<entry>
<title>Slovenščina</title>
<id>sk-SK/opds.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sk-SK/opds.xml"/>
@@ -304,7 +304,7 @@
<entry>
<title>Srpski (latinica)</title>
<id>sr-Latn-RS/opds.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-Latn-RS/opds.xml"/>
@@ -312,7 +312,7 @@
<entry>
<title>Српски</title>
<id>sr-RS/opds.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-RS/opds.xml"/>
@@ -320,7 +320,7 @@
<entry>
<title>Svenska</title>
<id>sv-SE/opds.xml</id>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sv-SE/opds.xml"/>
@@ -328,7 +328,7 @@
<entry>
<title>தமிழ்</title>
<id>ta-IN/opds.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ta-IN/opds.xml"/>
@@ -336,7 +336,7 @@
<entry>
<title>తెలుగు</title>
<id>te-IN/opds.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="te-IN/opds.xml"/>
@@ -344,7 +344,7 @@
<entry>
<title>Українська</title>
<id>uk-UA/opds.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:25</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="uk-UA/opds.xml"/>
@@ -352,7 +352,7 @@
<entry>
<title>简体中文</title>
<id>zh-CN/opds.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-CN/opds.xml"/>
@@ -360,7 +360,7 @@
<entry>
<title>繁體中文</title>
<id>zh-TW/opds.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 9fdb6ed..183c8cd 100644
--- a/public_html/or-IN/Site_Statistics.html
+++ b/public_html/or-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 2b4163d..4b351ac 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 75c1d38..bb28f32 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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 4f3c75f..5543210 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 2f7be5f..e2c1d44 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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 62ee106..e5af4ee 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 9333266..09c5ddf 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds.xml b/public_html/or-IN/opds.xml
index 58bff39..195c2b0 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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 9fdb6ed..183c8cd 100644
--- a/public_html/pa-IN/Site_Statistics.html
+++ b/public_html/pa-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 cbb6eb3..6a730fe 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 fe0279a..d33e7f6 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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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 599d70e..94a248d 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:18</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 0ae98aa..2cae350 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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:18</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 f9b0ed1..cef8c15 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:18</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 325dbeb..259d425 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds.xml b/public_html/pa-IN/opds.xml
index b6b5f2f..012ab79 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>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:17</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:18</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.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:18</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:18</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:43</updated>
+ <updated>2013-03-15T15:10:18</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 15e6cd3..cb48bcb 100644
--- a/public_html/pl-PL/Site_Statistics.html
+++ b/public_html/pl-PL/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Razem języków: </b>44<br />
- <b>Razem pakietów: </b>851
+ <b>Razem pakietów: </b>852
</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 a9703f3..2f91ea3 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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 7e54d81..e16ec8b 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>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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 a85d6bc..c0bc6c5 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_Documentation.xml</id>
<title>Dokumentacja dla współtwórców Fedory</title>
<subtitle>Dokumentacja dla współtwórców Fedory</subtitle>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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 e1d0962..84962c4 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>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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 9d262d5..f426e45 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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 f4dc483..fc46359 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds.xml b/public_html/pl-PL/opds.xml
index 8c36c8c..d7cfc90 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>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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 9fdb6ed..183c8cd 100644
--- a/public_html/pt-BR/Site_Statistics.html
+++ b/public_html/pt-BR/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 2107fd5..238327b 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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 d98244a..03186cf 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>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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 5668809..1c6a127 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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 677da4e..3e9e46d 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>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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 c95ce44..b6d9c8f 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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 32cfc8e..b57941b 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds.xml b/public_html/pt-BR/opds.xml
index a257ed6..d79d5c4 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>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:19</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:18</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>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:44</updated>
+ <updated>2013-03-15T15:10:19</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 9fdb6ed..183c8cd 100644
--- a/public_html/pt-PT/Site_Statistics.html
+++ b/public_html/pt-PT/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 af4f79c..f3be24d 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:19</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 9cc9bb1..467efb4 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>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 bca9156..ce73238 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 1a15fe6..a016685 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>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 2a27040..4eccc1c 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 62b2b46..f084e59 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds.xml b/public_html/pt-PT/opds.xml
index 5630211..98398eb 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>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:19</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>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 9fdb6ed..183c8cd 100644
--- a/public_html/ro/Site_Statistics.html
+++ b/public_html/ro/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</div>
</body>
</html>
diff --git a/public_html/ro/opds-Community_Services_Infrastructure.xml b/public_html/ro/opds-Community_Services_Infrastructure.xml
index fb076e6..4bbe528 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora.xml b/public_html/ro/opds-Fedora.xml
index 87a7f17..b6182b6 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>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 bed5a74..1f5c562 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 683dfbb..ba94f89 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>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 725f62a..c2c0b3d 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.xml</id>
<title>Schiță Documentație Fedora</title>
<subtitle>Schiță Documentație Fedora</subtitle>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 3d4892a..bb5b106 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds.xml b/public_html/ro/opds.xml
index d150198..548b4c8 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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:20</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/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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_Security_Team.xml</id>
- <updated>2013-03-15T14:21:45</updated>
+ <updated>2013-03-15T15:10:20</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 10d1501..5b54b35 100644
--- a/public_html/ru-RU/Site_Statistics.html
+++ b/public_html/ru-RU/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Всего языков: </b>44<br />
- <b>Всего пакетов: </b>851
+ <b>Всего пакетов: </b>852
</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 de4014b..2fec853 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:20</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 cf41e81..ecb9899 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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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 be8d86b..ff3a92b 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_Documentation.xml</id>
<title>Документация участника Fedora</title>
<subtitle>Документация участника Fedora</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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 d545cee..ac41711 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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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 7c269c5..2985187 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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 6a53311..a343519 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds.xml b/public_html/ru-RU/opds.xml
index 5755dfd..45c1001 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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:20</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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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 9fdb6ed..183c8cd 100644
--- a/public_html/sk-SK/Site_Statistics.html
+++ b/public_html/sk-SK/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 926df80..b8a1a5c 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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 f39b4c1..851db2e 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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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 2ef96c4..a1733f8 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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 2df4fbf..7190fd8 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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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 66f8f49..aa25ff4 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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 2ca2a7d..404f655 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds.xml b/public_html/sk-SK/opds.xml
index 160ae1d..2523905 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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:21</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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 9fdb6ed..183c8cd 100644
--- a/public_html/sr-Latn-RS/Site_Statistics.html
+++ b/public_html/sr-Latn-RS/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 c2bc0c7..5f9963d 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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 866793e..f7e4b13 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>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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 343a8e5..38b4772 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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 2e5f880..f3f49ad 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</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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 cb23828..6e9abd7 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_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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 f71263c..3c365a6 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.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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 9f54831..82c1410 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>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:46</updated>
+ <updated>2013-03-15T15:10:22</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</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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_Core.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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 9fdb6ed..183c8cd 100644
--- a/public_html/sr-RS/Site_Statistics.html
+++ b/public_html/sr-RS/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 efc8cd8..d727aa1 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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 5188694..bfe2327 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>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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 fe6fd83..3b9b4bd 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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 5b2e8ca..a50e5e4 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>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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 1690539..9e45968 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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 1b57a78..8f35d78 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds.xml b/public_html/sr-RS/opds.xml
index aa96cc3..6b53af2 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>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:22</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>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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 9fdb6ed..183c8cd 100644
--- a/public_html/sv-SE/Site_Statistics.html
+++ b/public_html/sv-SE/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 8965239..a5c4b85 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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 eb4646b..19de650 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>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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 adba8f7..e746774 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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 00fa144..a1de997 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>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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 dca23b1..b63e96f 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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 90fffb9..86c0147 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds.xml b/public_html/sv-SE/opds.xml
index 54b91e5..726d624 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>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:47</updated>
+ <updated>2013-03-15T15:10:23</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>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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.xml</id>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:23</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 9fdb6ed..183c8cd 100644
--- a/public_html/ta-IN/Site_Statistics.html
+++ b/public_html/ta-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 107cc22..35aa317 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:24</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 19a9fea..661fb9e 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>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:24</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 ad0b5db..e2c2ec2 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 e3d4ae3..0660cdf 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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 442a961..13ee21d 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 05d0cd5..9401be2 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds.xml b/public_html/ta-IN/opds.xml
index 487864e..e61b17f 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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:48</updated>
+ <updated>2013-03-15T15:10:24</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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 9fdb6ed..183c8cd 100644
--- a/public_html/te-IN/Site_Statistics.html
+++ b/public_html/te-IN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 e7e4c0a..45ea3cc 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 f232d17..91f24e4 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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 758e44c..9da6cc6 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 7af0216..54592b3 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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 2286969..de0f0ed 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 a94bd7a..199ee83 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds.xml b/public_html/te-IN/opds.xml
index 2ecb841..c33ae12 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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:24</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 9ad5de0..8d6933a 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -7153,6 +7153,21 @@
</div>
</div>
+ <div class="book">
+ <span id="System_Administrators_Guide" class="book">システム管理者ガイド</span>
+ <div class="types">
+
+ <a class="type" href="./ja-JP/Fedora/17/epub/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.epub">epub</a>
+
+ <a class="type" href="./ja-JP/Fedora/17/html/System_Administrators_Guide/index.html">html</a>
+
+ <a class="type" href="./ja-JP/Fedora/17/html-single/System_Administrators_Guide/index.html">html-single</a>
+
+ <a class="type" href="./ja-JP/Fedora/17/pdf/System_Administrators_Guide/Fedora-17-System_Administrators_Guide-ja-JP.pdf">pdf</a>
+
+ </div>
+ </div>
+
</div> </div> <div class="books">
<div class="book">
diff --git a/public_html/uk-UA/Site_Statistics.html b/public_html/uk-UA/Site_Statistics.html
index 93a92bf..5b29dd7 100644
--- a/public_html/uk-UA/Site_Statistics.html
+++ b/public_html/uk-UA/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Загалом мов: </b>44<br />
- <b>Загалом пакунків: </b>851
+ <b>Загалом пакунків: </b>852
</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 db71df3..eeb8f41 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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 7a96196..e8cc602 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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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 8490221..924b2c9 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_Documentation.xml</id>
<title>Документація для учасника розробки Fedora</title>
<subtitle>Документація для учасника розробки Fedora</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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 29bc69e..ad36773 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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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 2170d78..9632d68 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.xml</id>
<title>Чернетки документації з Fedora</title>
<subtitle>Чернетки документації з Fedora</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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 8e15c96..d3474c4 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds.xml b/public_html/uk-UA/opds.xml
index 09e80bf..aa298de 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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:49</updated>
+ <updated>2013-03-15T15:10:25</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 9fdb6ed..183c8cd 100644
--- a/public_html/zh-CN/Site_Statistics.html
+++ b/public_html/zh-CN/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 190dbf4..538d7ef 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:25</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 ad9b98a..331bd74 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>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 14e9ea7..5bcdc48 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 a6f6d94..3312388 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>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 3b742cb..a23bfcc 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 b55ed56..5acd519 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds.xml b/public_html/zh-CN/opds.xml
index 7f0b7ce..fea4e01 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>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:25</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>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 9fdb6ed..183c8cd 100644
--- a/public_html/zh-TW/Site_Statistics.html
+++ b/public_html/zh-TW/Site_Statistics.html
@@ -55,7 +55,7 @@
<td>4</td>
<td>20</td>
<td>16</td>
- <td>54</td>
+ <td>55</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>851
+ <b>Total Packages: </b>852
</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 c3795ba..fa5f436 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_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 1364408..529c201 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>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 26214e0..30c9711 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_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 d8a9c66..8821c99 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>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 e74d644..d3e15be 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.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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 1de330c..91bb43d 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</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml
index 4c8b830..d5b407e 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>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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-Fedora_Draft_Documentation.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</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-Fedora_Security_Team.xml</id>
- <updated>2013-03-15T14:21:50</updated>
+ <updated>2013-03-15T15:10:26</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
More information about the docs-commits
mailing list